| To: | realbasic-nug@lists.realsoftware.com |
|---|---|
| Subject: | Best way to handle contextual menus |
| From: | "Brian" <bbouch@mcio.org> |
| Date: | Thu, 31 Jul 2008 20:16:59 -0400 (EDT) |
| Authentication-results: | mx.google.com; spf=neutral (google.com: 74.124.194.228 is neither permitted nor denied by best guess record for domain of realbasic-nug-bounces@lists.realsoftware.com) smtp.mail=realbasic-nug-bounces@lists.realsoftware.com |
| Delivered-to: | listarchive@realsoftware.com |
| Importance: | Normal |
| Reply-to: | REALbasic NUG <realbasic-nug@lists.realsoftware.com> |
| Sender: | realbasic-nug-bounces@lists.realsoftware.com |
| User-agent: | SquirrelMail/1.4.10a |
I posted this question yesterday, but I never saw it come to the list, so I am "re-asking"... I have a number of edit fields in my application, all of which I would like the user to be able to right click on and see the basic edit menu options. I understand how to do this, but as it stands right now I need to write a snippet of code on every edit fields MouseClick event to handle this. I'm curious if there is a "better" way to handle this as a default behavior in my app. I don't know much about custom controls, but it sounded like that may be an option?? Or perhaps there is already a solution to this, as it seems like possibly a fairly standard request? - Brian _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: OOP design question, Eric de La Rochette |
|---|---|
| Next by Date: | Re: Best way to handle contextual menus, Terry Ford |
| Previous by Thread: | Select Case and case-sensitive strings?, Tim Jones |
| Next by Thread: | Re: Best way to handle contextual menus, Terry Ford |
| Indexes: | [Date] [Thread] [Top] [All Lists] |