File: TODO

package info (click to toggle)
lwm 1.01-3
  • links: PTS
  • area: main
  • in suites: woody
  • size: 228 kB
  • ctags: 592
  • sloc: ansic: 1,884; makefile: 495; sh: 6; tcl: 6
file content (120 lines) | stat: -rw-r--r-- 4,985 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
allow users to back out of closing a window if
they leave the box before letting go of the button.

change the pointer when the mouse is over various
parts of the frame _before_ a button is pressed?

fix the bug that causes GTK+ apps to leave a black
window lying around if lwm is killed and restarted
while they're running.


 ****


Return-Path: <marty@cosray2.wustl.edu>
Received: from mail.core.genedata.com (mentolat-e1.core.genedata.com [157.161.173.40])
	by relay.ch.genedata.com (8.9.3/8.9.3) with ESMTP id VAA1089586
	for <Elliott.Hughes@ch.genedata.com>; Fri, 12 Nov 1999 21:54:46 +0100 (CET)
Received: (from mail@localhost)
	by mail.core.genedata.com (8.10.0.Beta6/8.10.0.Beta6) id dACKsjv11567
	for <Elliott.Hughes@genedata.com>; Fri, 12 Nov 1999 21:54:45 +0100
Received: from cosray2.wustl.edu(128.252.125.242) by mentolat-e0.core.genedata.com via smap (V2.1)
	id xma011563; Fri, 12 Nov 99 21:54:36 +0100
Received: (qmail 11208 invoked from network); 12 Nov 1999 20:54:32 -0000
Received: from cris.wustl.edu (128.252.35.196)
  by cosray2.wustl.edu with QMQP; 12 Nov 1999 20:54:32 -0000
Date: Fri, 12 Nov 1999 14:54:32 -0600
From: Marty Olevitch <marty@cris.wustl.edu>
To: elliott <Elliott.Hughes@genedata.com>
Subject: lwm
Message-ID: <19991112145432.A10363@cris.wustl.edu>
References: <34D9E620.188125A5@genedata.com> <19980205101820.03939@cosray2.wustl.edu> <34D9EC0C.F5A880C1@genedata.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre4i
In-Reply-To: <34D9EC0C.F5A880C1@genedata.com>; from Elliott.Hughes@genedata.com on Thu, Feb 05, 1998 at 05:42:52PM +0100
Status:   

Hi Elliott,

I've run into a problem that involves lwm and tcl/tk 8.0.5.

When a menu is posted in tk by clicking on a menubutton, the menu does not
appear just below the menubutton as it should. It appears where it would
be if the menubutton happened to be at the upper left corner of the screen
(+0+0). Does this make sense? However, if the menubutton is moved a little
bit (using button 2 on its frame), then the menu will post correctly.

The problem doesn't appear in an earlier version of tk. However, the
problem also doesn't appear using other window managers, namely twm and
flwm. So, it looks like it is some combination of lwm and tk8.0.5. The same
thing occurs using any of Solaris 5.5, Solaris 7, or Linux Redhat 6.0.

Do you have any idea how to fix this?

Now, if you happen to use tcl/tk or want to go through the trouble of
installing it (or have access to a machine with it), here is a small
script that demonstrates the problem:

    #!/usr/bin/wish
    menubutton .mb -text menu
    pack .mb
    menu .mb.menu
    .mb configure -menu .mb.menu
    .mb.menu add command -label {quit} -command {destroy .}
    .mb.menu add command -label {barf} -command {puts "barf"}

Run the script, and click on the "menu" button. The menu should appear in
the upper left. Now move the menu button. Click on it again and the menu
should be posted in the correct place, below the button.

Thanks, and I hope all is well with you.
-- 
	Marty

Marty Olevitch           Washington U Physics Dept; St Louis, MO 63130 USA 
marty@cosray2.wustl.edu  http://cosray2.wustl.edu/~marty  Tel: (314) 935-6285 


 ****


From: Mike Meyer <mwm@phone.net>
Date: Wed, 8 Dec 1999 03:39:55 -0800 (PST)
To: Elliott Hughes <Elliott.Hughes@genedata.com>
Subject: Re: lwm bug???

Sorry for the delay in getting back to you - this project stalled as
my personal life got very complicated. It's still stalled, but I found
another bug.

This is in the CLOSE_PATCH.txt patch, though. It seems that
buttonrelease in the patched version dereferences the return value of
Client_Get without checking whether or not that value is NULL - and it
can be NULL (I've got two core files to prove it). Seems to be related
to my habit of double-clicking on the root menu to make the first
selection in the 9menu window that brings up - and sometimes missing
on the second click.

The obvious solution would seem to be just to check c before
dereferencing it, but I haven't tried it yet.

Elliott Hughes writes:
;->my question at the time was "but what would you do with this?" and
;->the only answer was "do simple window control from shell-scripts".

I think that window could do everything I'm providing. On the other
hand, I'm looking at more than "simple window control from shell
scripts". I want tools that work with sets of windows. The first
useful script finds the largest width & height in the set, then moves
all the windows so the upper left corners are on the points of a grid
with those dimensions. If the windows are all the same size, you get a
nice, non-overlapping window arrangement. The last client I want to do
before release (I'll be looking for an OSS CORBA ORB for Java when I
get back to it) is a simple desktop manager, letting you change window
configurations at the press of a button. Window could do the trick,
but wasn't the solution I was looking for.

	Thanx,
	<mike