Welcome to Swayimg Discussions!

[artemsen]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[voidbert]

I have an idea for the way anti-aliasing is managed. For the application programmer, having the anti-aliasing iterate through all the possible modes may be useful. However, I think most users would be fine with only two modes, e.g.: mks13 and none, and toggle between them.

A possible way to implement this would be the antialising config taking a list of modes as a value: antialiasing = mks13 none. Then, when swayimg opens, the first mode is chosen, and A and Shift+A switch between modes on that list. This way, the user can set what antialiasing modes they want to use, and the programmer can put them all in the config file to iterate through all of them.

I would have no problem implementing this feature if you think it's useful.

[artemsen]

I doubt this mode switching is necessary at all.
I would prefer one default mode setting and an on/off switch.

[voidbert]

Oh, so it would be even easier. Then, the antialising property could be kept as is, but another property would be added to say if it's enabled by default or not.