SMB3-Foundry
SMB3-Foundry copied to clipboard
Help tools also automatic for color change.
I noticed that in Foundry regarding the new tool for the color change of the layer, you must necessarily choose the color before seeing it in the project as it is.
So I thought: Isn't it better to see it in real time as you swipe between colors inside the window?
Then I thought of another solution to another problem:
Given that it is not possible to immediately understand which object a color is linked to, unless you already know by heart which object on the level it is associated with:
Isn't it easier to change one color at a time with each mouse wheel movement when the pointer is over a color square to then return to the original set once out of the square? This would be useful to see and understand, without opening the window and changing color, which object a color of one of the squares refers to, it could also be useful for a quick color scroll without having the window in front of your eyes, above the project that so it could be annoying when choosing.
Obviously then to set a color because you are sure of what you want you could open the window and set the color, but even in this case something should change, in the window containing all the colors, you should not see how a color is applied by necessity only if you choose it by confirming the setting, you should be able to hover the mouse pointer over the colors of the window and see in real time the color applied in the project.
Why should I waste time changing one at a time to see what a color looks like applied? How it works in the current version wastes time.
Returning to the first, if the mouse wheel were to be missing from the operator, there could be another easy way to use this function and view the colors without registering them but only to always try them on the condition that the pointer was over a color box, the problem of the lack of the mouse wheel could be overcome with simple and intuitive function keys, for example the "+" and "-" numeric keyboard keys. Obviously it is not necessarily necessary to use "+" and "-", also "page up" and "page down" would be fine or the arrows "up" and "down" if these already do not have other functional attributes. ("page up" and "page down" are much more interesting, I would prefer them) However the sense of what I want to understand is understood well is to take advantage of the keyboard in case of lack of the mouse wheel in order not to lose the intuitive function.
However I recommend writing the color value inside the window because for example the different types of black are not all the same, they have different results depending on the screen where the game is played, for example 0F is not the same 0D, 0E and others blacks, 0F should be applied to be more compatible, such as for example only white 30 and not 20, the only real shades of gray are 00 and 10, the other 1D, 2D and 3D vary according to the emulator. I am particular once they were revealed to me by a friend and I would like to point this out.
Perhaps if you chose a good idea it would also be launching a window notifying this possible danger of incompatibility with the screens but these are separate ideas, even if personally I would remove from the list the colors I mentioned as incompatible, also because, what do I need them all for? those blacks or a second white? And if those grays are not the result you wanted in your emulator, wouldn't it be useless to deceive ourselves?