|
possible yes.. if I intend to add this.. not for now.. the reason is that adding complex functionality to buttons like states press/hold adds a great deal of complexity to the usage of the software -- worse than cuttering the screen with buttons .. if a screen is getting crowded with buttons, I suggest grouping your functions that are alike in different screens -- if they relate to the same playlist etc, then you should make screens that are exactly the same (but with different buttons etc) when pressing a "switch" button, this new screen is loaded and it would basically look like that "panel" or part of the screen changed only. You can even implement this state thing by doing the same.. to be more specific: make something like Audio_player.skin, Audio_player2.skin and Audio_player3.skin... then make them exactly alike (as to looks) and then make a button in there that loads Audio_player2.skin and in that one, a button that loads Audio_player3.skin (and that one loads Audio_player.skin). Although I don't recommend doing such thing, it should be possible to do what you want .. I'd at most recommend making a "menu" with functions just like the radio functions menu.
__________________
Road Runner,RR's Myspace
"Being happy is not about having what you want, it's about wanting what you have."
"The best things in life are always free - but that doesn't mean money can't buy you good things."
|