Re: FvwmBanner shapes
On Wed, Sep 19, 2001 at 10:56:11PM -0400, Dan Espen wrote:
Dominik Vogt fvwm-workers@fvwm.org writes:
On Tue, Sep 18, 2001 at 08:48:31AM -0400, Dan Espen wrote:
I think the 2.4.3 release should be built soon, but I'll stay out of
this discussion now. Dan, could you again decide when the release
should be built?
The shape changes seemed to work, I tested xeyes, shaped icons in
the builtin icon box, FvwmIconBox, and FvwmBammer with shapes enabled.
Did you do any tests with shape support disabled at configure?
If not, I'll rebuild and give it a shot.
Judging from the recent problem, I did more tests with shapes
disabled that with shapes enabled.
I'd imagine it would be hard to find an XServer without shape support
so if anyone has one, the tests don't take long. If no one has
one, I don't think its workh worring about since they can be disabled.
I didn't test this, but perhaps it's possible to rename the
libXext... files?
This is how FShape.[ch] works: THe header file is responsible for
including the shape.h header file if present. Otherwise all the
objects defined in shape.h are defined in FShape.h. Then, all
these macros, typdefs, functions etc. are aliased to a macro with
the same name, but a capital 'F' instead of the 'X'.
The FShapeInit() function queries the X server for the shape
extension and sets FShapesSupported, FShapeEventBase and
FShapeErrorBase accordingly. The FHaveShapeExtension macro is set
to 1 if SHAPE is defined and to 0 if not (that's what caused the
FvwmBanner problem: it was always 0). Without SHAPE defined, all
the functions are replaced with empty macros and FShapesSupported
is defined to 0.
With these definitions one can now simply write
if (FHaveShapeExtension)
{
/* lots of code */
if (FShapesSupported)
{
FShapeCombineRegion(...);
}
}
instead of using ifdef SHAPE. One big advantage is that the
syntax of all this code is always checked, even without SHAPE
defined. The optimizer should remove the unnecessary code as
if (FHaveShapeExtensinon/FShapesSupported)
is replaced by
if (0)
Anything else in the FShape change you think should be tested?
Basically, all modules with Colorset support also need the shape
extension. They should all work with a shaped colorset.
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 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]
Some quirky things with xinerama.
I'm using a stock redhat7.1 system, except I've upgraded to XFree 4.1.0 and have two monitor's with xinerama support working happily. But!... and this may actually be a fvwm-themes-devel question... With Screen1 LeftOf Screen0 |-| |--| | | | | | Screen1| | Screen0 | | | | | | | | | |-| |--| I'm finding strange quirky things like WindowList and other menus popping up on either screen. For instance I'm using latest fvwm cvs as well as fvwm-themes cvs, and choose CDE themes half of the cde button bar module appears halfway off the screen of Screen0 which is on the right like the #'s in the above diagram. And if you manually drag it into view say to Screen1 which I have on the left, then clicking on any menu on the cde button bar the menu pops up on Screen0 which is on the right!? So, is that my fault for trying to do things back to front? Alex -- 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]
Re: Some quirky things with xinerama.
On Thu, Sep 20, 2001 at 08:56:41PM +0930, Alex Wallis wrote: I'm using a stock redhat7.1 system, except I've upgraded to XFree 4.1.0 and have two monitor's with xinerama support working happily. But!... and this may actually be a fvwm-themes-devel question... With Screen1 LeftOf Screen0 |-| |--| | | | | | Screen1| | Screen0 | | | | | | | | | |-| |--| I'm finding strange quirky things like WindowList and other menus popping up on either screen. For instance I'm using latest fvwm cvs as well as fvwm-themes cvs, and choose CDE themes half of the cde button bar module appears halfway off the screen of Screen0 which is on the right like the #'s in the above diagram. And if you manually drag it into view say to Screen1 which I have on the left, then clicking on any menu on the cde button bar the menu pops up on Screen0 which is on the right!? So, is that my fault for trying to do things back to front? Since screen 1 is bigger in the picture, I guess that it it the screen your work on primarily. It looks as if the button bar would fit nicely on screen 1. Try using XineramaPrimaryScreen 1 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 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]
Re: Some quirky things with xinerama.
On Thu, Sep 20, 2001 at 08:56:41PM +0930, Alex Wallis wrote: I'm using a stock redhat7.1 system, except I've upgraded to XFree 4.1.0 and have two monitor's with xinerama support working happily. But!... and this may actually be a fvwm-themes-devel question... With Screen1 LeftOf Screen0 |-| |--| | | | | | Screen1| | Screen0 | | | | | | | | | |-| |--| I'm finding strange quirky things like WindowList and other menus popping up on either screen. For instance I'm using latest fvwm cvs as well as fvwm-themes cvs, and choose CDE themes half of the cde button bar module appears halfway off the screen of Screen0 which is on the right like the #'s in the above diagram. And if you manually drag it into view say to Screen1 which I have on the left, then clicking on any menu on the cde button bar the menu pops up on Screen0 which is on the right!? So, is that my fault for trying to do things back to front? fvwm-themes is not Xinerama compliant. This will be on the TODO list. Adding a line of the form: PipeRead 'echo *FvwmButtons-Panel: Geometry 860x77+`expr ( $[vp.width] - 860 ) / 2`[EMAIL PROTECTED]' ^^ to your modules-extra should fix the cde buttons geometry. BTW, maybe it will be good to have some Xinerama support in COMMAND EXPANSION (e.g., new variables) and FvwmM4. About the menus popup by the cde button the problems come from cfg lines of the form: *FvwmButtons-Panel: (3x2+33+0, Frame 1, Icon module/large/panel-arrow.xpm, \ Padding 1 1, Colorset 11, \ Action 'Menu MenuFvwmSystem rectangle $widthx$height+$left+$top o+50 -100m') *Maybe* this is a FvwmButtons/fvwm2/Xinerama bugs or miss feature. I do not know. Olivier -- 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]
Re: Some quirky things with xinerama.
Dominik Vogt wrote: On Thu, Sep 20, 2001 at 08:56:41PM +0930, Alex Wallis wrote: I'm using a stock redhat7.1 system, except I've upgraded to XFree 4.1.0 and have two monitor's with xinerama support working happily. But!... and this may actually be a fvwm-themes-devel question... With Screen1 LeftOf Screen0 |-| |--| | | | | | Screen1| | Screen0 | | | | | | | | | |-| |--| I'm finding strange quirky things like WindowList and other menus popping up on either screen. For instance I'm using latest fvwm cvs as well as fvwm-themes cvs, and choose CDE themes half of the cde button bar module appears halfway off the screen of Screen0 which is on the right like the #'s in the above diagram. And if you manually drag it into view say to Screen1 which I have on the left, then clicking on any menu on the cde button bar the menu pops up on Screen0 which is on the right!? So, is that my fault for trying to do things back to front? Since screen 1 is bigger in the picture, I guess that it it the screen your work on primarily. It looks as if the button bar would fit nicely on screen 1. Try using Oh, I just can't draw. Both monitors are at the same size and same res of 1024x768 at 16 bpp, but the left is a 16M savage4 card and the right has a 4M ATI card. The left monitor should also be capable of 1600 x 1200, but I haven't figured out how to get it to work with different sizes. XineramaPrimaryScreen 1 That fixes the menus on the cde button bar module, but the built-in WindowList(right click) or windowops menus appear on the left when right-clicking on the right desktop on Screen0? Many thanks again. :) Alex -- 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]
Notification: incoming/784
FVWM Bug Tracking notification new message incoming/784 Message summary for PR#784 From: [EMAIL PROTECTED] Subject: Certain thin borders do not get redrawn after expose Date: Thu, 20 Sep 2001 17:29:38 -0500 0 replies 0 followups ORIGINAL MESSAGE FOLLOWS From [EMAIL PROTECTED] Thu Sep 20 17:29:39 2001 Received: from karazm.math.uh.edu ([129.7.128.1]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 15kCKB-00017V-00 for [EMAIL PROTECTED]; Thu, 20 Sep 2001 17:29:39 -0500 Received: from malifon.math.uh.edu (IDENT:[EMAIL PROTECTED] [129.7.128.13]) by karazm.math.uh.edu (8.9.3/8.9.3) with ESMTP id RAA12339 for [EMAIL PROTECTED]; Thu, 20 Sep 2001 17:29:38 -0500 (CDT) From: [EMAIL PROTECTED] Received: from localhost ([127.0.0.1] ident=65534) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 15kCKA-00017R-00 for [EMAIL PROTECTED]; Thu, 20 Sep 2001 17:29:38 -0500 To: [EMAIL PROTECTED] Subject: Certain thin borders do not get redrawn after expose Message-Id: [EMAIL PROTECTED] Date: Thu, 20 Sep 2001 17:29:38 -0500 Full_Name: Kekoa Proudfoot Version: 2.2.4 CVS_Date: OS: redhat 7.1 X_Server: xfree86 Submission from: (NULL) (171.64.77.61) The following FVWM config file style causes borders which are not redrawn after they are exposed: Style * MWMBorder, BorderWidth 1, NoHandles The easiest way to see this is to place the top window over a window with these thin borders, then move the top window away. That should make it pretty obvious, especially if the top window's contents are significantly different from the border color. Playing around with this some, I did find a workaround, which is to turn off MWMBorder using FVWMBorder. Since the borders are so thin they appear identical using this method. -Kekoa -- 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]
