Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Cut and Paste Causing Memo Corruption
Message
From
31/10/2004 17:32:07
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
00956032
Message ID:
00956340
Views:
14
>Hi Dragan,
>
>That seems to be the best solution. I have tried it from several sources and it works a treat.
>
>As far as the Copy and Paste modes are concerned, should I turn the option off? It seems a bit backward to do so, as the user does have to get the browse and my application along side each other to perform the drag and drop.
>
>Lisa Nicholls also suggested checking for certain characters [smart quotes - CHR(147) and CHR(148)], which I may also incorporate.

Somewhere in the bowels of old Fox kernel (if the beast may be described in those words), there's a certain sensitivity towards characters in the 129-159 range, as they can be viewed as chr(1)-chr(31) with eight bit set. The chr(141) (i.e. carriage return with 8th bit set) has a special position, because it was once the "soft return" used in FoxPlus's code editor.

Though, memo binary shouldn't be sensitive to anything at all, it should simply allow any character. However, that's true in replace, insert or append memo; don't know if the text may undergo some transformation when it's pasted into an editbox.

You may try to trap ctrl+v in editbox.keypress (though I'm not sure that'll work) and then just
nodefault
{do any filtering of _cliptext here}
this.seltext=_cliptext

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