This is a change of behaviour between 4.1.0 and 4.2.3
6.03 16 May 2012
ooDialog:126.96.36.19948 (an ooRexx Windows Extension)
Windows 7 pro 32bit
If a userdialog subclass has a method defined with sub-keyword private then it cannot call it in 4.2.3 whereas it can in a previous version
I receive the message 'xxxxx is not a method of an yyyyy'
Removing the 'PRIVATE' sub-keyword from the xxxxx method directive resolves this, as does falling back to previous version of ooDialog.
I attach a simple test case script - pressing the private button should show 'Private method running'
I have not tested intermediate versions of ooDialog, so this behaviour may have been introduced at an earlier stage.