- This topic has 7 replies, 3 voices, and was last updated 11 years, 2 months ago by
.
-
Posts
-
Hi Atom
I would like to know if panels exported to standalone (and vst) will be what we have now (an exe that is Ctrlr with the panel loaded and fully editable) or if they will be locked in some way so no edit could be made on the panels.
I never ment to disable all edit capabilities in exported instances, that was never the idea. So not really, the “Panel” menu will be active and you’ll be able to enter edit mode, edit lua methods etc. Do you think it should be different ?
Yes, I expected something different. Ctrlr and .panel or .bzpanel on one side, and an exe or dll on the other side, one editable, the other not editable.
I expected this based on your own words here
“My question is however, how to change the appearance of such a binary, i’d like it to be more end-user friendly without all the editing stuff”
“The new feature should help all of you who want to distribute your work on other pages, forums. Even sell your work, if you test your panels with a version and pack them into a binary then you can support them yourselves etc.”
I’d like to sell some panels, but I don’t like the idea of selling and giving support to something that can be confusing, edited or modified.
You are correct i’ll keep my word i’ll add some options for instance export to disable some of this editing features.
Big +1 on das’s request. This is always what I was expecting from an exported instance. Just a bare bones panel, no ability needed to edit the Lua scripts or anything behind the scenes.
One suggestion with the standalone instance – make it auto-save midi IN/OUT settings so the user doesn’t need to make the settings then save their own instance (confusing to most users, sad but true). So when the user sets their midi settings, they don’t need to save/export anything. Next time they open the standalone panel the MIDI settings should be auto-saved. My suggestion would be that if ctrlr needs to save these settings to an external file in order to autosave midi device settings, that’s fine just store it in the user’s home tree in a directory named the same thing as the panel name.
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
Well you for now i added a “export->restricted instance” option, try that.
Nice work. You sure implemented that quickly! (before my post even!)
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
- The forum ‘Change requests’ is closed to new topics and replies.