Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
BUG? - PEMSTATUS errors when '4' and prop. not exists
Message
From
10/06/2003 17:26:11
 
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00798596
Message ID:
00798653
Views:
23
Let's say it's been added using addproperty() to the _screen. Checking with '5' instead of '4' will return .t. Now if I check using '4' to see if it is user-defined, I still receive an error, not a false. How do you see if it is user defined without the error occuring?

>Jim,
>
>I don't think it's a bug. If property doesn't exist it's nether intrinisic nor user defined. You should first check if it's exist and only after that see if it's user defined.
>
>>The following 3 commands:
_screen.AddProperty("PrintScr")    && add the property (no error)
>>? PEMSTATUS(_Screen,'Printscr',4)  && returns .T.
>>? PEMSTATUS(_Screen,'xPrintscr',4) && gives error re invalid argument
Interestingly the command following run immediately after returns .F.
? PEMSTATUS(_Screen,'xPrintscr',5)
While it may be (don't know) that a property added by AddProperty is not considered to be "user defined", I don't think that using "4" should generate an error.
>>
>>This occurred in both VFP8 and VFP7SP1. A search of (online) MSKB using "Visual FoxPro 7" and "pemstatus" returned nothing.
.·*´¨)
.·`TCH
(..·*

010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform