PS: this was the surprise
. I wanted to make you a nice screenshot with your background. I forgot I wrote it in the changelog ><
Hehe, i was taking a look at git and it seems i was attracted to it like a bear to the honey
To be honest, i also thought it was something related with
@Crystal work...
1) Using the ps3sx emulator to run games, and even to do the "PKG shorcut"... with unknown performance but with custom settings, and the video/widescreen improvements mentioned by kozarovv
2) A new managunz wave (taken from retroarch) with real openGL shaders
3) Some kind of "translator" in between tiny3D and RSXGL (and a rebuild of the position and sizes of many interface elements) to create a "managunz HD" (in real 1920x1080p)
I still don't know if i'll change the name of colorset.ini ... anyway, It still need to check on this file to keep backward compatibility with previous themes. So, maybe it'll read 2 files colorset.ini and settings.ini (both will have the same job)
Hmmm, settings.ini is a very generic name but maybe you went too far
I prefer theme.ini because is more explicit, settings.ini sounds a bit like if is intended to store general managunz settings
I think is not needed to read the settings from the old .ini name to keep backward compatibility with them, if you are worrying about the themes i made i would say to drop the support to the old name completly
For now, it's available only for 3D and the box are aligned from the bottom like you asked. I wrote it in the todo list long time ago, I still have the screen shot you made.
About theme.ini, I had the same idea but it was settings.ini. Themes should be able to control some settings (like box align or waves enable/disable, every visual settings)
Hmm, yep i agree completly in that concept, the point is when we "apply" a theme the result should be exactly what the theme author intended to show, i bet there is many people reading this and thinking "of course mr. obvious" but is not so straightforward because there are some visual settings that doesnt belongs to the themes
Lets say... there are 2 different setting files, one from the theme and other for managunz general settings, and managunz is "merging" some settings from the theme.ini into the general settings
Btw, i think that "merging" is problematic, to be honest i could not understand well how it happens but while doing tests i had some "weird behaviours" as a consequence of swapping themes/UI's/colorsets back and forth
I cant give an accurate feedback of what i consider is weird sorry... but as far i remember what happens is some of the settins of theme_A are "inherited" by theme_B
And thats like a dual sided sword... it have something positive and something negative
The positive effect is it allows to create tutti-frutti megamixes of colors in a uncontrolled way... with this i mean... the result have a huge probability to look bad... but in few cases it could result in something aceptable
The negative effect is that usually looks horrible... and it happens without having any control of it (personally, i dont know when is going to happen, but most of the times it happened i thought it was an annoyance)
One last thing related with colorset.ini and changing the color filters "by month"... the concept of what i would like to achieve doesnt needs to be explained, you know, im trying to copy features of the XMB as usually
Basically... in the official XMB when we enter in the setting to change the background color there are 13 options... one of them is "by month" (dependant of the system time) and the other 12 are the months (keeps the color permanently, not dependant of the time)
I bet there is some point of the official code where that options are organized in a hierarchy where the the option "by month" is the parent and the 12 months are the children
I dont know how is the best way to deal with that in the colorset.ini but i was thinking also in the hierarchy, basically in the actual colroset.ini all the entries are located at "root" of the hierarchy like this:
Code:
[custom_colorset_name_1]
color_1...
color_2...
etc...
[custom_colorset_name_2]
color_1...
color_2...
etc...
And by adding other deepest level in the heirarchy it would look like this:
Code:
[custom_colorset_name_1]
color_1...
color_2...
etc...
[custom_colorset_name_2]
color_1...
color_2...
etc...
[by_month]
----[january]
----color_1...
----color_2...
----etc...
----[february]
----color_1...
----color_2...
----etc...
And in managunz settings we should be able to select either "custom_colorset_name_1", "custom_colorset_name_2", "by month"... or the months individually "january", etc...
Dunno, this way to organize the colorset.ini contents in a hierarchy is just the first idea that came to mind while thinking about how to deal with this new settings, but maybe you figure a better way, i started talking about it because is indirectly related with the cover/case alignment to bottom that can be stored in the theme.ini too... and yeah, the wave i forgot about it, and the font style too, etc... as you said, all the settings related to visual effects are candidate to be stored inside the theme.ini
