Re: Notification: incoming/714
[Dominik Vogt - Mon, 28 May 2001 04:09:37 AM CDT] > > Message summary for PR#714 > > From: [EMAIL PROTECTED] > > Subject: Java 1.2/1.3 problems with initial window size > > Date: Tue, 22 May 2001 10:13:14 -0500 > > 0 replies 0 followups > > > > I noticed a problem that probably has its roots in bug report #664, > > and is demonstratable through Sun's beans development kit. This bug > > does not appear in any other window manager I've tried, ranging from > > the simple (flwm) to the complex (enlightenment), so it's odd that it > > pops up in fvwm. > > > > Instructions for reproducing: > > > > 1. Download the BDK from Sun. I can send you the original zip archive > >or a tar/gzipped archive. > > Whatever you mean with "BDK" (I could not find this name on the > Sun web page) I downloaded the Netbeans 3.2 executable > distribution. It has not makefile anywhere and dumps core when I > try to run it. All attempts to download the source distribution > ended in netscape crashes until now. I'm still trying. (Please > do *not* email the sources to me). I meant the 'Beans Development Kit', from www.java.com. For easy access, I am temporarily providing it at http://srh1171.urh.uiuc.edu/~anle/misc/bdk1_1.zip You need unzip. -- An Thi-Nguyen Le |FORTRAN is for pipe stress freaks and crystallography weenies. -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Notification: incoming/715
[An Thi-Nguyen Le - Sun, 27 May 2001 01:32:43 PM CDT] > *FvwmColorset 8 fg blue, bg black, Pixmap > *FvwmColorset 8 fg red, bg white, Pixmap This even happens when I get the commands correct. :) *FvwmThemeColorset 8 fg blue, bg black, Pixmap *FvwmThemeColorset 8 fg red, bg white, Pixmap -- An Thi-Nguyen Le |Time goes, you say? |Ah no! |Time stays, *we* go. | -- Austin Dobson -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Notification: incoming/715
[Dominik Vogt - Sun, 27 May 2001 01:13:56 PM CDT] > On Thu, May 24, 2001 at 02:05:34AM -0500, fvwm-bug wrote: > > Full_Name: An Thi-Nguyen Le > > Version: CVS > > CVS_Date: May 24th > > OS: Linux (2.2) > > X_Server: XFree86 4.0.3 > > > > The FvwmWharf Module doesn't appear to update itself when its > > colorset is changed; moving a window over the module will cause > > it to repaint itself correctly on areas covered/uncovered by the > > window. > > I can't confirm this. FvwmWharf updates as it should for me. > Please provide your config file and detailed instructions to > reproduce the problem. Okay. Here's my configuration for FvwmWharf: *FvwmWharfColorset 8 *FvwmWharfColumns 1 *FvwmWharfGeometry -0+0 *FvwmWharf clock clock.xpm MaxSwallow "wmCalClock" \ wmCalClock -comicsans -l -e "xipacsum -t today" *FvwmWharf bubble bubble.xpm MaxSwallow "wmbubble" \ wmbubble -k "rxvt -e top" \ "rxvt -rv -T ROOT -n ROOT -e su" *FvwmWharf info info.xpm MaxSwallow "wmgtemp" wmgtemp -u 15 -M 45 *FvwmWharf fsm fsm.xpm MaxSwallow "wmfsm" wmfsm *FvwmWharf web web.xpm MaxSwallow "wmnetselect" \ wmnetselect -exec $HOME/software/mozilla/mozilla *FvwmWharf net net.xpm MaxSwallow "wmnet" \ wmnet -n -e "xnetstat -atu" \ -d 50 -l -x 1000 *FvwmWharf mail mail.xpm MaxSwallow "wmbiff" wmbiff *FvwmWharf mail2 mail.xpm MaxSwallow "wmbiff1" wmbiff1 -c $HOME/.wmbiffrc-1 *FvwmWharf weather sun.xpm MaxSwallow "wmWeather" wmWeather -s KCMI -W *FvwmWharf map map.xpm MaxSwallow "wmGrabImage" \ wmGrabImage -url http://www.atmos.uiuc.edu/weather/parser.php?/download/rada r/nicerad_N.gif \ -delay 600 -http http://www.atmos.uiuc.edu/weather/ -c *FvwmWharf music music.xpm MaxSwallow "wmusic" wmusic -t -u -x -w None of the *.xpm's exist. (Hmmm. Is that the problem, I wonder?) There are no folders, only swallowed apps. Anyways, the instructions are rather short and I'm not sure what else to add to them: 1. Define colorset 8 to be something. *FvwmColorset 8 fg blue, bg black, Pixmap 2. Start up FvwmWharf like normal. Module FvwmWharf This may or may not completely update itself; in my experience, on a restart of the fvwm session it doesn't, while starting it up in the middle of a session does. Sometimes. 3. Change colorset 8 to something different. *FvwmColorset 8 fg red, bg white, Pixmap Anything else with colorset 8 will change appropriately, while FvwmWharf merely sits there. This happens on both plain colorsets and colorsets with pixmaps/gradients. However, forcing expose events on FvwmWharf (iconifying and uniconifying, covering with windows and then removing them) will redraw the expose'd portions of the Wharf correctly. The patch I submitted fixes this problem (on my machine, anyways) by calling XClearArea and telling it to generate an Expose event. (Before, no expose events were being generated on changing colorsets). I also commented out the many calls to XClearWindow/XClearArea (before, XClearWindow was called for every folder/button) in that function, but maybe these are needed for folders that pop out. I looked at other modules (like FvwmPager) and apparently they do generate Expose events in such a way, sometimes, when colorsets get changed. -- An Thi-Nguyen Le |The longer the title, the less important the job. -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Patch for FvwmWharf and colorset updates
Attached is a small patch that fixes the FvwmWharf
doesn't-update-when-colorset-changes bug. Made against current CVS sources.
--
An Thi-Nguyen Le
|I thought there was something fishy about the butler. Probably a Pisces,
|working for scale.
| -- Firesign Theatre, "The Further Adventures of Nick Danger"
Index: modules/FvwmWharf/FvwmWharf.c
===
RCS file: /home/cvs/fvwm/fvwm/modules/FvwmWharf/FvwmWharf.c,v
retrieving revision 1.23
diff -u -r1.23 FvwmWharf.c
--- modules/FvwmWharf/FvwmWharf.c 2000/12/03 15:56:09 1.23
+++ modules/FvwmWharf/FvwmWharf.c 2001/05/27 17:39:18
@@ -2220,7 +2220,7 @@
for(x = 0; x < num_folders; x++)
{
-XClearWindow(dpy, Folders[x].win);
+/*XClearWindow(dpy, Folders[x].win);*/
RedrawWindow(&Folders[x].win,num_folderbuttons, -1,
Folders[x].cols, Folders[x].rows);
for(y = 1; y <= Folders[x].count; y++)
@@ -2230,10 +2230,12 @@
else
RedrawUnpushedOutline(&Folders[x].win, y, 1);
}
-XClearWindow(dpy, main_win);
-RedrawWindow(&main_win,0, -1, num_rows, num_columns);
+/*XClearWindow(dpy, main_win);*/
}
+ XClearArea(dpy, main_win, 0, 0, 0, 0, True);
+ RedrawWindow(&main_win,0, -1, num_rows, num_columns);
+
XSync(dpy, 0);
return;
@@ -2251,6 +2253,8 @@
colorset = LoadColorset(tline);
change_colorset(colorset);
}
+
+ RedrawWindow(&main_win,0, -1, num_rows, num_columns);
return;
}
Re: SetEnv not expanding environmental variables itself
[Dan Espen - Thu, 10 May 2001 10:14:34 AM CDT] > Use the notation: > > Exec echo $[bindir] Ah. Okay. Never mind... Embarassed... -- An Thi-Nguyen Le -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: SetEnv not expanding environmental variables itself
[An Thi-Nguyen Le - Thu, 10 May 2001 09:50:34 AM CDT]
> Version: cvs (as of May 10 09:35:30 CDT 2001)
>
> Maybe this is documented somewhere. Set up some environment stuff, like
> so:
>
> SetEnv fvwmdir ${HOME}/.fvwm
> SetEnv bindir $fvwmdir/bin
>
> 'Exec echo ' should fully expand these variables, then. However,
> this happens:
>
> Exec echo $fvwmdir
> ===> ${HOME}/.fvwm
> Exec echo $bindir
> ===> $fvwmdir/bin
>
> The second one should be something like maybe '${HOME}/.fvwm/bin'. Unless,
> of course, SetEnv's not supposed to expand environment variables.
Some more possibly strange things:
SetEnv fvwmdir ${HOME}/.fvwm
ImagePath /usr/share/icons
ImagePath +:$fvwmdir/pixmaps
doesn't work either. However, using
SetEnv fvwmdir /home/viper/.fvwm
*does* work.
--
An Thi-Nguyen Le
|It may be better to be a live jackal than a dead lion, but it is better
|still to be a live lion. And usually easier.
| -- Lazarus Long
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
SetEnv not expanding environmental variables itself
Version: cvs (as of May 10 09:35:30 CDT 2001)
Maybe this is documented somewhere. Set up some environment stuff, like
so:
SetEnv fvwmdir ${HOME}/.fvwm
SetEnv bindir $fvwmdir/bin
'Exec echo ' should fully expand these variables, then. However,
this happens:
Exec echo $fvwmdir
===> ${HOME}/.fvwm
Exec echo $bindir
===> $fvwmdir/bin
The second one should be something like maybe '${HOME}/.fvwm/bin'. Unless,
of course, SetEnv's not supposed to expand environment variables.
--
An Thi-Nguyen Le
|Beauty seldom recommends one woman to another.
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
FvwmPager WindowColorsets not updating completely
Version: cvs (May 8th) I ran across something strange recently with FvwmPager. 1. Set up the pager like so, and *without* mini icons: *FvwmPagerWindowColorsets 1 2 *FvwmPagerSmallFont 5x7 2. Set up colorsets 1 and 2: *FvwmThemeColorset 1 fg white, bg lightblue, Pixmap *FvwmThemeColorset 2 fg lightblue, bg navy, Pixmap 3. Start up the pager any way you want. 4. Move around windows, focusing them, unfocusing them, and so on. All the colors should be right. 5. Now, change the colorsets: *FvwmThemeColorset 1 fg red, bg pink, Pixmap *FvwmThemeColorset 2 fg green, bg black, Pixmap 6. Move around the windows, focusing them, unfocusing them, and so on. On the current viewport, everything is obviously okay. 7. Now change the viewport (scroll left or right or up or down by 100%, or change desktops). 8. Now, change back to the original viewport. 9. Now move around the windows, focusing and unfocusing them. Result: The unfocus windows colorset foreground for the pager has fallen back to the previous version (e.g., no longer red, but white). If one restarts the pager, then the colorsets are correct no matter what one does, up until the colorsets change again. -- An Thi-Nguyen Le -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Icon titles not retracting
Version: 2.3.32 When icons are focused on via the keyboard (e.g., binding 'Next [Iconic] Focus' to a key sequence), the icon title expands (as expected), but when focus leaves via the keyboard, the icon title stays expanded instead of contracting or retracting or whatnot. This doesn't appear to happen when focus enters and leaves via the mouse. -- An Thi-Nguyen Le |As the poet said, "Only God can make a tree" -- probably because it's |so hard to figure out how to get the bark on. | -- Woody Allen -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
