Re: FVWM: window placement preference
On Tue, Jan 23, 2007 at 12:04:13PM -0500, Emilie Ann Phillips wrote: Is it possible to have windows default placement to be at the center of the page, Sure, with CenterPlacement. and then cascade rather than from left to right? I don't understand what you want. Ciao Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: FVWM: window placement preference
On 1/25/07, Dominik Vogt [EMAIL PROTECTED] wrote: On Tue, Jan 23, 2007 at 12:04:13PM -0500, Emilie Ann Phillips wrote: Is it possible to have windows default placement to be at the center of the page, Sure, with CenterPlacement. and then cascade rather than from left to right? I don't understand what you want. Is it this? (image in annex) Cheers Renato cascade.png Description: PNG image
Re: FVWM: window placement preference
and then cascade rather than from left to right? I don't understand what you want. I mistyped. What I meant was the first window gets placed in the center, and subsequent windows get tiled to the left and the right of the center and then when all the screen has been taken up, the windows get cascaded over top of each other out from the center. I just tried Style * CenterPlacement and the behavior I got was a little odd. If my cursor is over my left monitor, the new window gets placed in the center of that monitor. If my cursor is over my right monitor, the new window gets placed at the very left of that monitor. And, there doesn't appear to be any tiling or cascading. All windows appear in the same spot. (which fits the description in the man page) I then tried MinOverlapPlacement to see how it worked, and it also gave me bizarre behavior on the right monitor but did what I expected on the left monitor. As far as I know, I don't have anything special set up for my two monitors. I am using fvwm 2.5.19 and fedora core 5. For now, I'll just go back to using the default TileCascadePlacement Emilie
Fwd: FVWM: window placement preference
Hmm. Google Mail somehow forgot that I wanted to write to the list. Here's the mail again. -- Forwarded message -- From: Hans Voss [EMAIL PROTECTED] Date: Jan 25, 2007 4:36 PM Subject: Re: FVWM: window placement preference To: Emilie Ann Phillips [EMAIL PROTECTED] Yeah, it is the second monitor setup that does weird things. FVWM CenterPlacement still sees both monitors as one large screen and tries to place the window in the center of it. [Try that with the primary on the right and secondary on the left, (so: SEC.|PRI. instead of PRI.|SEC.). FVWM still thinks the large desktop is build as PRI.|SEC. even though explicit placement on a screen upholds the correct placement of primary and secondary screens]. On 1/25/07, Emilie Ann Phillips [EMAIL PROTECTED] wrote: and then cascade rather than from left to right? I don't understand what you want. I mistyped. What I meant was the first window gets placed in the center, and subsequent windows get tiled to the left and the right of the center and then when all the screen has been taken up, the windows get cascaded over top of each other out from the center. I just tried Style * CenterPlacement and the behavior I got was a little odd. If my cursor is over my left monitor, the new window gets placed in the center of that monitor. If my cursor is over my right monitor, the new window gets placed at the very left of that monitor. And, there doesn't appear to be any tiling or cascading. All windows appear in the same spot. (which fits the description in the man page) I then tried MinOverlapPlacement to see how it worked, and it also gave me bizarre behavior on the right monitor but did what I expected on the left monitor. As far as I know, I don't have anything special set up for my two monitors. I am using fvwm 2.5.19 and fedora core 5. For now, I'll just go back to using the default TileCascadePlacement Emilie -- Met vriendelijke groeten / With kind regards Hans Voss --- * Senior Consultant Open Source, Networking and Security * google talk enabled * General Open Sourcerer. -- Met vriendelijke groeten / With kind regards Hans Voss --- * Senior Consultant Open Source, Networking and Security * google talk enabled * General Open Sourcerer.
FVWM: Wierd errors with UNICODe fonts and 2.5.18
Hello *, I run Fvwm 2.5.18 and become bombed with the following errors: 8- [FVWM][FlocaleGetFontSet]: (-adobe-helvetica-bold-r-normal--12-120-75-75-p-70-iso10646-1) Missing font charsets: ISO8859-1, ISO8859-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 [FVWM][FlocaleGetFontSet]: (-adobe-helvetica-bold-r-normal--12-*-*-*-*-*-iso10646-1) Missing font charsets: JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 [FVWM][FlocaleGetFontSet]: (-adobe-helvetica-medium-r-normal--12-120-75-75-p-70-iso10646-1) Missing font charsets: ISO8859-1, ISO8859-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 [FVWM][FlocaleGetFontSet]: (-adobe-helvetica-medium-r-normal--14-100-100-100-p-76-iso10646-1) Missing font charsets: ISO8859-1, ISO8859-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 [FVWM][FlocaleGetFontSet]: (-adobe-helvetica-medium-r-normal--10-100-75-75-p-56-iso10646-1) Missing font charsets: ISO8859-1, ISO8859-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 [FVWM][FlocaleGetFontSet]: No more missing charset reportings [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from ISO-IR-14 to UTF-8 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from ISO-IR-14 to UTF-8 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from ISO-IR-14 to UTF-8 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from ISO-IR-14 to UTF-8 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from ISO-IR-14 to UTF-8 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from ISO-IR-14 to UTF-8 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from ISO-IR-14 to UTF-8 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from ISO-IR-14 to UTF-8 [FvwmButtonsRight][FlocaleGetFontSet]: (-adobe-helvetica-medium-r-normal--14-100-100-100-p-76-iso10646-1) Missing font charsets: ISO8859-1, ISO8859-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 [FvwmButtonsTop][FlocaleLoadFont]: WARNING -- can't load font '-adobe-courier-medium-r-normal--14-100-100-100-p-76-iso10646-1', trying default: -*-fixed-medium-r-semicondensed-*-13-*-*-*-*-*-*-*,-*-fixed-medium-r-normal-*-14-*-*-*-*-*-*-*,-*-*-medium-r-normal-*-16-*-*-*-*-*-*-* [FvwmTaskBar][FlocaleGetFontSet]: (-adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso10646-1) Missing font charsets: ISO8859-1, ISO8859-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 [FvwmTaskBar][FlocaleGetFontSet]: (-adobe-helvetica-bold-r-normal--12-120-75-75-p-70-iso10646-1) Missing font charsets: ISO8859-1, ISO8859-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 [FvwmTaskBar][FlocaleGetFontSet]: (-adobe-courier-bold-r-normal--12-120-75-75-m-70-iso10646-1) Missing font charsets: ISO8859-1, ISO8859-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 [FvwmButtonsRight1][FlocaleGetFontSet]: (-adobe-helvetica-medium-r-normal--10-100-75-75-p-56-iso10646-1) Missing font charsets: ISO8859-1, ISO8859-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 [FvwmButtonsTop1][FlocaleGetFontSet]: (-adobe-helvetica-medium-r-normal--8-80-75-75-p-46-iso10646-1) Missing font charsets: ISO8859-1, ISO8859-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 [FvwmPager][FlocaleGetFontSet]: (-adobe-helvetica-medium-r-normal--8-80-75-75-p-46-iso10646-1) Missing font charsets: ISO8859-1, ISO8859-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 [FvwmPager][FlocaleGetFontSet]: (-adobe-helvetica-medium-r-normal--10-100-75-75-p-56-iso10646-1) Missing font charsets: ISO8859-1, ISO8859-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from ISO-IR-14 to UTF-8 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from ISO-IR-14 to UTF-8 [FVWM][convert_charsets]: WARNING - Invalid byte sequence during conversion from ISO-IR-14 to UTF-8 [FVWM][get_menu_options]: ERROR invalid position arguments 8- Why does fvwm want: ISO8859-1, ISO8859-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 If my whole System is UNICODE? iso10646-1 contain 1:1 ISO8859-1, so whats going on here? Note: I have menus where I need iso10646-1 (like with the UMLAUT) and my TaskbarStartMenu is shown right (e.g. Schließen and Ausführen). If i use iso8859-1 in the Font settings then the menus are not more correctly shown... Question: Can it be, that the TITLEBARS of windows do not support
FVWM: Skiplist (FvwmTaskBar) for windows
Hello, I have configured Desktop 3x2 and if I work a little bit heavy, I have sometimes over 80 windows open... Now I know I can limit the shown windows (in the FvwmTaskbar) to the windows on the current Page... Argh... I do not find the name of the option. Can anyone enlight me please? Greetings Michelle Konzack -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/6/6192519367100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
FVWM: Variables not working...
Hello *, I am ongoing to create a dynamic Fvwm configuration but I hit an error where icons are not more shown in FvwmButtons... In my definition of my FvwmButtonPanelTop I have: 8- PipeRead `echo -n *FvwmButtonsTop1: File ; tdfvwmbuttons $[FVWM_USERDIR]/FvwmButtonsTop.def` 8- which is working realy nice...where the FvwmButtonsTop.def is something like: 8- c:(6x2, Container) b:buttons/Button_Help b:buttons/Button_tdnewmsg b:buttons/Button_mutt b:buttons/Button_mozilla b:buttons/Button_gftp b:buttons/Button_xpdf b:buttons/Button_tdcheckserver b:buttons/Button_ssh b:buttons/Button_xterm b:buttons/Button_mc b:buttons/Button_editres b:buttons/Button_gimp c:(END) c:(2x2, Container) b:buttons/Button_tdxterm_mailcount_2x1 b:buttons/Button_OpenOffice_writer b:buttons/Button_OpenOffice_calc c:(END) b:buttons/Button_FvwmPager b:buttons/Button_xclock b:buttons/Button_wmmount b:buttons/Button_wmmon b:buttons/Button_wmifs b:buttons/Button_wmfsm b:buttons/Button_wmcpuload b:buttons/Button_xkill b:buttons/Button_shutdown 8- and it output a FvwmButtonsTop.real which is read by Fvwm. The button definitions went: 8- (1x1, \ Icon 32x32.xman.1.xpm, \ ActiveIcon 32x32.xman.1.xpm, \ PressIcon 32x32.xman.1.xpm, \ Action (Mouse 1) 'Exec xman -pagesize 900x656-75+76 -notopbox', \ Action (Mouse 2) Popup Button_menu_help, \ Action (Mouse 3) Popup Manpages \ ) 8- which I have changed to: 8- (1x1, \ Icon $[ICON_MSIZE].xman.1.xpm, \ ActiveIcon $[ICON_MSIZE].xman.1.xpm, \ PressIcon $[ICON_MSIZE].xman.1.xpm, \ Action (Mouse 1) 'Exec xman -pagesize 900x656-75+76 -notopbox', \ Action (Mouse 2) Popup Button_menu_help, \ Action (Mouse 3) Popup Manpages \ ) 8- But in the later one the Buttons do not more work and the Variable is set. Are variables not evaluated if I use: *FvwmButtonsTop1: File FvwmButtonsTop.real ? Greetings Michelle Konzack -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/6/6192519367100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: FVWM: Skiplist (FvwmTaskBar) for windows
On Thu, Jan 25, 2007 at 08:02:54PM +0100, Michelle Konzack wrote: Hello, I have configured Desktop 3x2 and if I work a little bit heavy, I have sometimes over 80 windows open... Now I know I can limit the shown windows (in the FvwmTaskbar) to the windows on the current Page... Argh... I do not find the name of the option. WindowListSkip is the Style option. In FvwmTaskBar, you can use: *FvwmTaskBar: UseSkipList -- Thomas Adam -- Wanting to feel; to know what is real. Living is a lie. -- Purpoise Song, by The Monkees.
Re: FVWM: Variables not working...
On Thu, Jan 25, 2007 at 08:03:10PM +0100, Michelle Konzack wrote: Are variables not evaluated if I use: *FvwmButtonsTop1: File FvwmButtonsTop.real Correct. Which is why you would use Read instead: In some file, you could have: ``` Test (!EnvIsSet MYICON) SetEnv MYICON xterm-sgi.xpm KillModule FvwmButtons F DestroyModuleConfig F:* *F: (1x1,Icon $[MYICON] Action(Mouse 1) 'Exec xman -pagesize 900x656-75+76 -notopbox',Action(Mouse 2) Popup Button_menu_help, Action(Mouse 3) Popup Manpages) Module FvwmButtons F ''' And then somewhere else: ``` Read $./MyButtonsFile ''' -- Thomas Adam -- Wanting to feel; to know what is real. Living is a lie. -- Purpoise Song, by The Monkees.
Re: Fwd: FVWM: window placement preference
On Thu, Jan 25, 2007 at 04:38:49PM +0100, Hans Voss wrote: Hmm. Google Mail somehow forgot that I wanted to write to the list. Here's the mail again. -- Forwarded message -- From: Hans Voss [EMAIL PROTECTED] Date: Jan 25, 2007 4:36 PM Subject: Re: FVWM: window placement preference To: Emilie Ann Phillips [EMAIL PROTECTED] Yeah, it is the second monitor setup that does weird things. FVWM CenterPlacement still sees both monitors as one large screen and tries to place the window in the center of it. [Try that with the primary on the right and secondary on the left, (so: SEC.|PRI. instead of PRI.|SEC.). FVWM still thinks the large desktop is build as PRI.|SEC. even though explicit placement on a screen upholds the correct placement of primary and secondary screens]. Well, have you Xinerama compiled in (see fvwm --version) and enabled? On 1/25/07, Emilie Ann Phillips [EMAIL PROTECTED] wrote: and then cascade rather than from left to right? I don't understand what you want. I mistyped. What I meant was the first window gets placed in the center, and subsequent windows get tiled to the left and the right of the center and then when all the screen has been taken up, the windows get cascaded over top of each other out from the center. I just tried Style * CenterPlacement and the behavior I got was a little odd. If my cursor is over my left monitor, the new window gets placed in the center of that monitor. If my cursor is over my right monitor, the new window gets placed at the very left of that monitor. And, there doesn't appear to be any tiling or cascading. All windows appear in the same spot. (which fits the description in the man page) I then tried MinOverlapPlacement to see how it worked, and it also gave me bizarre behavior on the right monitor but did what I expected on the left monitor. As far as I know, I don't have anything special set up for my two monitors. I am using fvwm 2.5.19 and fedora core 5. For now, I'll just go back to using the default TileCascadePlacement Ciao Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: Fwd: FVWM: window placement preference
On 1/25/07, Dominik Vogt [EMAIL PROTECTED] wrote: On Thu, Jan 25, 2007 at 04:38:49PM +0100, Hans Voss wrote: [snip] Well, have you Xinerama compiled in (see fvwm --version) and enabled? Yes, it is enabled and mostly it works, it is just the 'CenterPlacement' that doesn't handle it the way I would expect. -- Met vriendelijke groeten / With kind regards Hans Voss --- * Senior Consultant Open Source, Networking and Security * google talk enabled * General Open Sourcerer.
Re: Fwd: FVWM: window placement preference
Well, have you Xinerama compiled in (see fvwm --version) and enabled? Yes, it is enabled and mostly it works, it is just the 'CenterPlacement' that doesn't handle it the way I would expect. I also appear to have Xinerama support Emilie
