[repository.lp.se #107] Multiple Bugs found on ctwm 3.7a5 (from cvs)
OK, a recap on this one: [EMAIL PROTECTED] - Thu Feb 24 05:08:30 2005]: Bugs Found... * ExMH Icon window miss-positioned after WS switch I believe this is resolved. * Random Placement is NOT random. This is still to be resolved. * Selecting f.move or f.resize (and most other 'window operation' functions) from a root menu, just fails. This IS resolved. * Selecting resize from a menu attached to a titlebar works but if you just click to cancle, without moving the cursor, or even hitting the edge you wish to resize results in... 1/ window is moved border thickness +1 down and right 2/ window size is also increased a bit, even though it was cancled. Is this one resolved? /Richard
[repository.lp.se #107] Multiple Bugs found on ctwm 3.7a5 (from cvs)
[EMAIL PROTECTED] - Tue Apr 19 08:37:01 2005]: On Tue, Apr 19, 2005 at 08:17:59AM +0200 I heard the voice of Richard Levitte via RT, and lo! it spake thus: [EMAIL PROTECTED] - Thu Feb 24 05:08:30 2005]: * Random Placement is NOT random. This is still to be resolved. Well, speaking purely for myself, I *LIKE* the predictable placement. I guess random is overstating it a bit, but it's awful convenient having them cascade like that, especially when I do something that's going to open 20 or 30 windows in a row. Do you actually get that behavior with 3.7a6? Anthony's complaint is that two xterms in a row will have them at the exact same spot. /Richard
Re: [repository.lp.se #107] Multiple Bugs found on ctwm 3.7a5 (from cvs)
On Tue, Apr 19, 2005 at 11:28:58AM +0200 I heard the voice of Richard Levitte via RT, and lo! it spake thus: [EMAIL PROTECTED] - Tue Apr 19 08:37:01 2005]: Well, speaking purely for myself, I *LIKE* the predictable placement. Do you actually get that behavior with 3.7a6? Anthony's complaint is that two xterms in a row will have them at the exact same spot. I just fired up 8 terms in a row (xterm ; xterm ; etc) and they cascaded normally. I s'pose there could be a race condition in the timing somewhere that my machine isn't fast enough to hit, but I've never seen it happen, even when popping up 20 or 30 cities at a time in Freeciv. I think Anthony just abused ctwm in a previous life, and it's taking revenge now 8-} -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
[repository.lp.se #107] Multiple Bugs found on ctwm 3.7a5 (from cvs)
[EMAIL PROTECTED] - Tue Apr 19 08:37:01 2005]: On Tue, Apr 19, 2005 at 08:17:59AM +0200 I heard the voice of Richard Levitte via RT, and lo! it spake thus: [EMAIL PROTECTED] - Thu Feb 24 05:08:30 2005]: * Random Placement is NOT random. This is still to be resolved. Well, speaking purely for myself, I *LIKE* the predictable placement. I guess random is overstating it a bit, but it's awful convenient having them cascade like that, especially when I do something that's going to open 20 or 30 windows in a row. Do you actually get that behavior with 3.7a6? Anthony's complaint is that two xterms in a row will have them at the exact same spot. /Richard
[repository.lp.se #107] Multiple Bugs found on ctwm 3.7a5 (from cvs)
[levitte - Tue Apr 19 13:42:33 2005]: [EMAIL PROTECTED] - Tue Apr 19 11:48:48 2005]: On Tue, Apr 19, 2005 at 11:28:58AM +0200 I heard the voice of Richard Levitte via RT, and lo! it spake thus: [EMAIL PROTECTED] - Tue Apr 19 08:37:01 2005]: Well, speaking purely for myself, I *LIKE* the predictable placement. Do you actually get that behavior with 3.7a6? Anthony's complaint is that two xterms in a row will have them at the exact same spot. I just fired up 8 terms in a row (xterm ; xterm ; etc) and they cascaded normally. I s'pose there could be a race condition in the timing somewhere that my machine isn't fast enough to hit, but I've never seen it happen, even when popping up 20 or 30 cities at a time in Freeciv. I think Anthony just abused ctwm in a previous life, and it's taking revenge now 8-} I think you're being too hard on Anthony, especially because I found out what's happening. If you have RandomPlacement and DontMoveOff in your .ctwmrc, you will see a similar behavior. Basically, I'd say that the code to handle DontMoveOff in AddWindow (add_window.c) is completely and utterly bogus. For any window that's much smaller than the screen, the placement will be +50+50, period. That's astonishingly wacked. I do recall fiddling with that code, so I'm probably the one to blame as well... /Richard OK, I've just committed a fix that corrects this misbehavior. /Richard
[repository.lp.se #101] GotoWorkSpaceByNumber with incorrect argument in events.c
Resolving this ticket, since there hasn't been much discussion about it. If the solution is broken, please submit a new bug report. [levitte - Wed Jun 16 19:22:12 2004]: In message [EMAIL PROTECTED] on Wed, 16 Jun 2004 10:37:06 -0400, Rudolph T Maceyko [EMAIL PROTECTED] said: rm55 --On Wednesday, June 16, 2004 16:19:20 +0200 Richard Levitte via RT rm55 [EMAIL PROTECTED] wrote: rm55 rm55 In events.c, there's the following call to GotoWorkSpaceByNumber(): rm55 rm55GotoWorkSpaceByNumber (/* X */ NULL, Event.xclient.data.l[0]); rm55 rm55 The first argument should not be NULL, it should be a virtual screen, rm55 but I'm not at all sure what should be given here. rm55 rm55 Scr-currentvs should work--for a single display. I don't know what to rm55 do for multiple displays. OK, I've committed that change. /Richard
[repository.lp.se #108] [Anthony's wish list] RandomPlacement styles
[This was originally part of entry #107, submitted by Anthony Thyssen [EMAIL PROTECTED]] I'd love to specify some RandomPlacement styles. Currently windows are placed +30+30 from the last random placment. Eg: next window is below and to right of previous random placement. I'd love to specify things like -22+22 (eg next window is only below but to left of previous window. This way only the title bar is visible, but the stair case ensures the first LeftTitleButton button (with NoDefaults) is always visible, no matter how I resize.
[repository.lp.se #110] [Anthony's wish list] Better info in the info window
[This was originally part of entry #107, submitted by Anthony Thyssen [EMAIL PROTECTED]] The 'information' popup windows gives placement of the real window, but does not give the information displayed during moves and resizes. It would also be nice to have the negitive position offset for this display. This is the information that is needed for geometry arguments when starting the application, and is often the more usefull information.
