You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've started out building a control surface for an arduino project I've been working on - OSC cue lights, see the project at github and a video at video
It's great (and perfect timing) - a couple of things I have realised
The option to use a single command across a whole row would save a lot of typing!
There is no way to size fonts, it would be good if you could set a minimum font size so that the font gracefully shrinks to fit whatever is there
It would be nice if there was a way to set the colour of a button from an OSC input. I note there is a 'feedback' field but I'm not quite clear what this does - the way my system works is that you send a command (such as /go) and the unit responds with the state of the lamp (/go 1 or /go 0) meaning that if the unit doesn't work the lamps don't update. If this was possible it would remove for the separate activity widgets
The response of OSCWidgets seems to be significantly slower than touchOSC on an iPad - does the logging slow down responses? I think it's slower when the main window is open (I assume the logging is slowing things down?)
I have also realised I can't see a way to re-open the main properties window when you have closed it (without closing and re-opening the file) - could probably do with a view menu item to re-open it. Ideally then it wouldn't open by default when opening the file.
The text was updated successfully, but these errors were encountered:
The responsiveness issue was definitely related to the logging. In v0.6 I moved writing log messages to disk to a background thread, and also wrote a shiny new optimized logging display widget. Should feel faster now.
I agree, it takes to much typing to build a grid. I will have to think about a good fix for that. (You can always hand-edit the file in your text editor of choice until then)
Also agree about font sizing. I will add a new field for that.
"OSC Label" = set text label from an incoming OSC message
"OSC Feedback" = set the state of an OSCWidget widget from an incoming OSC message (ex: Toggle state of an OSCWidget Button, the level of an OSCWidgets Fader, the position of an OSCWidgets XY, etc...)
"OSC Trigger" = trigger an OSC widget from an incoming OSC message (ex: Press/Release an OSC Widget Button, start/stop an OSCWidgets Metronome, etc...)
I like the idea of setting color remotely, good idea.
To re-open the main window, you can right+click on any OSCWidget and select "Toggle Main Window" - and you can also choose that option from the OSCWidgets icon in the system tray.
Sorry - me again.
I've started out building a control surface for an arduino project I've been working on - OSC cue lights, see the project at github and a video at video
It's great (and perfect timing) - a couple of things I have realised
I have also realised I can't see a way to re-open the main properties window when you have closed it (without closing and re-opening the file) - could probably do with a view menu item to re-open it. Ideally then it wouldn't open by default when opening the file.
The text was updated successfully, but these errors were encountered: