How about having an extra text field in Jucer for each graphic element and component for a line of custom code / function call)? If used, Jucer would simply add that piece of code right after they’re created in the parent constructor or in the paint method. Which I could use for my embedded fonts
eventually, one could specify fonts as resources, and embed them in jucer components like the other images… when you create a text field, it have a combobox to let you select your embedded font.
I like spiderman’s suggestion though.
We use the Jucer a lot, and quite a few times we have similar problems.
We just want to add a little bit of code inside Jucer generated code.
Offering a tag like //[UserCode] which you can everywhere you want would be a nice addition.
don’t think that’d be possible - if a tag is in the middle of a pile of auto-generated code, and then that generated code changes, how could it figure out where to replace the tag?
[quote=“jules”]
don’t think that’d be possible - if a tag is in the middle of a pile of auto-generated code, and then that generated code changes, how could it figure out where to replace the tag?[/quote]
Yes, that’s exactly the problem. And that’s why I decided to subclass the LookAndFeel class and do as much as I can there (about embedded fonts, I mean). I think it’ a fairly clean and Juce-friendly way of doing this. But the problem with the Jucer generated graphics still remains.