FVWM: Re: HoverIcon for FvwmButtons (Was: animated FvwmButtons)
After you get this feel correctly, you may think about adding PressIcon, PressTitle and PressColorset to be used instead of the original ones. :) Would this make it possible to have a different icons for the 'up' and 'down' state of a button ? Because i'm awaiting this feature for a long time, but don't like hacking into FvwmButtons myself. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: [off topic] mp3 + ogg player
I'm very content about FVWM, but some programs don't comply to conventions, I guess everyone here knows that xmms is one of them. I'm What exactly is wrong with XMMS ? I use it, but it is minimized without an icons. I control it with shortcuts or with my gkrellm, and the playlist of xmms is automatically filled by LPlayer (http://lplayer.sf.net) cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: Preventing dynamic icons for NoIcon apps
Hi, I should probably make this a personal question, but since i think a lot of users use this feature, i thought i'ld ask it publicly. When using taviso's rc lines for having dynamic icons for applications when minimizing (http://dev.gentoo.org/~taviso/screenshot6.png), i would like to have that only icons are generated for applications that don't have the NoIcon windowstyle. Is this possible ? cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Conditionally adding menu items
have something like pointing a menu to a directory in which all programs/items to be shown or hidden are stored as links or something similar. If you have the luck to be running Debian, you can add a menuitem: .. + Debian Popup /Debian .. This menu will contain all installed applications, grouped in several categories. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Conditionally adding menu items
That's great but I am running gentoo. I wonder however why this would work only on Debian? Could you explain what Debian does to provide its menus so easily and how this tecnique is integrated into fvwm? Debian packages normally contain a file describing what type of application it is (graphical, games, ...), an icon for the application, .. Each time a debian package is installed, Debian transforms this information using scripts into files for window managers which have use for this. I'm not sure if other distributions have this, nor why they don't. But i'm sure other people will respond to this ;) cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Conditionally adding menu items
menu structure. I personally find it a real pain in the bum, and much prefer writing my own dynamic menus (mine are implemented with ruby). It's not really a pain in the bum, as you don't have to do anything about it to use it. Besides, they're not really dynamic, so it doesn't cost extra time to generate menus at runtime, whereas real dynamic menus do. I personally don't use the Debian menus (maybe just for browsing what applications are installed on a machine). Normally, you only have a small amount of applications you use, so you can just define your own statical menu and see that the apps exist on all machines you work on. I have a separate extra rc file per machine for adding machine-spoecific applications. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: mini icons and NoResource
Style mutt Icon norm/mutt_button.xpm MiniIcon mini/mutt-mini.xpm How about placing a comma in between your Icon and your MiniIcon declarations ? You can check the resource and class etc. of a window with FvwmIdent. If 'mutt' isn't anywhere in there, you could explicitly set the title of the xterm to 'mutt' with the -T option. But, if you start your mutt with 'xterm -e mutt', it should set the title automatically. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Smooth startup
# schedule FvwmPager so it starts after the root bg is up. + I Schedule 900 Module FvwmPager * * Yes, but that's not really clean (you might wait too long or too short). I used fvwm-root in a PipeRead, which seems to solve the problem. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: mini icons and NoResource
How do I get the mini icon to work with mutt ,class=mutt resource=xterm, and moneydance, class=moneydance Resource=com.moneydance.apps.md.view.gui.MainFrame. the norm works. Could you point me to the FAQ for this? :) The FAQ? This is simply in the manual: Style mutt MiniIcon mutt.mini.png (the same for moneydance) cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: Smooth startup
Hi, When i start fvwm, the initialization function starts the pager, the buttons, and sets the background. If the buttons and the pager are transparent, this gives some weird results while starting: first they are started with a black backround, after a while the background comes up, and then the backgrounds are updated. This doesn't look really smooth. Is there anything that can be done about that ? thanks, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Debian ./configure problem
PKG_CONFIG_PATH=/usr/X11R6/lib/pkgconfig:/lib/pkgconfig PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/lib/pkgconfig:/opt/gnome/lib/pkgconfig PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/opt/lib/pkgconfig:/usr/local/lib/pkgconfig Debian avoids the need to set environment variables. I also had troubles this weekend building the new fvwm, also with fontconfig. I didn't look into it yet, i suspect it has something to do with the new X server, but i am not sure. What version of XFree are you running ? cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Microsoft Patent
There is Microsoft Patent for a virtual desktop in the works, have you guys seen this: This is not the first time (and it certainly won't be the last) that Microsoft issues bogus patents. As mentioned before, there clearly is prior art here, so a patent like that will never hold up in court. Another example would be the 'contact is composing...' message in IM systems; for this, there also is prior art (even Jabber, a fairly 'new' protocol had that before the patent was issued). Concerning patents, i personally wouldn't pay too much attention to them. You only get frustrated, you lose a lot of time. Then again, i am no lawyer, just a programmer who likes to code whatever he has in his head. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: applet for displaying the battery status on a laptop
I'm using Fvwm2 and need an applet for displaying the battery status on a laptop. I've tried some WindowMaker applets but they did'nt work properly. For example, wmbatteries does'nt update the status. Is there an application which works fine with Fvwm2 and ACPI? Not strictly what you asked, but i use gkrellm for monitoring battery status and much much more. IMHO, gkrellm is the perfect addition to an FVWM desktop. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Conditionals in fvwm functions
I want to achieve something like this (in pseudocode): In this special case, i use a cleaner approach to achieve the same: in the end of my fvwm2rc (which is the same on all my machines) i have a: Read rc.local The rc.local is different on each machine, and contains machine-specific settings. Of course, this has not the full power of what you're asking, but it's sufficient for what I need. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: FvwmButtons: Up Down buttons
Hi, Is it possible to have different icons for the up down state of FvwmButtons ? thanks, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: transparency
Olivier, For those interested by Translucency I've uploaded a patch Exteremely cool to finally share your (huge) patch :) I just tested it, and it works perfect. Too bad my card isn't supported by XDirectFB, so i have to stick with the 'basic' translucency of menus, in which i am a bit disappointed. It just isn't perfect, but unfortunately it won't get any better under XFree :-( I suppose the XDirectFB translucency supports updates of the background ? cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Tray icon
I really don't know what you mean with docking applications. I meant an application requesting to put itself in the system tray. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: Tray icon
Hi, I am curious to know what the normal behaviour is in FVWM when an application 'docks' into the system tray, when there is no real system tray (only FVWM is running) ? And what should happen when there is an FvwmButtons running that swallows an application which docks into the system tray. I get really weird behaviour there: one time i was able to dock the application, and to redraw it by unfolding the swallowing panel, but then redrawing was really messed up, and interaction not really good working. Other times, FvwmButtons seems to want to swallow it, but it can't, and a press on the button times out. I had all these problems when enabling 'docking' in Psi, and i would like to know if it's due to Psi, due to FVWM, or due to the fact that it's just not nice to dock applications when there is no real system tray and that swallowing docking applications in panels is also a no-do. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: xterm bold font
I always wondered why people spend so much time configuring all aspects of a look, but do not improve such basic thing like their terminal. If a bold font is not specified using -fb option (or similar), than the Ok, i didn't see that part in the manpage. However, there is some behaviour which i don't understand: when i start xterm -fn 7x14, i get an xterm where bold fonts are clearly not generated by tracing the normal font, the bold font is clearly 7x14bold. Running xterm -fn 7x14 -fb 7x14bold gives me the exact same result. Maybe XTerm has some predefined corresponding bold fonts for standard fonts ? So, for example, if someone starts xterm like this: xterm -geometry 80x40 -sb +sk -si -sl 4096 -j -ls +lc -fn 7x14 the following addition makes it look nicer: xterm -geometry 80x40 -sb +sk -si -sl 4096 -j -ls +lc -fn 7x14 -fb 7x14bold So, these make no difference. cheers, Remko PS: I personally don't like the 7x14-7x14bold combination. The bold font is narrower (but bolder), and it looks like 2 different fonts in 1 terminal. I seem to prefer the 'generated' font. -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: xterm bold font
Ok, it is a matter of a habit. For me, the real font is more an art work that looks nice, the generated font looks a bit like a crap without anti-aliasing, especially for wide letters. :) I would think that too, but weird enough in this case my preference goes out to the other way. I have tried other font settings in the past (such as anti-aliased fonts), but i always come back to the default. An anti-aliased font would be nice, but i haven't found one which renders nice at such small point sizes. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: fvwm2rc files
_NIce_ screenshot!! Remko, do you by any chance remember where the background image came from? Just the thing for my daughter ;-) or did you produce it yourself? They come from the Dick Bruna website: http://www.miffy.com/ You can find a bunch of nice pictures there. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: fvwm2rc files
Also, does anyone have a screenshot of FvwmButtons...I want to see it in action. A little bit more discrete version of FvwmButtons can be seen in the top left corner of http://www.cs.kuleuven.ac.be/~remko/fvwm/screenshot2.png The 3 buttons contain panels that fold in and out (the first one is my IM client, the second one is my IRC window, and the third one is a remote SSH session which i keep open at all times, and frequently use) It can be seen in action on http://www.cs.kuleuven.ac.be/~remko/fvwm/buttons.gif cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: fvwm for Debian
to sources.list. Note that these aren't all that up-to-date; I think the version there is still 2.5.6. Nevertheless interesting ;-) I guess the maintainer decided to put it in a separate apt-repository instead of in the main unstable repository. thanks, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: fvwm for Debian
debian unstable is called unstable because it's not stable yet, not because it includes unstable (development) versions of apps. Generally debian unstable includes latest stable versions of apps (or at least that's the goal, as far as I can say). That's correct. Although that doesn't prevent them from adding the development version as well, but under a different name (such as they do with a lot of packages). And i too am longing for the FVWM development versions in Debian unstable, because FVWM is about the only package i still have to install from source. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: FvwmButtons Panel binding to keystroke
Would be easier to have a keyboard shortcut to retract/contract the panel than having to move my mouse and click. That isn't possible yet. I'm also interested in this feature, and was planning to implement it one day if nobody else had yet, but i didn't have any time so far. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Wiki for fvwm?
I'd rather if we collect config parts, like button setups, titlebar decorations, menu definitions and fvwm scripts, and place them together with a screenshot and description on the web site. I agree with Uwe. The current approach is a lot easier, much more maintainable, and gives a good overview. The threshold is a little bit higher, because you have to actually send a mail to someone, but maybe that isn't really such a bad thing after all ;-) IMHO, wiki is only suitable for early stages of a work in progress, when things are in a state of flux, and having centralized documents is a lot of overhead on synchronization. But once things stopped moving, the whole wiki hierarchy (which is usually a huge mess by then in which you get lost very quick) should be organized into centrally administered documents. Just my 2 cents. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FvwmButtons relief patch
I have a patch lying around here (for a few months now)
which adds an option to FvwmButtons for customizing the relief
(flat/raised/sunken) for both states. Do you suggest i polish it and
send it through now, or should i wait
Let us have a look at the patch; then we can decide.
I'm not sure if the patch got to the mailinglist (i've been having some
e-mail problems), but since it's been a month since i posted it and
haven't got any replies on it, i'm reposting it. If it's being reviewed,
please ignore my mail ;)
This patch adds a new 'Relief' option to FvwmButtons. The syntax is
described in the man page.
cheers,
Remko
Index: modules/FvwmButtons/FvwmButtons.1
===
RCS file: /home/cvs/fvwm/fvwm/modules/FvwmButtons/FvwmButtons.1,v
retrieving revision 1.61
diff -u -r1.61 FvwmButtons.1
--- modules/FvwmButtons/FvwmButtons.1 9 Nov 2002 15:18:52 - 1.61
+++ modules/FvwmButtons/FvwmButtons.1 22 Jul 2003 15:51:11 -
@@ -169,6 +169,12 @@
Specifies a background pixmap to use. Specify none (without the
double quotes) for a transparent background.
+.IP *FvwmButtons: ReliefStyle \fIstate\fP \fIstyle\fP
+Specifies which style of relief to draw when the button is in the given
+state. \fIstate\fP can be either \fIUp\fP or \fIDown\fP. \fIstyle\fP
+is one of \fIClean\fP (draws the background color), \fIRaised\fP or
+\fISunken\fP.
+
.IP *FvwmButtons: Rows \fIrows\fP
Specifies the number of rows of buttons to be created. The default
is 2 rows.
Index: modules/FvwmButtons/FvwmButtons.c
===
RCS file: /home/cvs/fvwm/fvwm/modules/FvwmButtons/FvwmButtons.c,v
retrieving revision 1.181
diff -u -r1.181 FvwmButtons.c
--- modules/FvwmButtons/FvwmButtons.c 6 Jul 2003 14:34:07 - 1.181
+++ modules/FvwmButtons/FvwmButtons.c 22 Jul 2003 15:51:11 -
@@ -783,6 +783,8 @@
UberButton-title = MyName;
UberButton-swallow = 1; /* the panel is shown */
+ UberButton-reliefstyle = (RELIEFSTYLE_RAISED 4) |
+(RELIEFSTYLE_SUNKEN); /* Default relief */
/* parse module options */
ParseConfiguration(UberButton);
Index: modules/FvwmButtons/FvwmButtons.h
===
RCS file: /home/cvs/fvwm/fvwm/modules/FvwmButtons/FvwmButtons.h,v
retrieving revision 1.44
diff -u -r1.44 FvwmButtons.h
--- modules/FvwmButtons/FvwmButtons.h 29 Jun 2003 19:53:24 - 1.44
+++ modules/FvwmButtons/FvwmButtons.h 22 Jul 2003 15:51:11 -
@@ -75,6 +75,7 @@
0x0200 /* By default this only done on Popup */
#define b_Id 0x0400 /* Has a user defined id for referencing */
#define b_IconAlpha 0x0800 /* Icon has an alpha chanel */
+#define b_ReliefStyle 0x1000 /* Relief Style */
/* Flags for b-swallow */
#define b_Count 0x0003 /* Init counter for swallowing */
@@ -125,6 +126,7 @@
Pixel bc,hc,sc; /* b_Back !b_IconBack */
FvwmPicture *backicon; /* b_Back b_IconBack */
ushort minx,miny;/* b_Size */
+ byte reliefstyle;/* b_ReliefStyle */
};
typedef struct
@@ -155,6 +157,10 @@
char *back; /* b_Back */
char *fore; /* b_Fore */
int colorset;/* b_Colorset */
+#define RELIEFSTYLE_CLEAN 0x0 /* No relief */
+#define RELIEFSTYLE_RAISED 0x1 /* Raised relief */
+#define RELIEFSTYLE_SUNKEN 0x2 /* Sunken relief */
+ byte reliefstyle;/* b_ReliefStyle */
byte xpad,ypad; /* b_Padding */
signed char framew; /* b_Frame */
byte justify;/* b_Justify */
Index: modules/FvwmButtons/button.c
===
RCS file: /home/cvs/fvwm/fvwm/modules/FvwmButtons/button.c,v
retrieving revision 1.32
diff -u -r1.32 button.c
--- modules/FvwmButtons/button.c29 Jun 2003 19:53:24 - 1.32
+++ modules/FvwmButtons/button.c22 Jul 2003 15:51:11 -
@@ -310,6 +310,24 @@
return -1;
}
+byte buttonReliefStyle(button_info *b)
+{
+button_info *bb = b;
+if (bb-flags b_ReliefStyle)
+return bb-reliefstyle;
+else if (bb-flags b_Container bb-c-flags b_ReliefStyle)
+return bb-reliefstyle;
+while ((bb = bb-parent))
+{
+if (bb-c-flags b_ReliefStyle)
+return bb-c-reliefstyle;
+}
+#ifdef DEBUG
+fprintf(stderr,%s: BUG: No relief definition?\n,MyName);
+#endif
+return (RELIEFSTYLE_RAISED4) | RELIEFSTYLE_SUNKEN;
+}
+
int buttonBackgroundButton(button_info *b, button_info **r_b)
{
button_info *tmpb, *pb;
@@ -516,6 +534,7 @@
b-c-back=safestrdup(rgb:90/80/90);
b-c-fore=safestrdup(black);
b-c-framew=2;
+b-c-reliefstyle= (RELIEFSTYLE_RAISED4) | RELIEFSTYLE_SUNKEN;
}
}
Index: modules/FvwmButtons/button.h
Re: FvwmButtons relief patch
Let us have a look at the patch; then we can decide.
Ok. Here goes.
Remko
Index: modules/FvwmButtons/FvwmButtons.1
===
RCS file: /home/cvs/fvwm/fvwm/modules/FvwmButtons/FvwmButtons.1,v
retrieving revision 1.61
diff -u -r1.61 FvwmButtons.1
--- modules/FvwmButtons/FvwmButtons.1 9 Nov 2002 15:18:52 - 1.61
+++ modules/FvwmButtons/FvwmButtons.1 25 Jun 2003 14:44:50 -
@@ -169,6 +169,12 @@
Specifies a background pixmap to use. Specify none (without the
double quotes) for a transparent background.
+.IP *FvwmButtons: ReliefStyle \fIstate\fP \fIstyle\fP
+Specifies which style of relief to draw when the button is in the given
+state. \fIstate\fP can be either \fIUp\fP or \fIDown\fP. \fIstyle\fP
+is one of \fIClean\fP (draws the background color), \fIRaised\fP or
+\fISunken\fP.
+
.IP *FvwmButtons: Rows \fIrows\fP
Specifies the number of rows of buttons to be created. The default
is 2 rows.
Index: modules/FvwmButtons/FvwmButtons.c
===
RCS file: /home/cvs/fvwm/fvwm/modules/FvwmButtons/FvwmButtons.c,v
retrieving revision 1.179
diff -u -r1.179 FvwmButtons.c
--- modules/FvwmButtons/FvwmButtons.c 25 Apr 2003 07:21:00 - 1.179
+++ modules/FvwmButtons/FvwmButtons.c 25 Jun 2003 14:44:50 -
@@ -780,6 +780,8 @@
UberButton-title = MyName;
UberButton-swallow = 1; /* the panel is shown */
+ UberButton-reliefstyle = (RELIEFSTYLE_RAISED 4) |
+(RELIEFSTYLE_SUNKEN); /* Default relief */
/* parse module options */
ParseConfiguration(UberButton);
Index: modules/FvwmButtons/FvwmButtons.h
===
RCS file: /home/cvs/fvwm/fvwm/modules/FvwmButtons/FvwmButtons.h,v
retrieving revision 1.43
diff -u -r1.43 FvwmButtons.h
--- modules/FvwmButtons/FvwmButtons.h 5 Jun 2003 14:00:21 - 1.43
+++ modules/FvwmButtons/FvwmButtons.h 25 Jun 2003 14:44:50 -
@@ -89,6 +89,7 @@
0x0200 /* By default this only done on Popup */
#define b_Id 0x0400 /* Has a user defined id for referencing */
#define b_IconAlpha 0x0800 /* Icon has an alpha chanel */
+#define b_ReliefStyle 0x1000 /* Relief Style */
/* Flags for b-swallow */
#define b_Count 0x0003 /* Init counter for swallowing */
@@ -139,6 +140,7 @@
Pixel bc,hc,sc; /* b_Back !b_IconBack */
FvwmPicture *backicon; /* b_Back b_IconBack */
ushort minx,miny;/* b_Size */
+ byte reliefstyle;/* b_ReliefStyle */
};
typedef struct
@@ -169,6 +171,10 @@
char *back; /* b_Back */
char *fore; /* b_Fore */
int colorset;/* b_Colorset */
+#define RELIEFSTYLE_CLEAN 0x0 /* No relief */
+#define RELIEFSTYLE_RAISED 0x1 /* Raised relief */
+#define RELIEFSTYLE_SUNKEN 0x2 /* Sunken relief */
+ byte reliefstyle;/* b_ReliefStyle */
byte xpad,ypad; /* b_Padding */
signed char framew; /* b_Frame */
byte justify;/* b_Justify */
Index: modules/FvwmButtons/button.c
===
RCS file: /home/cvs/fvwm/fvwm/modules/FvwmButtons/button.c,v
retrieving revision 1.31
diff -u -r1.31 button.c
--- modules/FvwmButtons/button.c1 Oct 2002 07:03:29 - 1.31
+++ modules/FvwmButtons/button.c25 Jun 2003 14:44:50 -
@@ -309,6 +309,24 @@
return -1;
}
+byte buttonReliefStyle(button_info *b)
+{
+button_info *bb = b;
+if (bb-flags b_ReliefStyle)
+return bb-reliefstyle;
+else if (bb-flags b_Container bb-c-flags b_ReliefStyle)
+return bb-reliefstyle;
+while ((bb = bb-parent))
+{
+if (bb-c-flags b_ReliefStyle)
+return bb-c-reliefstyle;
+}
+#ifdef DEBUG
+fprintf(stderr,%s: BUG: No relief definition?\n,MyName);
+#endif
+return (RELIEFSTYLE_RAISED4) | RELIEFSTYLE_SUNKEN;
+}
+
int buttonBackgroundButton(button_info *b, button_info **r_b)
{
button_info *tmpb, *pb;
@@ -515,6 +533,7 @@
b-c-back=safestrdup(rgb:90/80/90);
b-c-fore=safestrdup(black);
b-c-framew=2;
+b-c-reliefstyle= (RELIEFSTYLE_RAISED4) | RELIEFSTYLE_SUNKEN;
}
}
Index: modules/FvwmButtons/button.h
===
RCS file: /home/cvs/fvwm/fvwm/modules/FvwmButtons/button.h,v
retrieving revision 1.14
diff -u -r1.14 button.h
--- modules/FvwmButtons/button.h1 Oct 2002 07:03:29 - 1.14
+++ modules/FvwmButtons/button.h25 Jun 2003 14:44:50 -
@@ -42,6 +42,7 @@
Pixel buttonHilite(button_info*);
Pixel buttonShadow(button_info*);
int buttonColorset(button_info *b);
+byte buttonReliefStyle(button_info *b);
int buttonBackgroundButton(button_info *b, button_info **r_b);
byte buttonSwallow(button_info*);
byte buttonJustify(button_info*);
Index:
FvwmButtons relief patch
Hi, I have a patch lying around here (for a few months now) which adds an option to FvwmButtons for customizing the relief (flat/raised/sunken) for both states. Do you suggest i polish it and send it through now, or should i wait for 2.7 ? cheers, Remko -- Visit the official FVWM web page at URL: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]
FVWM: FvwmPlacement
Hello, I was wondering if it's possible to put an application which doesn't accept geometry parameters in a fixed location. I found a module FvwmPlacement which claims to do this, but thought it was strange that this feature is not in the standard FVWM distribution. Is there another way ? thanks, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FvwmButtons patch + Suggestion
I may suggest to do it a bit differently, new options for Panel: Respawn and SpawnOnOpen. This should achieve the functionality you want, but in a bit different (and I hope a more intuitive) way, This is indeed a better alternative. I thought about this alternative yesterday, but leaving out the Respawn option (since Respawn is default behaviour, and NoRespawn is an existing option). At the time, i found a problem with this, but i can't seem to find it anymore. So, is the Respawn option still needed ? I want to have the functionality in the patch, but the way it is done now it is not very extendible and as it is now it should be named DrawReliefOn state, not Relief reliefmode. I agree. Ideally I would like to have more relief styles in the future, like: Relief state style # state = up/down/both, style=clean/shadow/edge I'm not sure i understand 'style' completely. I would say style (at the moment) would be something of 'raisededge/sunkedge/flat' ? So although I want to have this functionality, I can't vote yes yet for the patch. This needs more discussion so we don't need to change the syntax in the future. Fair enough. I wasn't aware of a similar option in FvwmIconMan. It would indeed be better to have similar options. If i understand your 'Relief' approach above correctly, i will implement it that way. By the way, can you estimate how long the feature freeze will last ? cheers, Remko -- Visit the official FVWM web page at URL: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]
FvwmButtons patch + Suggestion
Hello FVWM workers,
Enclosed is a patch i proposed a few weeks ago, but which wasn't accepted at
the time because of another bug in FvwmButtons. So, i am reposting it for
revision, and would like it committed. The patch adds a new option to
FvwmButtons 'Relief reliefmode' (with reliefmode one of Up, Down, Both),
specifying in which state of the button a relief should be drawn.
Once this is done, I would like to implement two new options for Panel in
FvwmButtons.
The first one is 'OpenCreates': When a button controlling a panel is
clicked, and the panel does not exist yet, the command of the Panel
is executed to create the panel.
This new option induces another possible option, 'NoStart': When FvwmButtons
is started or restarted, the 'command' of the panel is _not_ executed.
I personally have a need for both options, both for a respawning and a non-
respawning panel. Does anyone have any comments on this ?
The names of the options might not be very good, so suggestions on those
are also very welcome.
cheers,
Remko
PS: I am not on the fvwm-workers list.
diff -urw fvwm-cvs/modules/FvwmButtons/FvwmButtons.1
fvwm-cvs.patched/modules/FvwmButtons/FvwmButtons.1
--- fvwm-cvs/modules/FvwmButtons/FvwmButtons.1 Sat Nov 9 16:18:52 2002
+++ fvwm-cvs.patched/modules/FvwmButtons/FvwmButtons.1 Mon Feb 10 20:40:10 2003
@@ -169,6 +169,11 @@
Specifies a background pixmap to use. Specify none (without the
double quotes) for a transparent background.
+.IP *FvwmButtons: Relief \fImode\fP
+Specifies when to draw relief around the button. \fImode\fP is either
+\fIUp\fP, \fIDown\fP or \fIBoth\fP for drawing relief only when
+the button is up, down, or in both cases.
+
.IP *FvwmButtons: Rows \fIrows\fP
Specifies the number of rows of buttons to be created. The default
is 2 rows.
diff -urw fvwm-cvs/modules/FvwmButtons/FvwmButtons.c
fvwm-cvs.patched/modules/FvwmButtons/FvwmButtons.c
--- fvwm-cvs/modules/FvwmButtons/FvwmButtons.c Sat Mar 8 17:27:23 2003
+++ fvwm-cvs.patched/modules/FvwmButtons/FvwmButtons.c Sat Mar 8 17:28:31 2003
@@ -780,6 +780,7 @@
UberButton-title = MyName;
UberButton-swallow = 1; /* the panel is shown */
+ UberButton-relief = RELIEF_BOTH; /* By default, show both reliefs */
/* parse module options */
ParseConfiguration(UberButton);
diff -urw fvwm-cvs/modules/FvwmButtons/FvwmButtons.h
fvwm-cvs.patched/modules/FvwmButtons/FvwmButtons.h
--- fvwm-cvs/modules/FvwmButtons/FvwmButtons.h Tue Oct 1 09:03:29 2002
+++ fvwm-cvs.patched/modules/FvwmButtons/FvwmButtons.h Mon Feb 10 20:40:10 2003
@@ -89,6 +89,7 @@
0x0200 /* By default this only done on Popup */
#define b_Id 0x0400 /* Has a user defined id for referencing */
#define b_IconAlpha 0x0800 /* Icon has an alpha chanel */
+#define b_Relief 0x1000 /* When to use relief */
/* Flags for b-swallow */
#define b_Count 0x0003 /* Init counter for swallowing */
@@ -139,6 +140,7 @@
Pixel bc,hc,sc; /* b_Back !b_IconBack */
FvwmPicture *backicon; /* b_Back b_IconBack */
ushort minx,miny;/* b_Size */
+ byte relief; /* b_Relief */
};
typedef struct
@@ -169,6 +171,10 @@
char *back; /* b_Back */
char *fore; /* b_Fore */
int colorset;/* b_Colorset */
+#define RELIEF_UP 0x1 /* Use relief only in up state */
+#define RELIEF_DOWN 0x2/* Use relief only in down state */
+#define RELIEF_BOTH 0x3/* use relief in both states */
+ byte relief; /* b_Relief */
byte xpad,ypad; /* b_Padding */
signed char framew; /* b_Frame */
byte justify;/* b_Justify */
diff -urw fvwm-cvs/modules/FvwmButtons/button.c
fvwm-cvs.patched/modules/FvwmButtons/button.c
--- fvwm-cvs/modules/FvwmButtons/button.c Tue Oct 1 09:03:29 2002
+++ fvwm-cvs.patched/modules/FvwmButtons/button.c Mon Feb 10 20:40:10 2003
@@ -309,6 +309,24 @@
return -1;
}
+byte buttonRelief(button_info *b)
+{
+button_info *bb = b;
+if (bb-flags b_Relief)
+return bb-relief;
+else if (bb-flags b_Container bb-c-flags b_Colorset)
+return bb-relief;
+while ((bb = bb-parent))
+{
+if (bb-c-flags b_Relief)
+return bb-c-relief;
+}
+#ifdef DEBUG
+fprintf(stderr,%s: BUG: No relief definition?\n,MyName);
+#endif
+return RELIEF_BOTH;
+}
+
int buttonBackgroundButton(button_info *b, button_info **r_b)
{
button_info *tmpb, *pb;
@@ -515,6 +533,7 @@
b-c-back=safestrdup(rgb:90/80/90);
b-c-fore=safestrdup(black);
b-c-framew=2;
+b-c-relief=RELIEF_BOTH;
}
}
diff -urw fvwm-cvs/modules/FvwmButtons/button.h
fvwm-cvs.patched/modules/FvwmButtons/button.h
--- fvwm-cvs/modules/FvwmButtons/button.h Tue Oct 1 09:03:29 2002
+++ fvwm-cvs.patched/modules/FvwmButtons/button.h Mon Feb 10 20:40:10 2003
@@ -42,6 +42,7 @@
Pixel buttonHilite(button_info*);
Pixel
FVWM: Shortcuts for FvwmButtons
Hello, Is it possible to bind a key to open a panel in FvwmButtons ? If not, would this be a lot of work ? cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Shortcuts for FvwmButtons
If you know the position of a button, you could use the WarpPointer command to place the pointer on the button and then press return. Can you send a return event with an FVWM command ? thanks, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Relief Patch
These were only my thooughst. If you redo the patch (possibly fixing the negative Frame or, instead, making it absolete by new options), it is likely that your solution (whichever it will be) is applied. With the frame bug fixed, are there any preferences for my Relief option for FvwmButtons (to be able to customize a bit more when to use relief) ? - Either i introduce an option Relief [OnlyUp|OnlyDown|Both] for drawing relief in both up,down or both states (this patch is ready) - Or, as Mikhael proposed, i give more customization power, and insert 2 options UpRelief [flat|raised|sunken] and DownRelief [flat|raised|sunken] (introducing the possibility of having sunken relief for both up and down state) I'm sorry to bother you with questions on such a small patch, but as i am new to this, I would like to get some opinions before adding another option to FVWM. thanks, Remko -- Visit the official FVWM web page at URL: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]
Relief Patch
Hello FVWM workers,
I wrote a patch for a minor adjustment for the FvwmButtons module. I
added an extra FvwmButtons option 'Relief reliefmode' to specify when
relief of the button should be drawn: only in the up state, only in the down
state, or in both states (default).
The reason i wanted this was so that my buttons can integrate nicely
with my desktop. An example can be seen on
http://www.cs.kuleuven.ac.be/~remko/fvwm/screenshot2.png, where i only draw
relief when a button is down (i.e. the panel is open).
I don't know if you are interested in putting this in the official fvwm
branch. If so, it might be good to check my patch for bugs ;-)
Finally i have one question: Line 357 of 'draw.c' in FvwmButtons sets
the frame width to the absolute value of the frame; however, the manual
states that a negative value for a frame simply inverts the
relief/shadow. With this line, it does not. Why is that ?
cheers,
Remko
PS: I am not on the fvwm-workers list.
diff -u -r fvwm-2.5.5/modules/FvwmButtons/FvwmButtons.1
fvwm-2.5.5.patched/modules/FvwmButtons/FvwmButtons.1
--- fvwm-2.5.5/modules/FvwmButtons/FvwmButtons.1Sat Nov 9 16:18:52 2002
+++ fvwm-2.5.5.patched/modules/FvwmButtons/FvwmButtons.1Wed Feb 5
16:45:45 2003
@@ -169,6 +169,11 @@
Specifies a background pixmap to use. Specify none (without the
double quotes) for a transparent background.
+.IP *FvwmButtons: Relief \fImode\fP
+Specifies when to draw relief around the button. \fImode\fP is either
+\fIUp\fP, \fIDown\fP or \fIBoth\fP for drawing relief only when
+the button is up, down, or in both cases.
+
.IP *FvwmButtons: Rows \fIrows\fP
Specifies the number of rows of buttons to be created. The default
is 2 rows.
diff -u -r fvwm-2.5.5/modules/FvwmButtons/FvwmButtons.c
fvwm-2.5.5.patched/modules/FvwmButtons/FvwmButtons.c
--- fvwm-2.5.5/modules/FvwmButtons/FvwmButtons.cTue Nov 5 13:30:29 2002
+++ fvwm-2.5.5.patched/modules/FvwmButtons/FvwmButtons.cWed Feb 5
16:45:46 2003
@@ -779,6 +779,7 @@
UberButton-title = MyName;
UberButton-swallow = 1; /* the panel is shown */
+ UberButton-relief = RELIEF_BOTH; /* By default, show both reliefs */
/* parse module options */
ParseConfiguration(UberButton);
diff -u -r fvwm-2.5.5/modules/FvwmButtons/FvwmButtons.h
fvwm-2.5.5.patched/modules/FvwmButtons/FvwmButtons.h
--- fvwm-2.5.5/modules/FvwmButtons/FvwmButtons.hTue Oct 1 09:03:29 2002
+++ fvwm-2.5.5.patched/modules/FvwmButtons/FvwmButtons.hWed Feb 5
16:45:46 2003
@@ -89,6 +89,7 @@
0x0200 /* By default this only done on Popup */
#define b_Id 0x0400 /* Has a user defined id for referencing */
#define b_IconAlpha 0x0800 /* Icon has an alpha chanel */
+#define b_Relief 0x1000 /* When to use relief */
/* Flags for b-swallow */
#define b_Count 0x0003 /* Init counter for swallowing */
@@ -139,6 +140,7 @@
Pixel bc,hc,sc; /* b_Back !b_IconBack */
FvwmPicture *backicon; /* b_Back b_IconBack */
ushort minx,miny;/* b_Size */
+ byte relief; /* b_Relief */
};
typedef struct
@@ -169,6 +171,10 @@
char *back; /* b_Back */
char *fore; /* b_Fore */
int colorset;/* b_Colorset */
+#define RELIEF_UP 0x1 /* Use relief only in up state */
+#define RELIEF_DOWN 0x2/* Use relief only in down state */
+#define RELIEF_BOTH 0x3/* use relief in both states */
+ byte relief; /* b_Relief */
byte xpad,ypad; /* b_Padding */
signed char framew; /* b_Frame */
byte justify;/* b_Justify */
diff -u -r fvwm-2.5.5/modules/FvwmButtons/button.c
fvwm-2.5.5.patched/modules/FvwmButtons/button.c
--- fvwm-2.5.5/modules/FvwmButtons/button.c Tue Oct 1 09:03:29 2002
+++ fvwm-2.5.5.patched/modules/FvwmButtons/button.c Wed Feb 5 16:45:46 2003
@@ -309,6 +309,24 @@
return -1;
}
+byte buttonRelief(button_info *b)
+{
+button_info *bb = b;
+if (bb-flags b_Relief)
+return bb-relief;
+else if (bb-flags b_Container bb-c-flags b_Colorset)
+return bb-relief;
+while ((bb = bb-parent))
+{
+if (bb-c-flags b_Relief)
+return bb-c-relief;
+}
+#ifdef DEBUG
+fprintf(stderr,%s: BUG: No relief definition?\n,MyName);
+#endif
+return RELIEF_BOTH;
+}
+
int buttonBackgroundButton(button_info *b, button_info **r_b)
{
button_info *tmpb, *pb;
@@ -515,6 +533,7 @@
b-c-back=safestrdup(rgb:90/80/90);
b-c-fore=safestrdup(black);
b-c-framew=2;
+b-c-relief=RELIEF_BOTH;
}
}
diff -u -r fvwm-2.5.5/modules/FvwmButtons/button.h
fvwm-2.5.5.patched/modules/FvwmButtons/button.h
--- fvwm-2.5.5/modules/FvwmButtons/button.h Tue Oct 1 09:03:29 2002
+++ fvwm-2.5.5.patched/modules/FvwmButtons/button.h Wed Feb 5 16:45:46 2003
@@ -42,6 +42,7 @@
Pixel buttonHilite(button_info*);
Pixel buttonShadow(button_info*);
int
Re: FVWM: Some suggestions -a rant
my point: fvwm2 could have a nicer default look I think... I agree with the fact that the default look (the pink one) is rather ugly, which is the reason for most people not to use FVWM at all. However, a lot of window managers and desktop managers seem to have a sober default look and feel, probably because maybe nobody likes that look, but it irritates no one either. My impression is that most people however use most of these window managers, because they have seen a lot of fancy screenshots, proving that you _can_ make it look verry classy. And personally, i think this is a problem with FVWM: most of the screenshots on the webpage are not stylish. Don't get me wrong, the screenshots show different nice features of FVWM, but if you look at the big picture, the screenshots seem to revolt a lot of people. So a suggestion for making FVWM more appealing: add some screenshots of 'designer' look and feels (with nice title bars with pixmaps etc.) I am currently changing the look of my FVWM again, and maybe i can contribute a screenshot in the near future. don't get me wrong.. the web site is nice Personally, i think the site could be a lot more appealing and modern too (without making it heavy). But of course, it is easy to criticize someone else's work, and i am not too great at original web design either. When i have some time, i might propose a new look for the FVWM website. Just my 2 cents, Remko PS: It goes without saying that i think FVWM is the best window manager around ;) -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Some suggestions -a rant
fvwm-themes), but the great thing about fvwm is that it's as configurable in it's behaviour as it is in the looks. I don't think any of us doubts about that. But you can't 'show' how handy and configurable a window manager's feel is; however, you _can_ show how configurable a window manager's look is. Using a window manager is like falling in love: first you need shallow, visual attraction, and after a while you discover the internals, the 'real stuff', and only then you truly know that this is the one for you. Without the latter it can't last, but without the former it won't start. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: Display update while dragging
Hi, When i drag (or resize) a window in FVWM, other applications do not update the display. I was wondering if there is a way of solving this ? cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Acrobat Reader refuse to move in FVWM!
Disabling MwmFunctions fixed the problem for me. I have been having the same problem for a while now (Acrobat refusing to move after a fullscreen view), and this fixes the problem for me too. thanks, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: QuitFunction
Hi all, I know this was a post of a while ago, but has this been implemented yet? Will it ever be ? cheers, Remko On 13 Aug 2002, Mikhael Goikhman wrote: Now when I think about this, I see an elegant solution for these problems. We only need 2 functions (not including Session*Function variants), StartFunction and ExitFunction. StartFunction may include conditions StartUp and Restart, ExitFunction may include conditions Restart and Quit, these conditions are always false anywhere else. This way InitFunction and RestartFunction are not needed (not that RestartFunction is needed now anyway). AddToFunc StartFunction + I FvwmPager AddToFunc ExitFunction + I On (Quit) Exec killall xplanet-runner + I On (Restart) Exec play /some/ding.au + I Echo Either Restart or Quit -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: QuitFunction
Hi, I am using xplanet to update my background every couple of minutes. When i quit fvwm, i would like to kill xplanet so that it doesn't keep on running. A QuitFunction (called only when actually quitting) would be convenient for this, but i can't seem to find it in the manual. Why is this ? thanks, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: QuitFunction
It's named ExitFunction. Yes, i saw the ExitFunction. But the man page says that this function is called on restarts also. I only want to kill xplanet when actually quitting. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: QuitFunction
Well, you may start xplanet in StartFunction instead of InitFunction and ExitFunction will work for you like you want. That's not really what you would want to do with xplanet. Or run an fvwm wrapper like this: xplanet fvwm killall xplanet # or: kill `pidof xplanet` This is indeed a solution, but i was wondering if it could be moved inside fvwm. Is there a reason why there is no such QuitFunction ? cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: QuitFunction
I don't see a problem with this. It's a pure luxury problem. When fvwm is restarted, xplanet doesn't have to be restarted because all it does is update the background. Restarting it on every fvwm restart is CPU intensive, and causes the background to blank out for a few seconds. Noone just needed it, because other solutions exist. We would also need PreRestartFunction for completeness. I'm not saying that i _really_ need it, because as you said before, it can be moved out of fvwm inside a wrapper. But now that i read the manual more thoroughly, i get your point on needing Pre-restart functions. I had the impression that the functions were organized this way (which they aren't): - InitFunction: called upon initialization only - QuitFunction (doesn't exist): called when the user quits only - StartFunction: called after InitFunction (when initing) or after RestartFunction (when restarting) - RestartFunction: called before QuitFunction (when quitting) or before StartFunction (when restarting) My intuition behind this was that, things you want to do before a restart (RestartFunction) and after a restart (StartFunction) , you also want to do before quitting and after initing respectively. I hope this makes any sense to you at all ;) cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: QuitFunction
Why don't you just start it in the ~/.xinitrc file? That's what i was planning to do. But for some strange reason, i preferred to have it in my fvwmrc, and have as less as possible inside my .xinitrc. (i know, it's a purely subjective principle, but that's just my feeling :) Anyway, i'll stick with the .xinitrc file. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: QuitFunction
StartFunction may include conditions StartUp and Restart, ExitFunction may include conditions Restart and Quit, these conditions are always false anywhere else. This way InitFunction and RestartFunction are not needed (not that RestartFunction is needed now anyway). ... Your approach is indeed cleaner and more general than what i had in mind. Another advantage about this is that it's backward compatible. I don't know whether it is more intuitive or not. It is to me ! cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Scroll Lock mode
Oh dear! You've lived with the most frequently encountered problem for a year without knowing that the solution is written in big friendly letters right at the front of the fvwm FAQ. ;-) Oops. Didn't see that one :( Then again, it took me a year to find out that it was due to the modifiers that things stopped working. I still don't understand why these modifiers get turned on from time to time. Thanks for the tip ! Another small question: Is it possible that DGradient doesnt work in the development versions ? I have a line MenuStyle * MenuFace DGradient 128 2 grey50 50 grey95 50 grey50 but it doesnt seem to do anything since i upgraded. Thanks a lot, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Scroll Lock mode
It works fine here. What version did you upgrade to? If you switched to using colour sets for menus, the MenuFace style does not work anymore. You have to use the builtin Colorset command to change the gradient (2.5.x) I'm not using colorsets. It's definitely a bug. The problem is that i can't seem to pinpoint the reason for it. This is what happens: - When i use anti-aliased fonts in my menu (e.g. with MenuStyle * Font xft:Arial:size=11), i never get the gradient. - When i don't use the anti-aliased font, sometimes the gradient shows, sometimes it doesn't. What i get all the time is the thing seen on http://spike.ulyssis.org/tmp/snap.png The blue rectangle for highlighting the active menu item doesnt get cleared, and leaves a trace behind. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: FvwmButtons 'hangon'
Hi there, I would like to create a panel for X-Chat using FvwmButtons, but i seem to have some problems. When X-chat is started, it gets the title X-Chat [1.8.9]: my_nick @ irc.myserver.org / #mychannel So, i define a panel *FvwmButtons: (Icon mini.xchat.xpm, \ Panel(position top,right,delay 0,UseOld,NoClose) \ X-Chat* Nop) However, X-chat doesnt seem to hang itself on the button. The wildcard should be correct, because Style X-Chat* NoTitle removes the title from the X-Chat window. Is there a solution to this problem ? A second problem i have with the FvwmButtons module is the following: i define a button just identical to the one above (i.e. with UseOld and NoClose). When i restart FVWM with the application of the button visible, everything is ok: i can still click the button to show/hide the application. But, after i restart FVWM when the application is in the hidden state, clicking the button doesnt do anything. The application is still running however, but i can't get a hold of it anymore. Is this normal ? Thanks a lot, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: Scroll Lock mode
Hi again, I have been coping with a specific problem ever since i started using fvwm one year ago. For some reason, from time to time my key bindings stopped working, and closing windows by clicking on the button in the top left corner of the window didn't work either. Because i couldn't reproduce the error, i didn't mention it (yet). However, i seem to have found the reason: going into 'Scroll Lock' mode seems to change some things that make fvwm ignore these events. It's a mystery to me how i get into that 'scroll lock' mode, but pressing scroll lock seems to solve the problem every time (and pressing it again causes the events to be ignored again). Is there a solution to this ? cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: Some problems
Hi, I am experiencing some problems with both FVWM 2.5.2 and the snapshot of 20020704. However, i'm not sure if these problems are due to fvwm or to other apps. First of all, when i add the line FontPath unix/:7101 to my XFree config file (to be able to use my truetype fonts), and i try starting fvwm, i only get an hourglass, and nothing happens. Removing the line, starting fvwm, and then using xset fp+ unix/:7101 to use xfstt seems to work fine. Another problem i am coping with, even with older versions of fvwm, can be seen on http://spike.ulyssis.org/tmp/snap.png When i move my mouse pointer quickly over the menu items, there seems to be a 'refresh' problem, leaving some blue spots of my highlight rectangle near the right arrows. The problem doesn't occur with XFree 3.3.6. Does anyone know what might cause these problems ? thanks, Remko PS: I run Debian (unstable) with XFree 4.1.0 and xfstt 1.2.1. -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Some problems
I am experiencing some problems with both FVWM 2.5.2 and the snapshot of 20020704. However, i'm not sure if these problems are due to fvwm or to other apps. Sorry about my last post, the errors i described don't occur in the snapshot any more. I just loaded the wrong version. Also, i should have used the bug tracking system instead of mailing it here. Sorry about that. cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
