Re: [flexcoders] Preventing cutpaste in Flex3 application

2008-09-16 Thread Daniel Freiman
I don't think you can disable the cut/paste menus. But you can disable/cancel the functionality. I'd play around with the keydown and change events of the UITextField. If the control key is down in the active in the keydown event, save the current htmltext of the textfield and reset the text to

Re: [flexcoders] Preventing cutpaste in Flex3 application

2008-09-16 Thread Paul Andrews
OK, I'm curious. Why don't you want users to cut and paste? I'd be pretty fed up if I was using an application that wouldn't let me paste into an input field. Paul - Original Message - From: justincase772 [EMAIL PROTECTED] To: flexcoders@yahoogroups.com Sent: Tuesday, September 16,

Re: [flexcoders] Preventing cutpaste in Flex3 application

2008-09-16 Thread Tom Chiverton
On Tuesday 16 Sep 2008, justincase772 wrote: Hello everybody. As dumb as it might sound, I need to disable cutpaste in a flex3 web application, You're right, it sounds dumb - what's the use case ? -- Tom Chiverton Helping to elementarily unleash cross-platform channels

Re: [flexcoders] Preventing cutpaste in Flex3 application

2008-09-16 Thread Michael Schmalle
Doesn't sound that dumb, what if it was copyright issues? I know they could take screenshots but that is the first thing I thought of. If you don't want people to right click in the text area, make a subclass that puts a transparent modal sprite over the bounding box of the text field minus what

Re: [flexcoders] Preventing cutpaste in Flex3 application

2008-09-16 Thread Andrew Wetmore
The users of my app get nervous because it seems as if they can highlight and delete the text from the screens. If they changeState and come back, the text is back, but they don't know that the first time through. I would love to disable this behavior without affecting the display of the text

RE: [flexcoders] Preventing cutpaste in Flex3 application

2008-09-16 Thread Jim Hayes
Set selectable = false ? or editable = false ? Or have I missed something? -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Wetmore Sent: 16 September 2008 15:30 To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Preventing cutpaste

Re: [flexcoders] Preventing cutpaste in Flex3 application

2008-09-16 Thread Michael Schmalle
yeah, didn't think of that, I was on the wrong wave. My solution wouldn't be one for this. Seems like you would have to do something like if a key stroke was recordred, blah blah. Yeah this is complicated. ;-) Mike On Tue, Sep 16, 2008 at 10:30 AM, Andrew Wetmore [EMAIL PROTECTED]wrote:

Re: [flexcoders] Preventing cutpaste in Flex3 application

2008-09-16 Thread Andrew Wetmore
editable = false doesn't seem to do the trick. I will try selectable = false. -- Andrew Wetmore User Experience Director Open Learning Exchange - www.ole.org 978-319-7324

Re: [flexcoders] Preventing cutpaste in Flex3 application

2008-09-16 Thread Andrew Wetmore
selectable = false seems to work, although the context menu still offers Select all (although nothing happens that I can see). This is curious behavior that only occurs on some of my text areas, where you can seem to edit the text in a way that you aren't intended to be able to. a On Tue, Sep

RE: [flexcoders] Preventing cutpaste in Flex3 application

2008-09-16 Thread Battershall, Jeff
Subject: Re: [flexcoders] Preventing cutpaste in Flex3 application selectable = false seems to work, although the context menu still offers Select all (although nothing happens that I can see). This is curious behavior that only occurs on some of my

Re: [flexcoders] Preventing cutpaste in Flex3 application

2008-09-16 Thread Andrew Wetmore
Yes. I need to write about 15 context menus for various states in the app, and use a generic menu elsewhere. On my to-do list. a -- Andrew Wetmore User Experience Director Open Learning Exchange - www.ole.org 978-319-7324

Re: [flexcoders] Preventing cutpaste in Flex3 application

2008-09-16 Thread Tom Chiverton
On Tuesday 16 Sep 2008, Michael Schmalle wrote: Doesn't sound that dumb, what if it was copyright issues? What if it was ? /me points at defectivebydesign.org This should effectively eat the mouse interaction of the underlying The user can still tab to the control and then use the keyboard