I don't think I expressed myself very well in the bug report you filed... The examples for syntax shouldn't use undocumented / ide functions - as it is misleading.
The ide functions as yet aren't documented but at some point will be as a 'how to write ide components' reference. However, that being said, there are IDE APIs for accessing all information related to widgets so using those is the best approach for such things rather than writing bespoke code that processes their form on disk and in XML files. The best thing to do is to have a look through revidelibrary and revideextensionlibrary. Mark. Sent from my iPhone > On 11 Oct 2015, at 01:23, Mark Wieder <mwie...@ahsoftware.net> wrote: > >> On 10/10/2015 12:44 PM, Peter Haworth wrote: >> >> I'm getting the path to the user extensions folder the same way as >> you. Strange that they'd advise you not to use the official way to get >> those paths, especially the system extensions since it will be different on >> each platform. > > Ah. No, sorry, I meant that the revIDESpecialFolderPath() functions were the > ones I was advised not to use. They're not documented and I get the > impression they may change or disappear with future builds of the IDE / > engine. They're handy, but given that the revEnvironment... functions do the > job neatly I'd stick with them and expect that they'll get documented in time. > > -- > Mark Wieder > ahsoftw...@gmail.com > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
