ericmoderbacher / pushy Goto Github PK

I need some sort of higher level structure in place so that the user can swap which part of the screen does what.

Maybe a widget class despite hating the term "widget class".

Things to keep in mind:

• We will want configurations to persist across sessions
• We will want presets
• we need to tie some control to the widgets
• could be cool to have two controls control the same widget. for large and fine grain changes.

PushyINC.lua is getting big (377 lines)

Things that can potentially be put into its own file:
-Drawing to the screen
-slider object
-text object

pushy needs to be easily includable in other scripts. I imaging that the default behavior would be to just allow the user to edit params. But that should also be customizable.

If the user configures the push to behave in a specific way then it should persist when written to and read back out of a preset.

Notes:
The values of params are also saved to the preset so we only need to store which params are linked to which ui elements

Meta controls like sensitivity should also be captured by the param system.

when a control is removed from the system, its corresponding preset should die on the next save... which might be a fancy way of saying that gathering the preset values might have to be done right before presets are saved and not as we go.

Drawing a slider on a line breaks the line for other purposes. I think its because im adding elements to the line message table which means the sysex message is too long.
-need to limit the slider size to the size remaining on the line.
-maybe have some belts and suspenders when i send the sysex?