Generating a recent Linux 3.2gamma VM with VMMaker-3-2-version5.5.cs ConsolidateTo4744-JMM.4.cs 3.2-4743 #1 [oss audio, xshm] Tue Mar 5 17:50:35 CET 2002 gcc 2.95.4 actual SF sources gives a bad event handling: mouse button presses only work after *moving* the mouse thereafter! If you click e.g. a collapse button it becomes darker, but the window collapses just after moving the mouse then. This is new compared with older VMs.
Greetings,
Stephan
I see this one as well, it appears that the mouseup event doesn't register until the mouse is moved. For example, if I click in the gutter of a scroll bar without moving the mouse it scrolls continuously until I either move the mouse or it reaches the endpoint.
Ken
On Tue, 2002-03-05 at 11:33, Stephan Rudlof wrote:
Generating a recent Linux 3.2gamma VM with VMMaker-3-2-version5.5.cs ConsolidateTo4744-JMM.4.cs 3.2-4743 #1 [oss audio, xshm] Tue Mar 5 17:50:35 CET 2002 gcc 2.95.4 actual SF sources gives a bad event handling: mouse button presses only work after *moving* the mouse thereafter! If you click e.g. a collapse button it becomes darker, but the window collapses just after moving the mouse then. This is new compared with older VMs.
Greetings,
Stephan
Stephan Rudlof (sr@evolgo.de) "Genius doesn't work on an assembly line basis. You can't simply say, 'Today I will be brilliant.'" -- Kirk, "The Ultimate Computer", stardate 4731.3
Ken Causey ken@ineffable.com is claimed by the authorities to have written:
I see this one as well, it appears that the mouseup event doesn't register until the mouse is moved. For example, if I click in the gutter of a scroll bar without moving the mouse it scrolls continuously until I either move the mouse or it reaches the endpoint.
Ok, so who has done what to sqX11Windows.c recently? Hmm, SF says Lex & Bert have been torturing those poor innocent bits recently, including apparently some areas to do with event handling. I point the finger of suspicion at...
Colonel Mustard in the Maids Bedroom with the EggBeater!
Er, no maybe not. Lex? Bert? Is there something you should tell us?
tim
On Tue, 5 Mar 2002, Tim Rowledge wrote:
Ken Causey ken@ineffable.com is claimed by the authorities to have written:
I see this one as well, it appears that the mouseup event doesn't register until the mouse is moved. For example, if I click in the gutter of a scroll bar without moving the mouse it scrolls continuously until I either move the mouse or it reaches the endpoint.
Ok, so who has done what to sqX11Windows.c recently? Hmm, SF says Lex & Bert have been torturing those poor innocent bits recently, including apparently some areas to do with event handling. I point the finger of suspicion at...
Isn't a log nice? ;-)
Colonel Mustard in the Maids Bedroom with the EggBeater!
Almost correct :)
Indeed, I had to touch the stuff for the Browser Plugin update, and Lex thought it was finally time to clean some things up in the event section - did someone notice that alt-. doesn't bring up *two* debuggers anymore?
Er, no maybe not. Lex? Bert? Is there something you should tell us?
No. Why? It was fixed almost an *hour* ago! I reported the buglet to Lex today (privately). Run, don't walk, to your nearest CVS outlet for a nice update shot!
-- Bert
Wow, this was fast! It works for me now.
Seems that I have hitted a small gap between two working versions...
But:
Bert Freudenberg wrote:
On Tue, 5 Mar 2002, Tim Rowledge wrote:
Ken Causey ken@ineffable.com is claimed by the authorities to have written:
I see this one as well, it appears that the mouseup event doesn't register until the mouse is moved. For example, if I click in the gutter of a scroll bar without moving the mouse it scrolls continuously until I either move the mouse or it reaches the endpoint.
Ok, so who has done what to sqX11Windows.c recently? Hmm, SF says Lex & Bert have been torturing those poor innocent bits recently, including apparently some areas to do with event handling. I point the finger of suspicion at...
Isn't a log nice? ;-)
Colonel Mustard in the Maids Bedroom with the EggBeater!
Almost correct :)
Indeed, I had to touch the stuff for the Browser Plugin update, and Lex thought it was finally time to clean some things up in the event section - did someone notice that alt-. doesn't bring up *two* debuggers anymore?
Er, no maybe not. Lex? Bert? Is there something you should tell us?
No. Why? It was fixed almost an *hour* ago! I reported the buglet to Lex today (privately).
How large was the gap? The changelog says about one day...
Do we need test pilots for big SF changes? Or am I one of them... Aehem, I think so ;-)
But issuing such bug reports to the list, too, would help avoiding second ones...
Run, don't walk, to your nearest CVS outlet for a nice update shot!
-- Bert
Greetings,
Stephan
Stephan Rudlof wrote:
Wow, this was fast! It works for me now.
Possibly I've been too fast with my success message, possibly not...
Now the middle button of my 3-button mouse gives the halos: is this intended behaviour?
Before the halos have been evoked by the third one and the middle one has given the menues, now they are switched.
Greetings,
Stephan
Seems that I have hitted a small gap between two working versions...
But:
Bert Freudenberg wrote:
On Tue, 5 Mar 2002, Tim Rowledge wrote:
Ken Causey ken@ineffable.com is claimed by the authorities to have written:
I see this one as well, it appears that the mouseup event doesn't register until the mouse is moved. For example, if I click in the gutter of a scroll bar without moving the mouse it scrolls continuously until I either move the mouse or it reaches the endpoint.
Ok, so who has done what to sqX11Windows.c recently? Hmm, SF says Lex & Bert have been torturing those poor innocent bits recently, including apparently some areas to do with event handling. I point the finger of suspicion at...
Isn't a log nice? ;-)
Colonel Mustard in the Maids Bedroom with the EggBeater!
Almost correct :)
Indeed, I had to touch the stuff for the Browser Plugin update, and Lex thought it was finally time to clean some things up in the event section - did someone notice that alt-. doesn't bring up *two* debuggers anymore?
Er, no maybe not. Lex? Bert? Is there something you should tell us?
No. Why? It was fixed almost an *hour* ago! I reported the buglet to Lex today (privately).
How large was the gap? The changelog says about one day...
Do we need test pilots for big SF changes? Or am I one of them... Aehem, I think so ;-)
But issuing such bug reports to the list, too, would help avoiding second ones...
Run, don't walk, to your nearest CVS outlet for a nice update shot!
-- Bert
Greetings,
Stephan
Stephan Rudlof (sr@evolgo.de) "Genius doesn't work on an assembly line basis. You can't simply say, 'Today I will be brilliant.'" -- Kirk, "The Ultimate Computer", stardate 4731.3
On Tuesday 05 March 2002 02:54 pm, Stephan Rudlof wrote:
Now the middle button of my 3-button mouse gives the halos: is this intended behaviour?
Before the halos have been evoked by the third one and the middle one has given the menues, now they are switched.
Cool! someone finally fixed it <g>...
On Tue, 5 Mar 2002, Stephan Rudlof wrote:
How large was the gap? The changelog says about one day...
Yes, there is some delay because Lex and I live in different time zones.
Do we need test pilots for big SF changes? Or am I one of them... Aehem, I think so ;-)
But issuing such bug reports to the list, too, would help avoiding second ones...
I remember seeing a doc on how to set up automatically mailing of commit notifications from CVS. If it is agreed that this wouldn't clutter the list too much that might be a good idea. Alternatively, we could use a separate mailing list for that (SourceForge provides mailing lists).
-- Bert
Bert Freudenberg wrote:
On Tue, 5 Mar 2002, Stephan Rudlof wrote:
How large was the gap? The changelog says about one day...
Yes, there is some delay because Lex and I live in different time zones.
Do we need test pilots for big SF changes? Or am I one of them... Aehem, I think so ;-)
But issuing such bug reports to the list, too, would help avoiding second ones...
I remember seeing a doc on how to set up automatically mailing of commit notifications from CVS.
My point here was mailing *bug* reports - like your private one to Lex - to the list, too; not commits. This privacy has led to the work of making a second bug report by me.
Greetings,
Stephan
If it is agreed that this wouldn't clutter the list too much that might be a good idea. Alternatively, we could use a separate mailing list for that (SourceForge provides mailing lists).
-- Bert
Just a note that this one seems to be cleared up in Lex's latest Debian vm package 3.2.4743-2. Unfortunately it looks like some debugging output was left in so you get a spew of event debugging to stdout. Nothing a little >/dev/null can't take care of though.
Ken Causey
On Tue, 2002-03-05 at 12:20, Ken Causey wrote:
I see this one as well, it appears that the mouseup event doesn't register until the mouse is moved. For example, if I click in the gutter of a scroll bar without moving the mouse it scrolls continuously until I either move the mouse or it reaches the endpoint.
Ken
On Tue, 2002-03-05 at 11:33, Stephan Rudlof wrote:
Generating a recent Linux 3.2gamma VM with VMMaker-3-2-version5.5.cs ConsolidateTo4744-JMM.4.cs 3.2-4743 #1 [oss audio, xshm] Tue Mar 5 17:50:35 CET 2002 gcc 2.95.4 actual SF sources gives a bad event handling: mouse button presses only work after *moving* the mouse thereafter! If you click e.g. a collapse button it becomes darker, but the window collapses just after moving the mouse then. This is new compared with older VMs.
Greetings,
Stephan
Stephan Rudlof (sr@evolgo.de) "Genius doesn't work on an assembly line basis. You can't simply say, 'Today I will be brilliant.'" -- Kirk, "The Ultimate Computer", stardate 4731.3
squeak-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
Ken Causey -
Ned Konz -
Stephan Rudlof -
Tim Rowledge