I read from the Dictionary under closeField: "The closeField message is not 
sent when a handler changes the field's contents using the put command.”

May I submit that it ought to? An edited field is an edited field, and when it 
loses focus, if the contents are not what they were when it was opened, 
closeField *ought* to be sent! 

At any rate, I do not think there is a message I can send the the field to let 
it know the contents have changed. I am probably going to have to recode for 
textChanged. 

Bob S


On Sep 13, 2014, at 17:55 , Bob Sneidar <bobsnei...@iotecdigital.com> wrote:

> Hi all.
> 
> As many know, creating a custom menu set on OS X (not sure about Windows) 
> will typically add the File and Edit menus to your customer menu set. This 
> has the net effect of *disabling* cut/copy/paste/clear. I can live with that, 
> because I have scripted the necessary menus to mimic the behaviors of those 
> actions, but I am finding some quirks. 
> 
> First, if I cut or paste something in a field then tab out, closeField is not 
> triggered. I assumed this was because the field was not getting 
> selectionChanged, so I sent selectionChanged to the focusedObject after the 
> cut/copy operations. Still, closeField does not get sent when I tab out of 
> it. closeField DOES get sent if I simply edit the field then tab out. 
> 
> So what gets sent to the engine exactly that lets it know that the contents 
> of a field have changed, so that tabbing out generates the proper closeField 
> message? 
> 
> I suppose I could use textChanged to work around it, but frankly I would have 
> to go through all my scripts which send a closeField to this object, and I’d 
> rather not mess with what is already working. 
> 
> Bob S


_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to