On Sun, Jul 3, 2011 at 12:42 PM, <[email protected]> wrote:
> **
> > The .constDir or the dialog objects constDir attribute *do not* have
> anything to do with .h file names. Providing a file name, is simply a way
> to add symbols to the .Directory object, implemented by ooDialog. It is
> convenient, for ooDialog, because resource editors in general maintain a
> separate file to define symbolic constants.
>
> Ah-ha! I misunderstood. I thought the filename was the index in the
> directory, and that the file would be read when the symbols were needed. Now
> I understand that when you do
> .application~useGlobalConstDir(..)
> the symbols and their numbers are extracted from the .h file, and stored in
> the directory object. Thus invoking ~useGlobalConstDir merely extracts the
> symbols/numbers from the provided .h file and adds them to the directory.
>
> I checked the ooRexxRef for the Directory class - seems that indexes are
> unique - so if I have two .h files, and the first has (say)
> IDC_EDIT 21
> and the second has:
> IDC_EDIT 32
> then after the second .h file is added to the ClobalConstDir, then there
> will be a single entry for IDC_EDIT with a numeric ID of 32.
>
Yes, exactly.
That's why I said in one of the other e-mails:
"Another drawback could be that the global .constDir is global to the
application. Which means that duplicate symbols with different numeric
values can not be used. I.e., if you have dialog A with symbol IDD_DIALOG1
== 100 and dialog B with symbol IDD_DIAOLG1 == 200, this will not work using
the global .constDir. (Or rather you could do it, but your outcome is
indeterminate.)"
--
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
