Re: OpenField mystery

I’ve seen this too Jacque in the current app I am working on. If I am in a field and I click the “Save” button closeField does not get sent to that field. I will use your solution to get around it. Bob S On Aug 23, 2014, at 14:22 , J. Landman Gay wrote: > On 8/23/2014, 3:02 PM, Graham Samue

Re: OpenField mystery

On 8/25/2014, 5:46 AM, Graham Samuel wrote: For those interested, I have reported the bug below and (separately) the fact that 'openField' can be triggered in surprising circumstances (the subject of my original post under this heading) - which people here have reported as being an ancient quirk

Re: OpenField mystery

For those interested, I have reported the bug below and (separately) the fact that 'openField' can be triggered in surprising circumstances (the subject of my original post under this heading) - which people here have reported as being an ancient quirk of LiveCode, Runtime Revolution and maybe e

Re: OpenField mystery

That's been an issue on Macs forever. If you're in a field and then click a button, the field doesn't lose focus so no closeField is sent. I believe the way to get round it is to "focus on nothing" in the mouseUp code of the button (or the mouseDown). Pete lcSQL Software H

Re: OpenField mystery

I concur. I would never have thought of it. It works very well for me. Thanks Peter Graham On 24 Aug 2014, at 00:24, J. Landman Gay wrote: > On 8/23/2014, 4:10 PM, Peter M. Brigham wrote: >> I have long been annoyed at the default placement of the insertion >> point in the first field when the

Re: OpenField mystery

I think the bug is still there: I just created a stack with one button and one field. I can edit the field and then immediately click the button, but the 'closeField' doesn't fire unless I make it do so explicitly, for example with a 'returnInField' handler, or if the whole stack loses focus and

Re: OpenField mystery

On 8/23/2014, 4:10 PM, Peter M. Brigham wrote: I have long been annoyed at the default placement of the insertion point in the first field when the card is opened (I believe it's not just when the stack gains focus). My solution is to group all the fields and set the traversalon of the group to f

Re: OpenField mystery

On 8/23/2014, 3:02 PM, Graham Samuel wrote: It is quite possible for him (her) not to close the last revised field, but simply to go straight to clicking the button. This means that I can't rely on a 'closeField' message being generated even when a field is modified! Hm, that's an old bug that

Re: OpenField mystery

On Aug 23, 2014, at 4:02 PM, Graham Samuel wrote: > My user is allowed to write stuff into a succession of fields, and then click > on a button to get something done. The 'something' depends on whether any of > the fields have been modified or not. It is quite possible for him (her) not > to cl

Re: OpenField mystery

On Aug 23, 2014, at 3:31 PM, J. Landman Gay wrote: > On 8/23/2014, 12:14 PM, Graham Samuel wrote: >> I have a palette with a lot of objects on it. There are some fields >> and some buttons. I have just realised that when I click on one of >> the buttons, before executing the 'mouseUp' handler for

Re: OpenField mystery

Jacque to the rescue as ever! Thanks, you have nailed it. It's not just annoying, it's a bug - since an error or omission in the documentation is a bug too, as far as I am concerned: I have not seen a description of this very odd behaviour in the Dictionary or elsewhere (of course I could have m

Re: OpenField mystery

On 8/23/2014, 12:14 PM, Graham Samuel wrote: I have a palette with a lot of objects on it. There are some fields and some buttons. I have just realised that when I click on one of the buttons, before executing the 'mouseUp' handler for the button, the engine fires an 'openField' for one of the fi

Re: OpenField mystery

Graham, I'm just speculating... Is one of your fields receiving keyboard focus when the palette receives focus? Do you get the same "openField" for each button press in the palette, or just the first one upon returning to the palette? - Charles On 23 Aug 2014, at 12:14 PM, Graham Samuel wrote: