[APP] Magic Square Painter

[Phenomena]

@reina

Thinking of it, the game now feels taller (more Height?) than in your first screenshot of the post, and has a lot more space for the user interface.

Oddly enough, I made the resolution smaller, but reworked some of the buttons and the overall layout.

@reina

That was just an example of why I thought the info text was neat to look at, though. Apart from needing to learn Storage events, I can respect how you feel about that design of the program.

Thank you I may adopt a similar approach as Paint.net as having it in a little bar at the bottom is less in-your-face, but still there if you need it. It’s a good idea and I definitely don’t want anyone to feel lost on the tools at any level of use. Perhaps if I add more options, like texture overlays or something where it would be a bit more info to absorb, I’ll do that.

@reina

However, I suspect it will cause something to break because colour values are integers/numbers without decimals, and TimeDelta() causes a number with decimals to be generated.

Indeed, it did! I just posted about it here.

I can already see a difference in speed on preview, but of course, the real test will be getting it published online for the real trials by fire.

@reina

To solve the inconsistency issue in the second gif of my last post - if it’s even an issue

Ahh, that’s it! Knew I overlooked answering something…sorry about that.

I think the problem there is threefold:

• You’ll get black on the initial click, since it seems more intuitive and comfortable even to begin by adding color on new selections.

• Deselecting options resets all the values to 0, which also ends up being black. This is to clear out color ‘residue’ in the variables, otherwise you might have blends when you don’t want or expect them. There are times where you will want them though, so this is something I’d like to allow. Hopefully it’s not going to end up being like wanting my cake and trying to eat it too…

• Allowing selections to be locked in where all are colored the same has interfered with the rainbow bucket, as it can do different hues on all selected options at the same time - although it’s not accurately reflected in the values on the buckets and it’s hard to make slight changes after that due to the two previous things.

For now, this isn’t ideal at all, but a temporary workaround is to remember that any intial selections and deselections will erase your color settings from the variables - if you can plan for it when designing your pattern, it’s not as bad. The colors you choose before deselecting is still displayed on the grid since it was stored in the picker strings, but clicking the option again will be read as an ‘initial click’.

I don’t want to force anyone to start over when they only want to make a small change. I just have to make all of the above work in harmony, probably with another variable as you said.

Another idea is to make it possible to create & store a custom palette - at least for the duration of a session - which you can then apply as desired, and the only way these values would be edited or erased is if you choose to replace them or end your session.

@reina

Now that I’ve typed that out, it sounds even more confusing than usual

You’re good, but I know the feeling when things seemed to sound better in your head lol. I hope you got some rest.

Thanks a million!