Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

finding default and "live" geometry for plugin modules #12

Closed
dirkleas opened this issue Apr 24, 2018 · 3 comments
Closed

finding default and "live" geometry for plugin modules #12

dirkleas opened this issue Apr 24, 2018 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@dirkleas
Copy link
Owner

I've prototyped some code in a rack fork that generates much of the introspective data for rack plugins/modules. there're several modules that are dynamically resizeable once added to a patch. I'm looking for details on how to get that detail both 1) from the plugin distributions (ideally without having to instantiate ModuleWidget instances), and 2) from a loaded patch. is there something similar to gPlugins for the live patch modules? code and/or references appreciated

ps: for extra credit, how about the width of the patching window so I can do layout management in view?!

@dirkleas dirkleas added bug Something isn't working help wanted Extra attention is needed and removed bug Something isn't working labels Apr 24, 2018
@dirkleas
Copy link
Owner Author

resizeable modules in core are consistently storing a width property in the patch json as expected, and current patch is available from settings.json via lastPath or within rack at runtime via gRackWidget->lastPath

@dirkleas
Copy link
Owner Author

dirkleas commented May 4, 2018

fyi, latest fork adds width data to generated .../Rack/meta.json via File.Catalog, and also saves width when saving patches, stability improving -- beta quality stability. woot!

@dirkleas
Copy link
Owner Author

confirmed here that widgets can't be instantiated outside Rack main thread (e.g. not in plugin modules) and that a PR wasn't probable, so sticking with 1) my fork (preferred), or 2) DLwigglz r4xH4x + rackcli --sync/--share

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant