Ref Exercise04a - I had tried the change you made, and it worked fine, but
many thanks for committing it.
I think I'm confused because I thought you had said (several days ago) that
previously-working RcDialogs - i.e ones that used symbolic IDs but of course
without ~useGlobalConstDir - should *continue* to work. Thus I was trying to
get Exercise04a working again *without* using the GlobalConstDir. I now
understand that that is not possible. Please tell me I've got it straight
now <grin>.
If this is correct, then I have to change Chapter 4 to explain about
.Application and its ~useGlobalConstDir method, which I'd have preferred not
to do so early in the Guide.
Many thanks,
Oliver
_____
From: Mark Miesfeld [mailto:[email protected]]
Sent: 03 July 2011 18:32
To: Open Object Rexx Users
Subject: Re: [Oorexx-users] Global ConstDir and RcDialog Menu
On Sun, Jul 3, 2011 at 11:48 AM, <[email protected]> wrote:
There are two problems:
Zero problems now. <grin>
(1) The most important is that Exercise04a in the Guide was working fine
with the previous release of ooDialog 4.2, but does not work the latest
release. I've made no changes. It's an RcDialog, uses symbolic IDs, and does
not use the .Application class. So either there's a bug in ooDialog, or
there's a chnage in ooDialog such that I need to update Exercise04a.
I just committed a change that fixes Exercise04a. Do a svn update to pull
in that change.
(2) You said that for ScriptMenuBar I should add stuff into the .rc file in
order to use numeric IDs.
No, I said if you want to use numeric IDs in the Rexx code, you have to use
numeric IDs in the resource script file.
Personally, I wouldn't use numeric IDs, it is too hard in your program code
to remember exactly what 4014 is. It is too hard for some one else to read
the code and understand what it is doing.
The changes I made to ooDialog require only a very minimal change to any
existing 4.2.0 programs that use menus. There are only about 2 programs
that fit that category in the entire world. You are simply misunderstanding
something basic here. Once the light bulb goes on you will realize that.
Do you happen to know if I can get resEdit to do that? If not, I'd prefer
not to tell readers of the Guide that they need to change the .rc file
manually. I'd prefer to skip that option alltogether - stick with symbolic
IDs at least for RcDialog classes.
Yes, you should stick with symbolic IDs. I'm not sure about resEdit, there
should be a way, but maybe not. It is not a normal thing to do.
PS: Is there a way for me to find out what the build number of my installed
ooDialog 4.2 is?
Use .DlgUtil~version('S') as in:
say 'Version:' .DlgUtil~version('s')
::requires 'ooDialog.cls'
and you will see something like:
Version: 4.2.0.7017
That is the build number.
--
Mark Miesfeld
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Oorexx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-users
