While I cannot say much about your problem, here are some bits that you might (or might not) find useful.
Thank you for taking the time to respond!
- Have you tried / is it possible for your task to define your dialog resource as a file system rather than by code?
My interface includes a large list of dynamic elements. I'm not sure that I'll be able to give each a unique ID unless I create them with code. But I'll see if I can restructure at least some of this.
Although I cannot find the exact passage right now, it says somewhere in the docs, that you should use files, since it is the only way to get all features, except for menus, which are only constructable by code.
Gotcha. Good to know. The docs have really improved, but there's lots of little tidbits like this that you'll only see if you read every page of every parent class rather than seeing all of the relevant info in the method definition.
- I came to the (unconfirmed) conclusion, that some of the more exotic
CustomGuidata types are apparently not fully supported for dialog resources (the same definition for a
SPLINEgadget worked just fine in a description resource) and wrote my own little thing.
Ah. That makes sense as well. I think for now I'll live with the stylistic limitations of the current BitmapButton as it's easier than writing my own.