[7838] in Athena Bugs

home help back first fref pref prev next nref lref last post

re: playing with dash

daemon@ATHENA.MIT.EDU (vanharen@ATHENA.MIT.EDU)
Mon Jul 29 23:55:40 1991

From: vanharen@ATHENA.MIT.EDU
Date: Mon, 29 Jul 91 23:55:53 -0400
To: marc@ATHENA.MIT.EDU
Cc: bugs@ATHENA.MIT.EDU
In-Reply-To: bugs[7802]


>>	Lots of out-of-date info, other stuff
>> Dash -> About Dash
>> 	mentions 7.2 release notes.

Unfortunately, the dash menu file is on AFS, and so things will be
out-of-date with respect to 7.3, because we want to make the information
"current" for the majority of the workstations out there, which are
still 7.2.

>> Communication -> Mail -> Emacs Mail Handler
>> 	says to run "emacs -q -f mh-rmail"  Why -q?

Dunno.  I felt like it.  Starts up faster.  Yeah, I guess maybe that
should be changed.

>> Programming -> Unsupported Languages
>> 	perhaps mention gcc?

OK.  Seems reasonable to me.  I'll add it.

>> Programming -> Unsupported Languages -> Perl
>> 	it's now in the perl locker:  add perl; man perl

OK.  Didn't know that...  as I was saying earlier, the menus are on AFS,
so the change will show up tomorrow night at the next AFS propogation
(every night at 9pm?).

>> When menus are up, dash appears to be processing all the events.  One
>> annoying side effect is that if I click off a zgram, the menu
>> structure I have up vanishes.  Why is dash grabbing the mouse?

The default behavior is to grab the mouse, yes.  Thus, if I click
anywhere outside the menu or menubar, the menus pop down.  This was done
with the intention of making it easier to use for naive users.  To
change this behavior, add "Dash*rude: false" to your .Xresources or
.dashrc file.

>> The window is override redirect.  Why?  This conflicts with some of
>> the other options.  There are several properties set which only make
>> sense if the window is not override-redirect:
>> 
>> WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW
>> WM_HINTS(WM_HINTS):
>>                 Initial state is Normal State.
>> WM_ICON_NAME(STRING) = "Menu Bar"
>> WM_NAME(STRING) = "Menu Bar"
>> 
>> In fact, properties mean practically nothing at all when the app is
>> override-redirect.

It is override-redirect so that you can't move it, of course...  :-)
This can be changed with: "Dash*menuTree.window.overrideRedirect: False".
Although, I have to give your fair warning -- strange things *will*
happen if you turn off override-redirect and move the menubar around the
screen, as soon as you try using the menus...

As for the properties on the menubar...  if you were to turn off
override-redirect, those properties would have some use, no?  Is it
worth it to check to see if the window is override-redirect, and if so,
not bother installing all the properties?  The "Window Jet" is what is
installing all the properties, and it does it for all the windows
created by dash -- at some point, it should be changed to check and see
whether the window it is creating is an application window, and if so,
not install all those properties.  I'm not sure whether having the extra
properties on all those windows is really that expensive, though, is it?

>> I should be able to cut-and-paste from the help boxes with shift-drag
>> or something.

Yeah, I know.  Didn't have time to get it done for this release.  It's
on the list.  Watch for the next release...

							-C.

home help back first fref pref prev next nref lref last post