Jean-Michaël Celerier

hmmmmm I wonder if it's not better to just set a unit on it and have it work automatically for those case instead of having multiple types ? (and maybe...

what should happen ? I tried with e.g. an automation with min/max -10, 10, and the OSC value used for tweening at -100 and 100 and I get the expected...

First we need to have a couple of examples / use-cases that use those to see what kind of api shold be provided

yes, that's reasonable :) the thing is, currently, the position of elements in a scenario is relative (between [0; 1]). But I can make it absolute to prevent it to...

I fixed the 1025 being displayed part

## To do : In the DeviceExplorer{Model,View} (and certainly also the StateInspectorWidget), delegates that match the various data types should be created, following this tutorial : http://doc.qt.io/qt-5/model-view-programming.html#a-simple-delegate This could also...

hmm, so at some point with @blueyeti we thought about using javascript scripts that would define what would happen at the level of a whole time sync (e.g. the trigger,...

e.g. to send `/foo/123 456` for weird OSC APIs

@thibaudk could you identify some of the cases where the focus gets lost ? Afterwards it can be manually be regained with grabKeyboard() but it's better if we don't loose...

everything is good but please revert the AVND_TEST_BUILD to 0, it should never be enabled on master (as some people use ossia-score-git arch package and may get random bamboozle test...