Re: A naive Xinerama question
On Mon, Aug 13, 2001 at 10:27:12AM -0400, Dan Espen wrote:
> Dominik Vogt writes:
> > On Tue, Aug 07, 2001 at 01:05:22PM +0200, Olivier Chapuis wrote:
> > > BTW, I think that the change Xinerama{Enable,Disable} -> Xinerama
> > > is not very good: it is difficult to a configuration tool or a user
> > > new to Xinerama to know if Xinerama is enabled or not.
> >
> > Er, what is the big difference between
> >
> > XineramaEnable
> > XineramaDisable
> >
> > and
> >
> > Xinerama on
> > Xinerama off
> >
> > ? It just saves the additional commands. And I can't think of
> > any fvwm command that has an "off" and an "on" version.
>
> Iconify on
> Iconify off
That's what I said. You have one command with an "on" and an
"off" option instead of "Iconify" and "Deiconify". This makes
toggling these settings possible in the first place. My wording
was a bit unfortunate, perhaps.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, email: [EMAIL PROTECTED]
LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen
fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20
--
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: A naive Xinerama question
Dominik Vogt writes:
> On Tue, Aug 07, 2001 at 01:05:22PM +0200, Olivier Chapuis wrote:
> > BTW, I think that the change Xinerama{Enable,Disable} -> Xinerama
> > is not very good: it is difficult to a configuration tool or a user
> > new to Xinerama to know if Xinerama is enabled or not.
>
> Er, what is the big difference between
>
> XineramaEnable
> XineramaDisable
>
> and
>
> Xinerama on
> Xinerama off
>
> ? It just saves the additional commands. And I can't think of
> any fvwm command that has an "off" and an "on" version.
Iconify on
Iconify off
--
Dan Espen
444 Hoes Lane Room RRC 1C-214 E-mail: [EMAIL PROTECTED]
Piscataway, NJ 08854 Phone: (732) 699-5570
--
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: xfm and moxfm: Once more unto the breach...
On Mon, Aug 13, 2001 at 08:21:11AM -0400, Bob Woodside wrote: > > Well, this one has led me a merry chase...and I'm still chasing. > > To recap the problem: it boils down to the need to suppress Xlib's > automatic grab when a mouse button is pressed, and the unwanted > LeaveNotify/EnterNotify > events generated by that grab; and it's the Leave/Enter events that > confuse Xtlib's double-click translation logic. This automatic grab used > to be overridden by our button grabs on the parent window, but that's > not happening at present. > > The problem seems to be mostly confined to focus.c: focus_grab_buttons, > which doesn't quite work as intended. I've hacked it up to the point > where it does what I think was intended. It seems to work pretty well, > except that it breaks MouseFocusClickRaises. There is clearly some > additional synchronization needed that I haven't figured out yet. > > Dominik, if I can't work out the remaining piece in a few days, I'd > like to send you a patch to see if you have any ideas. (I'd rather not > commit my changes as they stand now, knowing that they will break > something.) No problem. Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- 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]
CVS domivogt: * Default MenuStyle also resets colour sets.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt01/08/13 07:25:27 Modified files: . : ChangeLog libs : defaults.h modules: ChangeLog modules/FvwmTheme: FvwmTheme.1 Log message: * Default MenuStyle also resets colour sets. * Typo fix in FvwmTheme man page. -- 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: xfm and moxfm: Once more unto the breach...
Well, this one has led me a merry chase...and I'm still chasing. To recap the problem: it boils down to the need to suppress Xlib's automatic grab when a mouse button is pressed, and the unwanted LeaveNotify/EnterNotify events generated by that grab; and it's the Leave/Enter events that confuse Xtlib's double-click translation logic. This automatic grab used to be overridden by our button grabs on the parent window, but that's not happening at present. The problem seems to be mostly confined to focus.c: focus_grab_buttons, which doesn't quite work as intended. I've hacked it up to the point where it does what I think was intended. It seems to work pretty well, except that it breaks MouseFocusClickRaises. There is clearly some additional synchronization needed that I haven't figured out yet. Dominik, if I can't work out the remaining piece in a few days, I'd like to send you a patch to see if you have any ideas. (I'd rather not commit my changes as they stand now, knowing that they will break something.) Cheers, Bob -- 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/758
On Mon, 13 Aug 2001, Dominik Vogt wrote:
> > How to reproduce: install
> > redhat-6.2/powertools/**/xforms{,-demos,-devel}-0.88-9, than run
> > /usr/lib/xforms/DEMOS/sliderall.
> > It creates an OverrideRedirect window (looking kinda TV onscreen menu).
> > When cursor passes over this window, something strange happens to fvwm (the
> > cursor can be moved away from sliderall window). First sign is that it
> > stops reacting to hotkeys (like CSM-Arrows, Alt-Tab etc.). And it shows a
> > previously focused window as focused, while the window itself realizes that
> > it had lost focus (xterm changes the cursor). These lasts until focusing
> > another window.
>
> Is it possible to run this on a SuSE system? Could you try to
> isolate the necessary files from the RH system and send them to
> me?
As I understand, SuSE is rpm-based? If true, it has to be able to
use RedHat's .rpms. For case it isn't, I've put the necessary files to
http://ulpc08.gsi.de/~yakimenk/tmp/xforms.tar.bz2 (that's just the
contents of xforms{,-demos}.rpm).
_
Dmitry Yu. Bolkhovityanov
[EMAIL PROTECTED]
The Budker Institute of Nuclear Physics
--
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/758
On Sun, Aug 12, 2001 at 02:54:38AM -0500, fvwm-bug wrote:
> FVWM Bug Tracking notification
>
> new message incoming/758
>
> Message summary for PR#758
> From: [EMAIL PROTECTED]
> Subject: Strange behaviour with XForms "sliderall" demo
> Date: Sun, 12 Aug 2001 02:54:37 -0500
> 0 replies 0 followups
>
> Full_Name: Dmitry Bolkhovityanov
> Version: 2.4
> CVS_Date:
> OS: Red Hat Linux 7.1
> X_Server: XFree86 4.0.3
> Submission from: (NULL) (140.221.9.192)
>
>
> How to reproduce: install
> redhat-6.2/powertools/**/xforms{,-demos,-devel}-0.88-9, than run
> /usr/lib/xforms/DEMOS/sliderall.
> It creates an OverrideRedirect window (looking kinda TV onscreen menu).
> When cursor passes over this window, something strange happens to fvwm (the
> cursor can be moved away from sliderall window). First sign is that it
> stops reacting to hotkeys (like CSM-Arrows, Alt-Tab etc.). And it shows a
> previously focused window as focused, while the window itself realizes that
> it had lost focus (xterm changes the cursor). These lasts until focusing
> another window.
Is it possible to run this on a SuSE system? Could you try to
isolate the necessary files from the RH system and send them to
me?
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, email: [EMAIL PROTECTED]
LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen
fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20
--
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: Problem setting font for default Style
>From fvwm bug report #735: > Full_Name: Beiad Ian Q. Dalton > Version: 2.4.0 > CVS_Date: > OS: Debian Sid > X_Server: Xfree86 4.0.3 > Submission from: (NULL) (65.5.95.44) > > > > Okay. I'm trying to use a scalable font in the window title, by defining > it > with the Style command in the config. I'm okay to use a 100 DPI font such > as "-adobe-helvetica-medium-r-*-*-20-*" but I am not okay to use a font > such as "-urw-urw bookman l-regular-r-normal-*-20-*-*-*-*-*-*-*" which is > a > scalable font. However, I'm able to use this font for my menus with the > MenuStyle command in my config. > > If I type into FvwmConsole the Style command, I am told: > [FVWM][CMD_Style]: > <> Bad style option: "" > If I type into FvwmConsole a similar MenuStyle command with the same font > string, it is accepted and used. That awfully sounds as like a syntax error in your style line. Try to enclose the font name in double quotes (it contais whitespace). If that does not help, pleas send me the command line you sent to FvwmConsole. > Also, and this may be an X server issue instead, I don't think so. Fvwm is unhappy with the command line. It tries to interpret the font name as a style, not as the argument to the Font style. > if I attempt to use a > 19-point helvetica instead of 20-point, it will fall back to the 'fixed' > font, even though (as far as I can tell) I have a scalable version of > helvetica installed. If I specify 19-point urw bookman l, I get 19 point. Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- 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/761
On Sun, Aug 12, 2001 at 10:21:46PM -0500, fvwm-bug wrote: > FVWM Bug Tracking notification > > new message incoming/761 > > Message summary for PR#761 > From: [EMAIL PROTECTED] > Subject: FvwmTheme man page > Date: Sun, 12 Aug 2001 22:20:24 -0500 > 0 replies 0 followups > > Full_Name: Jim Crigler > Version: 2.4.0 > CVS_Date: > OS: Linux 2.2.14/RH 6.2 > X_Server: XFree86 3.3.6 > Submission from: (NULL) (63.36.158.209) > > > I was nearly driven crazy by my inability to get the highlight color to > work > as documented in the FvwmTheme man page. In fact I cut and pasted from > that > man page to my .fvwm2rc, but the hilight color just wouldn't work. Then I > realized that there are two different spellings: > > HighlightColorset (in the FvwmTheme man page example .fvwm2rc) > and > HilightColorset (in the fvwm2 man page). > > Of course, only the latter is correct. A correction of the spelling in > the > former would be a great service to new users ... Thanks for the report. I will apply a patch to the man page as soon as possible. Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- 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/757
On Sat, Aug 11, 2001 at 09:46:00PM -0500, fvwm-bug wrote: > FVWM Bug Tracking notification > > new message incoming/757 > > Message summary for PR#757 > From: [EMAIL PROTECTED] > Subject: 2.4.0 won't compile > Date: Sat, 11 Aug 2001 21:45:59 -0500 > 0 replies 0 followups > > Full_Name: David Blaschke > Version: > CVS_Date: > OS: > X_Server: > Submission from: (NULL) (209.178.176.18) > > > I tried installing 2.4.0 and received the error message that MAX_SEQUENCE > was undeclared in events.c. Checking all of the programs and headers > revealed > that it is used by 3 programs, but never declared as far as I can tell. I > > also checked 2.2.5 and it isn't used in that version. Hope this helps. This is because you are compiling with version 0.5 of the strokes library. You have three options: 1) Compile without stroke support: $ ./configure --with-stroke-library=no 2) Downgrade libstroke to a version < 0.5. 3) Upgrade fvwm to the latest snapshot or development version (or wait for 2.4.1 where the problem is solved). Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- 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]
