On Sat, May 28, 2011 at 4:46 PM, <[email protected]> wrote:
> I was checking the params for .ScripMenuBar in the code > (https://oorexx.svn.sourceforge.net/svnroot/oorexx/main/trunk/extensions/pla > tform/windows/oodialog/oodMenu.cpp) and noticed that the params do not seem > to match those that I'm currently using (and which work ok). Am I > mis-reading something? Or is a change in store? Yes, this is a change. Since the menu classes have never been released, I can still change the interface. There is going to be a global constDir. The menu classes will use the global constDir to resolve symbolic IDs. The code to make this work, has already been checked into main, but I have not yet created a new version of switchOODialog. When, I release the next beta ooDialog 4.2.0, you will need to use the new parameters. The change / refactoring will allow symbolic resource IDs to be used with classes that are not dialog classes. (Such as menus.) > Can I assume a future build of ooDialog will require me to change my code? > No problem in that, but would be useful to know roughly when the change may > occur. I'm trying to get a new ooDialog beta released around June 1. -- Mark Miesfeld ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Oorexx-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-users
