On 2017-05-01 10:49 AM, Will Godfrey wrote: > Hi Tim, > > I've just found that there is a new-ish atom message for a plugin to notify > the > host of this. Does Muse use this yet? Also, I can't seem to find a plugin > example anywhere. Any idea where I can find one. > > Something like this is long overdue for Yoshimi :( > > .. and if I can manage to sneak it in bevore LAC... :) > > > TTFN > > Will. > Hiya Will, I'll CC our list since Andrew added the LV2 support. I imagine he would have liked to have this feature as well.
We support the state class. But not the changed message. Yet. I thought all that state saving/restoring stuff was already done in MusE. Well, yes it is. But I guess this is a new (and more powerful) thing where we can actually be informed of a change in the plugin (and more) rather than having to ask or poll? Possibly MusE doesn't need this 'changed' message for now: I think, we only need to retrieve the state when we save our song file (the user hits 'save', or the app closes etc.). Whatever the state happens to be at that time is what gets put into our song files. Being immediately informed of a change in the plugin might not be useful to MusE currently. Others may chime in here. Possibly, at least we can use it to set MusE's 'song is dirty' flag immediately (an asterisk appears beside the song name in the title bar, and you are prompted to save upon closing.) BTW Sorry I did get your last email but haven't had time to test your latest and greatest with the learning features. I should. I use yoshimi at every sit-down at the keys! Cheers. Tim. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
