Hey All,
There seems to be a strange bug in celtk. I'm looking into it but wondered if any of you guys had any clues.
Celtk seems to be delaying the evaluation of an "on-command" procedure until the next "on-command" event is generated. You can see this in the example ltktest-ci. If you start that, and click the "Hallo" button, then the "Wald" button, then the "Hallo" button, you'll see what I'm talking about.
I've made a few changes to my local copy so it might just be me but it would be interesting to find out if anyone else can confirm this behaviour.
Cheers, Andy
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:
Hey All,
There seems to be a strange bug in celtk. I'm looking into it but wondered if any of you guys had any clues.
Celtk seems to be delaying the evaluation of an "on-command" procedure until the next "on-command" event is generated. You can see this in the example ltktest-ci. If you start that, and click the "Hallo" button, then the "Wald" button, then the "Hallo" button, you'll see what I'm talking about.
I've made a few changes to my local copy so it might just be me but it would be interesting to find out if anyone else can confirm this behaviour.
Cheers, Andy
cells-devel site list cells-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/cells-devel
No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.54/2300 - Release Date: 08/13/09 06:11:00
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-command fired immediately.
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.
May well be. Do you have a small example, Andy ?
Cheers Frank
On Fri, Aug 14, 2009 at 3:56 PM, Frank Goenningerfrgo@me.com 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 do not see this behaviour in my Celtk copy. I always get on-command fired immediately.
What version of tcl/tk are you using? If you're on 8.4, this could confirm my theory.
My own copy has diverged somewhat from that in CVS so it's equally likely this is a problem of my own making :-)
I sent an example earlier but forgot to CC the list. I'll re-attach it here...
(defmd test-buttons (window) (title$ "My Buttons") (kids (c? (the-kids (mk-stack (:packing (c?pack-self)) (mk-stack () (loop for button-id in '(a b c) collect (let ((id button-id)) (mk-button-ex ((symbol-name id) (format t "hitting button: ~a" id)))))))))))
If you click "A", then "B", then "C", the console will print...
;;nothing when you click "A" "hitting button: A" ;;when you click "B" "hitting button: B" ;;when you click "C"
Am 14.08.2009 um 17:38 schrieb Andy Chambers:
On Fri, Aug 14, 2009 at 3:56 PM, Frank Goenningerfrgo@me.com 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 do not see this behaviour in my Celtk copy. I always get on-command fired immediately.
What version of tcl/tk are you using? If you're on 8.4, this could confirm my theory.
Mac OS X 10.5.8 with Tcl/Tk 8.5.6 (as downloaded from ActiveState).
My own copy has diverged somewhat from that in CVS so it's equally likely this is a problem of my own making :-)
I sent an example earlier but forgot to CC the list. I'll re-attach it here...
(defmd test-buttons (window) (title$ "My Buttons") (kids (c? (the-kids (mk-stack (:packing (c?pack-self)) (mk-stack () (loop for button-id in '(a b c) collect (let ((id button-id)) (mk-button-ex ((symbol-name id) (format t "hitting button: ~a" id)))))))))))
If you click "A", then "B", then "C", the console will print...
;;nothing when you click "A" "hitting button: A" ;;when you click "B" "hitting button: B" ;;when you click "C"
Using your code above I see the following here:
Click on "A" -> 0> defcommand > ^on-command b5 nilhitting button: A
This comes before any other button is pressed ...
So, again, sorry to say: I can't duplicate it here.
Oh - btw - I discovered a "bug" in your on-hover patch: The hover- timer slot in tk.object is defined as ":reader hover-timer" but should be :accessor ... I'm sure you have it ok in your code base...
Cheers Frank
cells-devel site list cells-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/cells-devel
-- Frank Goenninger
Cell: +49 175 4321058 E-Mail: frgo@me.com
On Fri, Aug 14, 2009 at 4:50 PM, Frank Goenningerfrgo@me.com 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 button is pressed ...
So, again, sorry to say: I can't duplicate it here.
Oh - btw - I discovered a "bug" in your on-hover patch: The hover-timer slot in tk.object is defined as ":reader hover-timer" but should be :accessor ... I'm sure you have it ok in your code base...
Hadn't come across that as being a problem but it makes sense. Thanks
Cheers, Andy
-
Andy Chambers -
Frank Goenninger -
Kenneth Tilton