Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
mainly, using a non-zero menuDelayClose allowed you to have multiple submenus open
|
|
|
|
<tomi@nomi.cz>
|
|
|
|
|
|
|
|
|
|
built into sh
|
|
|
|
created a strut
|
|
writing rc
|
|
|
|
|
|
session.ignoreBorder: true
|
|
but not height
|
|
|
|
|
|
rather than the active tab in the same window
|
|
|
|
|
|
|
|
|
|
|
|
|
|
with focusnew
|
|
get restacked on the bottom
|
|
|
|
|
|
the client
|
|
|
|
|
|
accidentally left in
|
|
|
|
|
|
|
|
suppose your alpha was at 3 and then you double-clicked -- IntResMenuItem was
setting the alpha to -2, which in FbWinFrame::setAlpha got cast to an unsigned
char, or 254; then, IntResMenuItem would check if the value was less than 0,
which, of course, it wasn't
now, IntResMenuItem checks if the value will exceed the max/min before setting
|
|
removed here did anything useful; it's probably a remnant of an old menu
implementation
|
|
|
|
|
|
or else we'll lose an entire keystroke!\
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|