I think i understand why u had some trouble.
It's because the square to change value is a new feature from the v1.28... in the previous version we must enter to the submenu with cross button to change the value, or to do something else like loading the theme, or deleting it.
Then I added this button to change some values faster, especially when there is only "Yes" or "No". But I added it to everyoption, wihtout thinking.
So, i'm going to disable square with the option theme because you are rirght, changing the value without loading the theme is confusing...
Hmm, yes i guess at some point i did that, the other day at the time i wrote the big wall of text reporting small problems i was not aware that is mandatory to press the "cross load" at the end of the sequence to select a new theme, i was entering the submenu (with the arrows up/down), but not pressing the "cross load" after changing it so nothing was loaded
But i guess at some point i tryed to change them as you say, with the "square change" without entering the submenu (so the indication "cross load" doesnt even appears... so nothing is loaded)
I think at this point you have caught all the small problems i was mentioning about those selectors, the only one i still have a doubt is how to make obvious for the user that is absolutelly needed to press the "cross load" at the end of the sequence when choosing a theme
Maybe at this point you have changed something in the code or imagined a way, but im thinking maybe there is an easy solution
The real problem is when the user changes the theme this value is saved at the time of chaging it, even before pressing the "cross load"... so the solution is to not save the value at that point
If the user enters that menu changes the value and exits without pressing the "cross load" then you could reset the value to the previous state
This is annoying enought for the user to realize that is needed to enter the menu again and press the "cross load" after changing something (this is the point where you think "damn what i just changed has not been saved") and after that point you learn the lesson, this annoyance happens in lot of games, people is used to it
In other words... only save the value after pressing the "cross load"... actually this text could be renamed to something ike "load and save"
Btw, another detail (i cant stop)... that arrows used in the submenu that actually aims to up/down are used in the settings menu of lot of games... but uses to be horizontal to left/right
Actually, the way are located now up/down overlaps a bit with the option before/after the one we are changing, there is a small problem of pixels overlapped right now
If you place the arrows horizontally left/right this problem about pixels overlapped will be solved and i think will look more standard, additionally i think will be better mapped. Top/down to select the setting you want to change and left/right to change the value, is more intuitive imo
BTW, square decrease the value and triangle increase the value, i didn't want to overcrowd the screen with to much indication, so there is just square.
Ok, now i get why square decreases values... is because is working in combination with the position of the triangle "on top"... and "top" is to increase... so square is "down"
Personally i would remove triangle and keep only square to increase (or remove both and make the changes with left/right arrows as suggested before), the feature of being able to increase/decrease with 2 buttons is fine, but i agree with you is better to use the minimal buttons posible, not only because there is not much room at bottom to indicate how works each button... but because in most cases there are only needed a few buttons
The most simplifyed an interface is will be more intuitive and easyer to use (no need to remember anything, personally i hate hidden button combos because this reason)
Following this idea i would consider changing all the "cross change", "cross enter" and other cross text variants to a generic "cross select" (like in games settings too, hehehe)
In game settings menus there are usually only 2 button indications at bottom of the screen... "cross select" and "circle back"
And this takes me to another suggestion... i think there is no need to have the indication "hold circle back to XMB" in managunz games menu, the feature is fine (and the idea of the countdown is pretty cool) but the problem is the texts at bottom of games menu becomes longer (harder to read, less intuitive, increases dirtyness)
Everybody knows how to exit a game/app (by pressing "PS" button and selecting the option "quit game" from ingame XMB game column), so removing that option is not going to make any harm, the user will still be able to exit managunz by the official way
------------
Edit:
How works the image BG_TITLE.PNG for a "Flow" theme ?
I prepared a custom flow theme and included a 300x100 pixels png image for it (as a test to try to find where is used) but is not displayed
And another problem report, this time related with the side menu... it seems when you have a custom theme aplyed and you are in main managunz screen with all games displayed (so background is BG.PNG)... if you press triangle to make appear the side menu it suddenlly displays BGS.JPG for a milisecond (and then displays BG.PNG again)
It happens so fast that is hardly notable... i think the reason why i noticed it is because the background images i was using are big (around 2mb each) so it takes time to load them, even it can be seen the "progress bar/bullet" on top sudenlly
This happens only when having the side menu enabled of course
I can imagine is happening because the side menu shares code with the standard/previous game config display at full screen that uses the BGS.JPG, but im just mentioning incase you find a way to avoid this, is not much important and is not notable in most of the themes
. But I can add the "TV screen test" option inside the Adjust Screen option. There is a lot "TV screen test", if you choose one, i'll add it for the next update.
