On Fri, Aug 14, 2009 at 5:21 PM, Frank Goenninger - Consequor
Consulting AG wrote:
> Am 14.08.2009 um 17:56 schrieb Andy Chambers:
>
>> OK Thanks for checking that out Frank. I must have something else
>> wrong over here.
I think the problem was actually with my Lisp. I changed the test to
have
On Fri, Aug 14, 2009 at 4:50 PM, Frank Goenninger wrote:
> Using your code above I see the following here:
>
> Click on "A" ->
> 0> defcommand > ^on-command b5 nilhitting button: A
OK Thanks for checking that out Frank. I must have something else
wrong over here.
> This comes before any other
Am 14.08.2009 um 17:38 schrieb Andy Chambers:
> On Fri, Aug 14, 2009 at 3:56 PM, Frank Goenninger wrote:
>> Hi Kenny, hi Andy,
>>
>> Am 14.08.2009 um 16:07 schrieb Kenneth Tilton:
>>
>>> I do not have that code over here. Maybe FG committed something.
>>
>> I did. But that just extended the number
On Fri, Aug 14, 2009 at 4:20 PM, Kenneth Tilton wrote:
> That would just leave the problem extant, by finding some other way to
> dispatch commands. I may DL and try myself later. Did you grab from CVS
> recently? Or, better: zip up your copy and send me that so we are looking at
> the same code f
On Fri, Aug 14, 2009 at 3:56 PM, Frank Goenninger wrote:
> Hi Kenny, hi Andy,
>
> Am 14.08.2009 um 16:07 schrieb Kenneth Tilton:
>
>> I do not have that code over here. Maybe FG committed something.
>
> I did. But that just extended the number of Mouse Button Down handlers
> (on-mouse-...). Also I
Hi Kenny, hi Andy,
Am 14.08.2009 um 16:07 schrieb Kenneth Tilton:
> I do not have that code over here. Maybe FG committed something.
I did. But that just extended the number of Mouse Button Down handlers
(on-mouse-...). Also I do not see this behaviour in my Celtk copy. I
always get on-comma
On Fri, Aug 14, 2009 at 3:54 PM, Kenneth Tilton wrote:
> If you now click some place at random do you see "hitting button C"? You
> might have to create a checkbox or something else that is enabled and
> handles mouse events.
No but it does eventually catch up when you close the app down. I adde
I do not have that code over here. Maybe FG committed something. Maybe
if you can describe it better I can figure out what must be going on. I
am not aware of any problems at the core level, but then again I do not
have that code so maybe something new is going on.
kt
Andy Chambers wrote:
> He
