Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
No - No ... Default!
Message
From
01/09/2006 16:53:05
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01150433
Message ID:
01150446
Views:
28
>The edtbox is subclassed from the bsse class editbox.

The nodefault is there to prevent the native behavior of the control. For programmaticchange the behavior is to assign the value to control's .value - so the value wouldn't be assigned.

Just try to assign a value to this editbox's .value from somewhere in the code, and set step on just before that. Put editbox.value in the watch window and, well, watch. Then try with the nodefault commented out. See whether there's a difference.

Without knowing what the rest of the code in programmaticchange does, I figure the purpose of the nodefault is to prevent the programmatic change from happening, or to completely override it.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform