Rockbox Development > Feature Ideas

Custom actions/tags for touchscreen targets

<< < (3/5) > >>

Biont:
That does make sense, yes. Dunno which one sounds better, though  ;)

punkt:
Sorry it took so long, here's the simulator: http://www.theess.de/assets/files/buildsim.zip

This includes the updated patch (see FS#11084). Tags are:

--- Code: ---%vl|identifier|number of states|
%vd'identifier'

--- End code ---

Touch-Action is:

--- Code: ---vs'identifier'[value]

--- End code ---

Biont:
Thank you very much!!

I already spent 3 hours getting used to the tags and writing a new theme and I must say I'm having loads of fun :)


Another idea: Cycle backwards. It might not be the most important thing there is, but I'm sure it wouldn't hurt being able to do it.



I'm currently trying to realize some basic WPS customization from within the WPS. Keeping track of the viewports to display pretty much blows my mind atm, but I hope I'll get it done.

But saving the values in a file so it can be reloaded on the next startup would go too far, right?

EDIT:

This is fun:



3 custom buttons and the "wps menu"


change settings in the menu (currently only button config and screen menu)


and change the behaviour of the 3 custom buttons (each of them can cycle through a set of different functions)

punkt:
Wow, that's far out!

Biont:
Those customizable buttons are the main reason I came up with the idea of saving the values in some sort of config file (or the .wps itself, if that's possible)

This patch is already so amazing that I'm having a hard time thinking about basic stuff that might be missing.
All I can come up with are these far-fetched ideas (apart from cycling backwards)

Also nice to have: setting values conditionally and/or being able to have multiple actions in one touch area.

That would be very useful in cases when I'd like to open a new popup while there are others currently active. You'd either need to close them first or cause a big mess :) So what would be great is something like this:

%?vda<...|%vsb0%vsc0%Vda|...|...>

or

%T|0|0|40|40|vsa1
%T|0|0|40|40|vsb0
%T|0|0|40|40|vsc0

I'm not sure which way would be better and I also don't know if both wouldn't require a huge amount of extra coding (the same for saving the values). I'm just writing down ideas here ;)

EDIT: I am aware that there's no need to go crazy on this patch. It already has loads of potential as it is now :D

Navigation

[0] Message Index

[#] Next page

[*] Previous page