In the case of oodialog, the best approach would be to cache a reference to the package in a global location or in a control block associated with the event that triggers the need to attach a new thread.
Rick On Sat, Jan 13, 2024 at 1:10 PM Erich Steinböck <erich.steinbo...@gmail.com> wrote: > When a native function package like ooDialog has call-backs which > re-attach through AttachThread() the call-back has just a ThreadContext > available. This makes it difficult for the call-back to search for its own > classes loaded with a ::requires. > > FindClass() is available in a ThreadContext but will only search the REXX > package. > FindContextClass() is unavailable for a ThreadContext. > FindPackageClass(), GetPackagePublicClasses() or similar require a Package > object to search. > ooDialog used to re-load the full ooDialog.cls with LoadPackage which I > think is a bit desperate. > > Is there a decent way to access own classes from a ThreadContext? > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
