I also agree about the issue: it's likely the plugin may be trying to grab stuff that just isn; y there yet. I would move part of this setup stuff to something later in the process, ie. perhaps a lazy-creation proc which gets the plugin popup reference and sets the value from the global instance if it doesn't exist yet.
So, I'm not sure I get it but I'm assuming this won't be an issue in the
next version, right? Please confirm.
what would "not be an issue"?with Pd-0.54 the ".popup" will not be created any more at all, so if your code depends on such an item, it will fail.otoh, Pd-0.54 will replace the ".popup" with a window-specific "${win}.popup". this window-specific item will not be created until the window is created, so if your code depends on such an item to exist at startup time, it is likely to fail as well.