[quote=“abishur”][quote=“pturmel”] I’m going to go out on a limb here and guess that the undocumented features are undocumented because a programmer has to have some grasp of java and swing to use them safely.[/quote]I obviously think that’s asinine the fact that there are abbreviations for existing methods (but the non-abbreviate methods also work) is exactly what I’m talking about. I completely missed that one page that talked about one specific usage example precisely because there is no centralized page that discusses common scripting methods for specific elements. It’s too decentralized and makes fully utilizing the underlying power of Ignition difficult for newcomers to Java like myself.[/quote]I strongly disagree about the safety of using the underlying java, particularly the material discovered via reflection. It is absurdly easy to crash the designer or client, or corrupt the project you’re working on so you can’t open it again. Pretty good reasons in my book for IA to leave it to the forum. I’ve attached warnings to some of the techniques I’ve posted on these forums because I’ve been there and done that.
IA has documented the very few common (supported) scripting methods in the manual section I linked. There simply isn’t anything else common except for the Swing stuff underneath. IA has substantial detail on per-component properties and methods in the appendix I pointed out, which you also seem to have missed. I’m not going to say IA’s manual has everything I think should be there, but they’ve chosen what techniques they want to support.[quote=“abishur”]Even for experienced Java users I fail to see why such a help page would be a bad thing or something you’d want to resist?[/quote]Experienced java users actually read javadocs, a standardized documentation system. My pointer to the Swing part of Oracle’s javadocs answers your questions about common methods that IA left out of their manual. Why should IA re-document what Oracle displays publicly to all who visit? (But copyrighted – so no importing into IA’s manual, except for tiny fair-use snippets.)[quote=“abishur”]I mean what benefit is there in saying, “Well the methods are spread out through the existing help document, but you have know what they’re called to find them, so let’s keep things the way they are?” instead of saying “Hey, yeah, a single page for each individual component under the advanced scripting section would be extremely useful for rapidly referencing of supported methods” [/quote]You’re asking for a magic cheat sheet. Sorry, it’s not that simple. The methods are spread out because they differ from component to component, as I’ve pointed out. There’s no need to document all the getters and setters because you don’t need them in Jython – you have the corresponding property to use.
Understanding Swing, even a little, would answer your questions. I’ve suggested some reading towards that end, and Mark has suggested some other reading towards that end. Mark is clearly nicer than I am, or you’ve just managed to push my buttons, so I think I’ll let others carry this topic forward.