David,
I have no way to determine what popup is defined or not other then DISPLAY MEMO. IOW I've skipped the idea.
For your question regarding the texts in the display memo.
You can test yourself
create a little exe that does nothing more then DISPLAY MEMORY TO FILE
cFileon the MS explorer create a link to this exe
alter the link and add parameters to the exe
your.exe -L%CommonProgramFiles%\Microsoft Shared\VFP\VFP8RDEU.DLL
run it, check the
cFile for the text ,alter the link for the next runtime and so on.
if the code above fails replace %CommonProgramFiles% with the return of getenv('CommonProgramFiles')
HTH
Agnes
>Thanks Agnes! Didn't even think of that!
>
>Do you know if 'Popup' and 'Popups' is included in every language runtime? Then I can just check for "Popup" $ my_line_string
>or "Popups" .
>
>Regardless though, I am really hoping to find a better way to do this. One way would be to programmatically iterate through every menu choice - e.g. - assume that the menu is _msysmenu (which it is in my case) - get the pad names
>then ACTIVATE MENU _msysmenu PAD (padname).
>At that point I should be able to call 'popup()' and it should return the name of the current popup. No? But popup() is not behaving the way I expect it to. It always returns an empty string()
>
>
>
>
>>Hi David,
>>
>>as long as you use the english runtime it will work. as soon as you use something different (lets say your exe runs on my comp) it might fail:
>>[snip]
>>
>>_WRAP Global L .F.
>>
>> 81 Systemvariablen definiert
>>
>>Menü- und Blockdefinitionen
>>
>> 0 Menüs definiert
>>
>>Popup-Definitionen
>>
>> 0 Popups definiert
>>
>>Fensterdefinitionen
>>
>>[/snip]
>>
>>Agnes
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord
Weeks of programming can save you hours of planning.
OffThere is no place like [::1]