Message path question working with iPhone Control Kit
mike at doub.com
Sat Dec 17 06:59:30 CST 2011
Making a duplicate of the BehaviourButton of the of the slider control on the (Behaviors) card of the iPhone Control Kit stack and reassigning the behaviour reference to the new button ID seems to have solved the problem.
On 2011-12-17, at 7:48 AM, Michael Doub wrote:
> Ahh, part of the mystery is solved. For each group representing the control, there is a behavior reference in the property inspector. This behavior reference points to the button id of the BehaviourButton on the (Behaviors) card of the iPhone Control Kit stack. This explains the message path.
> Unfortunately, it does not explain why this one control is not receiving the message even though the reference linkage looks correct.
> On 2011-12-16, at 6:00 PM, Michael Doub wrote:
>> I am hoping that someone on the list is familiar with the Andreas Rozek's iPhone Control Kit. (http://22.214.171.124/LiveCode/iPhoneControlKit/index_en.html) I am trying to figure out why the scroller object is not responding to the mouseUp messages. Poking around I found that I can catch the MouseUp message in the BehaviourButton script of the of the appropriate control on the (Behaviors) card of the iPhone Control Kit stack for all controls except the scroller. Although the problem I am chasing is with the scroller, how are the MouseUp messages being routed to the buttons on the (Behaviors) card? There are no MouseUp handlers in most the controls on the MainCard of the iPhone Control Kit card, or in the MainCard script. The scroller is an exception and it looks like it doing normal work. There are not even any MouseUp handlers in the stack script of iPhone Control Kit itself.
>> How are the MouseUp message routed to these controls? I am clearly missing something.
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode