Just committed
1) The Xinerama cleanup.
2) A big patch that makes move_resize.c and some related places
in other files use the types position, size_rect and rectangle.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
On Tue, Nov 23, 2021 at 01:44:52AM +0100, Dominik Vogt wrote:
> Menu foomenu monitor c c
>
> Should place the menu in the middle of the current monitor.
Or
Menu foomenu c-20 c+30
should place it 20% of the monitor size left from the center and
30% below the center.
Ciao
Dominik ^_^ ^_^
On Mon, Nov 22, 2021 at 11:52:38PM +, Thomas Adam wrote:
> On Tue, Nov 23, 2021 at 12:31:15AM +0100, Dominik Vogt wrote:
> > The old manmage said:
> >
> > XineramaRoot
> >
> > the root window of the whole Xinerama screen. Equivalent to
> > "
On Tue, Nov 23, 2021 at 12:31:15AM +0100, Dominik Vogt wrote:
> The old manmage said:
>
> XineramaRoot
>
> the root window of the whole Xinerama screen. Equivalent to
> "root" when Xinerama is not used.
>
> Can you please restate that for me? What is &
, a real one and still "xineramaroot" for
compatibility. Screenroot? Rootscreen? Just tell me a good
name.
The old manmage said:
XineramaRoot
the root window of the whole Xinerama screen. Equivalent to
"root" when Xinerama is not used.
Can you please restate that fo
uld be syntactically breaking people's configs, but... I
bet it's a rarely-used option that should just be "screenroot" or something.
> > > > ./perllib/FVWM/Commands.pm: descr => q{Move a window to
> > > > another Xinerama screen},
> >
> >
eramaroot"))
>
>
> Not sure what the right name of the option and the flag variable
> should be. There's only a placeholder in the man page either.
>
> > > ./perllib/FVWM/Commands.pm: descr => q{Move a window to
> > > another Xinerama screen
On Sat, Nov 20, 2021 at 10:24:46PM +, Thomas Adam wrote:
> On Sat, Nov 20, 2021 at 03:54:10PM +0100, Dominik Vogt wrote:
> > On Sat, Nov 20, 2021 at 02:15:58PM +, Thomas Adam wrote:
> > > On Sat, Nov 20, 2021, 14:13 Dominik Vogt wrote:
> > >
> > > >
On Sat, Nov 20, 2021 at 03:54:10PM +0100, Dominik Vogt wrote:
> On Sat, Nov 20, 2021 at 02:15:58PM +, Thomas Adam wrote:
> > On Sat, Nov 20, 2021, 14:13 Dominik Vogt wrote:
> >
> > > Is Xinerama still useful for anything or can we remove it?
> > >
>
On Sat, Nov 20, 2021 at 03:54:10PM +0100, Dominik Vogt wrote:
> On Sat, Nov 20, 2021 at 02:15:58PM +, Thomas Adam wrote:
> > On Sat, Nov 20, 2021, 14:13 Dominik Vogt wrote:
> >
> > > Is Xinerama still useful for anything or can we remove it?
> > >
>
On Sat, Nov 20, 2021 at 02:15:58PM +, Thomas Adam wrote:
> On Sat, Nov 20, 2021, 14:13 Dominik Vogt wrote:
>
> > Is Xinerama still useful for anything or can we remove it?
> >
> It has already been removed. Where are you seeing references to it?
Everywhere.
Is Xinerama still useful for anything or can we remove it?
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt05/10/14 14:43:00
Modified files:
fvwm : fvwm.1.in
Log message:
* Corrected a typo and rephrased some Xinerama docs.
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt04/09/06 05:08:59
Modified files:
. : ChangeLog
libs : FScreen.c
Log message:
* Fixed Xinerama crash.
--
Visit the official FVWM web page at URL:http://www.fvwm.org
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt04/08/26 04:40:42
Modified files:
. : ChangeLog NEWS configure.in
libs : FScreen.c
Log message:
* Fixed Solaris Xinerama configure test (nested AC_CHECK_LIB calls don't
20 Aug 2004 13:26:58 -
@@ -298,8 +298,18 @@
$UNSET ac_cv_lib_Xinerama_XineramaIsActive
AC_CHECK_LIB(Xinerama, XineramaIsActive,
with_xinerama=yes; Xinerama_LIBS=-lXinerama; AC_DEFINE(HAVE_XINERAMA),
+AC_CHECK_LIB(Xext, XineramaGetState,
+ [ AC_DEFINE(HAVE_XINERAMA
Dominik Vogt [EMAIL PROTECTED] writes:
Note that this nesting of AC_CHECK_LIB calls did not work with my
autoconf/automake versions. I have split it in two separate
calls.
Darn. And I tested this on Linux and Solaris.
I woke up in the middle of the night and it dawned on me that I never
On Thu, Aug 26, 2004 at 06:48:22AM -0400, Dan Espen wrote:
I woke up in the middle of the night and it dawned on me that I never
updated NEWS. I figured no one would notice and I could
take care of it when I got up.
Heh, now *that*'s what I call being passionate about one's work. :)
--
On Thu, Aug 26, 2004 at 06:48:22AM -0400, Dan Espen wrote:
Dominik Vogt [EMAIL PROTECTED] writes:
Note that this nesting of AC_CHECK_LIB calls did not work with my
autoconf/automake versions. I have split it in two separate
calls.
Darn. And I tested this on Linux and Solaris.
They
.
And the #ifdef'd code is now more sensible than it was, and
than I'd made it. Thanks.
But, there was one typo (capitalization error), and one
error in the #def's. Solaris' xinerama.h does *not* define
XineramaScreenInfo, since Solaris' xinerama system API is
*completely* different. I just
ac_cv_lib_Xinerama_XineramaIsActive
AC_CHECK_LIB(Xinerama, XineramaIsActive,
with_xinerama=yes; Xinerama_LIBS=-lXinerama; AC_DEFINE(HAVE_XINERAMA),
+AC_CHECK_LIB(Xext, XineramaGetState,
+ [ AC_DEFINE(HAVE_XINERAMA) AC_DEFINE(HAVE_SOLARIS_XINERAMA)
+ with_xinerama=yes; Xinerama_LIBS=-lXext
Dan Espen wrote:
I guess I can answer my own question, it configures but doesn't
compile:
gcc -DHAVE_CONFIG_H -I. -I../../version-2_5_11/libs -I.. -I../../version-2_5_11
-I/opt/public/include -I/usr/openwin/include -I/opt/public/include -g
-O2 -Wall -Wno-implicit-int -c
to check for the header in configure, and if
it's not present (Solaris 7 11/99, or Solaris 8) I could
just sub in the contents. They're quite minimal.
This seem to objectionable to people?
I don't see any problem with Xinerama only working on only Sol 9 or later.
In other words, requiring
Dan Espen wrote:
Didn't you say the Sol 9/10 header would work on Sol 8.
Why not make the header required. If someone wants Xinerama
on Sol 8, make them supply the header.
It does, but it seems like having the xinerama support enabled
with no user effort for Solaris 8 users would be worth
Chris Ross [EMAIL PROTECTED] writes:
Dan Espen wrote:
Didn't you say the Sol 9/10 header would work on Sol 8.
Why not make the header required. If someone wants Xinerama
on Sol 8, make them supply the header.
It does, but it seems like having the xinerama support enabled
Chris Ross [EMAIL PROTECTED] writes:
Chris Ross wrote:
Okay. I don't know how many of you know this, but Solaris ships
an Xsun that has Xinerama support in it (as of the last dist.
of Solaris 7). *But*, in typical Sun Microsystems style, there
is no Xinerama library, nor header
Dan Espen [EMAIL PROTECTED] writes:
Chris Ross [EMAIL PROTECTED] writes:
Chris Ross wrote:
Okay. I don't know how many of you know this, but Solaris ships
an Xsun that has Xinerama support in it (as of the last dist.
of Solaris 7). *But*, in typical Sun Microsystems style
Okay. I don't know how many of you know this, but Solaris ships
an Xsun that has Xinerama support in it (as of the last dist.
of Solaris 7). *But*, in typical Sun Microsystems style, there
is no Xinerama library, nor header file.
So, in doing some research, it appears there are a few
Chris Ross wrote:
Okay. I don't know how many of you know this, but Solaris ships
an Xsun that has Xinerama support in it (as of the last dist.
of Solaris 7). *But*, in typical Sun Microsystems style, there
is no Xinerama library, nor header file.
Oops. I should've mentioned
on Xinerama screens.
--
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]
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt02/05/03 06:00:53
Modified files:
. : configure.in
Log message:
* Clarified that --enable-xinerama-emulation is only useful for developers.
--
Visit the official FVWM web page at URL:http
a menu placement problem w/ xinerama.
--
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]
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt02/03/01 01:11:18
Modified files:
. : ChangeLog configure.in
utils : ChangeLog configure_dev.sh
Log message:
* Re-added with-xinerama-emulation optioen that vanished some
On Thu, Feb 21, 2002 at 12:20:28PM +, Darren Marshall wrote:
Attached is a patch to fix a problem where clicking the mouse button to popup
the windowlist on the secondary screen of an xinerama setup always pops up on
the primary screen.
I'll apply the patch shortly. Thanks for your help
Attached is a patch to fix a problem where clicking the mouse button to popup
the windowlist on the secondary screen of an xinerama setup always pops up on
the primary screen.
This e-mail and any attachments are confidential. If you are not the intended
recipient, please notify us
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: olicha 01/10/04 11:10:52
Modified files:
fvwm : fvwm2.1 style.c
. : ChangeLog
Log message:
* Added the possibility to add an Xinerama screen to the 4 numerics
Iconbox format
* Warning
On Thu, Sep 30, 2021 at 10:16:34PM +0200, Dominik Vogt wrote:
On Fri, Sep 28, 2001 at 05:23:18PM +0200, Olivier Chapuis wrote:
Hello,
I make some Xinerama test recently using Sls 1x2 on
my poor 800x600 screen:
---
| | |
| 0 | 1
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: olicha 01/10/02 06:18:41
Modified files:
. : ChangeLog
fvwm : menus.c
Log message:
* fixed Xinerama placement of menu with empty but not null position hints
--
Visit the official FVWM
placement fixes w/ Xinerama.
* New screen specifier 'w' for IconBox command.
--
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]
On Fri, Sep 28, 2001 at 05:23:18PM +0200, Olivier Chapuis wrote:
Hello,
I make some Xinerama test recently using Sls 1x2 on
my poor 800x600 screen:
---
| | |
| 0 | 1 |
| | |
---
The support seems really great! (BTW
stack.c update.c windowlist.c
libs : FScreen.c FScreen.h
Log message:
* Xinerama fixes for bugs reported by Olivier in menu code, WindowList.
* Applied Xinerama patches by Sidik (partially rewritten).
* Removed useless code pointed out by Suzanne Britton
On Fri, 28 Sep 2001, Olivier Chapuis wrote:
Hello,
I make some Xinerama test recently using Sls 1x2 on
my poor 800x600 screen:
---
| | |
| 0 | 1 |
| | |
---
The support seems really great! (BTW, does there exits
Hello,
I make some Xinerama test recently using Sls 1x2 on
my poor 800x600 screen:
---
| | |
| 0 | 1 |
| | |
---
The support seems really great! (BTW, does there exits
laptop with a double head video card?).
I've noted a few
Hi,
I'm preparing an SGI package of fvwm and I have a couple issues
with your implementation of Xinerama.
SGI is currently developing the Xinerama library as per the
latest spec (Actually SGI is even beyond the spec for certain
things)
It sounds like you're using an old spec. A couple
On Wed, 26 Sep 2001, Stephane Rosa wrote:
Hi,
I'm preparing an SGI package of fvwm and I have a couple issues
with your implementation of Xinerama.
SGI is currently developing the Xinerama library as per the
latest spec (Actually SGI is even beyond the spec for certain
things
Very interesting link, I wasn't aware of the xinerama sourceforge project.
To add to your speculation regarding the relations between the xinerama
apis: Since the sourceforge project leader and the x org xinerama task force
chair are the same person and Mark V of xfree86 is also a sourceforge
On Sun, 23 Sep 2001, Sidik Isani wrote:
Hello -
I have a suggestion for Xinerama, but I don't know enough about
automake to provide a patch: we could use configure options
telling fvwm2 where to look for the library and include files.
Also related to Xinerama, here are better
Hello Dmitry -
Thanks for taking a look at the patches. Comments on your comments
are below . . .
Dmitry Yu. Bolkhovityanov wrote:
|
|On Sun, 23 Sep 2001, Sidik Isani wrote:
|
| Hello -
|
| I have a suggestion for Xinerama, but I don't know enough about
| automake to provide a patch
Hello -
I have a suggestion for Xinerama, but I don't know enough about
automake to provide a patch: we could use configure options
telling fvwm2 where to look for the library and include files.
Also related to Xinerama, here are better versions of some patches
I posted before (now
diff -ru fvwm-snap-20010916/libs/FScreen.c fvwm-2.5.0-cfht/libs/FScreen.c
--- fvwm-snap-20010916/libs/FScreen.c Sat Sep 15 01:00:05 2001
+++ fvwm-2.5.0-cfht/libs/FScreen.c Tue Sep 18 20:41:10 2001
@@ -528,6 +528,27 @@
return 0;
}
+/* Returns the screen of which (global_x, global_y) is
this usage, the
starting desk/page can also be specified via a resource (e.g.,
--xrm 'Fvwm.Page: 1 0 2').
+-xrm '*page: 1 0 2').
.I StartsOnPage
in conjunction with
.I SkipMapping
@@ -5254,19 +5254,23 @@
A new window is placed on the specified Xinerama screen. The
default is to place windows
+ * USPosition so that it is relative to that particular screen.
+ * If we don't do this, then a geometry would completely cancel
+ * the effect of the StartsOnScreen style.
+ *
+ * So there are two ways to get a window to pop up on a particular
+ * Xinerama screen
, screen_y;
+ /*
+ * Translate x,y into local screen coordinates, in case Xinerama is used.
+ */
+ FScreenGetScreenXY(x, y, screen_x, screen_y);
+
if (Scr.gs.do_hide_position_window)
return;
position_geometry_window(eventp);
- (void) sprintf (str, GEOMETRY_WINDOW_POS_STRING, x, y
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
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
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
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
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/09/16 07:19:42
Modified files:
. : todo-3.0
Removed files:
. : todo-xinerama
Log message:
* Removed remaining todo items to todo-3.0 and deleted todo-xinerama
Hi!
As was mentioned some time ago, Xinerama API implementation in
XFree86 isn't an official X.org standard. And X environments other than
XFree86 use different (and incomplete, and undisclosed) Panoramix API.
A draft of upcoming standard API is available at
http
when the Xinerama command is
used. Let's assume Xinerama is enabled with two screens.
Style * IconBox [EMAIL PROTECTED]
puts the icon box at 0 0 of screen 1. Now,
Xinerama off
is issued. The @1 must now refer to the global screen since there
are no more Xinerama screens.
Bye
Dominik
be saved, but what for?
For recalculation of the icon boxes when the Xinerama command is
used. Let's assume Xinerama is enabled with two screens.
Thanks, now I understand.
I added the screen spec to the iconbox structure for the case when a
geometry style spec is used, but the IconBox can also
On Sat, Aug 18, 2001 at 08:28:54PM +0700, Dmitry Yu. Bolkhovityanov wrote:
Hi!
This patch deals with withdrawing Wharf to corners and with
in which direction panels should open.
Appliet. BTW, could you please include ChangeLog entries with
your patches?
BTW, there's a
with
your patches?
Ok. For this one it is Make FvwmWharf use current Xinerama
screen for choosing in which direction to slide panels and for withdrawn
position calculation (khm, a bit too long, shame on me...).
BTW, there's a strange error in drawing the panel's host button
Dominik Vogt fvwm-workers@fvwm.org writes:
On Mon, Aug 20, 2001 at 09:45:11AM -0400, Dan Espen wrote:
Dominik Vogt fvwm-workers@fvwm.org writes:
On Sun, Aug 19, 2001 at 06:45:32PM -0400, Dan Espen wrote:
Is there a way to test screen size changes without Xinerama working
to test screen size changes without Xinerama working?
With Xinerama emulation. Run configure with
$ ./configure --enable-xinerama-emulation
The screen is then split into two fake Xinerama screens and a
blank area that doesn't belong to any screen. To switch
Xinerama
On Sun, Aug 19, 2001 at 07:35:15PM -0400, Dan Espen wrote:
Dominik Vogt [EMAIL PROTECTED] writes:
Dan, I looked at the icon box code in style.c because I wanted to
make it work with changes of the Xinerama state, but the matter is
too complex to write a patch in short time for me.
What
On Sun, 19 Aug 2001, FVWM CVS wrote:
Log message:
* Applied Xinerama patch for Maximize command but changed syntax to
Maximize Screen screen-spec.
fvwm.org seems to be offline, so the question: would it be
possible to maximize on the same screen where the window currently is?
I.e
to
make it work with changes of the Xinerama state, but the matter is
too complex to write a patch in short time for me.
What I want to do:
1) Default to using the primary screen for icon box specs
(already works for X geometry like specs and is easy to do
On Mon, Aug 20, 2001 at 04:40:52PM +0700, Dmitry Yu. Bolkhovityanov wrote:
On Sun, 19 Aug 2001, FVWM CVS wrote:
Log message:
* Applied Xinerama patch for Maximize command but changed syntax to
Maximize Screen screen-spec.
fvwm.org seems to be offline, so the question: would
Dominik Vogt fvwm-workers@fvwm.org writes:
On Sun, Aug 19, 2001 at 06:45:32PM -0400, Dan Espen wrote:
Is there a way to test screen size changes without Xinerama working?
With Xinerama emulation. Run configure with
$ ./configure --enable-xinerama-emulation
The screen is then split
Dominik Vogt fvwm-workers@fvwm.org writes:
Currently, fvwm uses the icon boxes in the order of creation. So,
if one icon box is created on screen 0 and one is created on
screen 1, all icons are placed on screen 0 until the icon box is
full, then all icons are put on screen 1. My question was
On Mon, 20 Aug 2001, Dan Espen wrote:
Dominik Vogt fvwm-workers@fvwm.org writes:
Currently, fvwm uses the icon boxes in the order of creation. So,
if one icon box is created on screen 0 and one is created on
screen 1, all icons are placed on screen 0 until the icon box is
full, then all
On Mon, Aug 20, 2001 at 09:45:11AM -0400, Dan Espen wrote:
Dominik Vogt fvwm-workers@fvwm.org writes:
On Sun, Aug 19, 2001 at 06:45:32PM -0400, Dan Espen wrote:
Is there a way to test screen size changes without Xinerama working?
With Xinerama emulation. Run configure
Dominik Vogt fvwm-workers@fvwm.org writes:
On Mon, Aug 20, 2001 at 09:45:11AM -0400, Dan Espen wrote:
Dominik Vogt fvwm-workers@fvwm.org writes:
On Sun, Aug 19, 2001 at 06:45:32PM -0400, Dan Espen wrote:
Is there a way to test screen size changes without Xinerama working
Dmitry Yu. Bolkhovityanov [EMAIL PROTECTED] writes:
On Mon, 20 Aug 2001, Dan Espen wrote:
Dominik Vogt fvwm-workers@fvwm.org writes:
Currently, fvwm uses the icon boxes in the order of creation. So,
if one icon box is created on screen 0 and one is created on
screen 1, all icons are
Hi!
This patch deals with withdrawing Wharf to corners and with
in which direction panels should open.
BTW, there's a strange error in drawing the panel's host button.
When a vertical Wharf is at the right border (and a panel slides to the
left), after a panel completely
On Sat, Aug 18, 2001 at 06:59:56PM +0700, Dmitry Yu. Bolkhovityanov wrote:
On Fri, 17 Aug 2001, Dominik Vogt wrote:
On Fri, Aug 17, 2001 at 11:46:45AM +0700, Dmitry Yu. Bolkhovityanov wrote:
On Thu, 16 Aug 2001, Dominik Vogt wrote:
On Wed, Aug 15, 2001 at 08:30:20PM +0700, Dmitry
Dan, I looked at the icon box code in style.c because I wanted to
make it work with changes of the Xinerama state, but the matter is
too complex to write a patch in short time for me.
What I want to do:
1) Default to using the primary screen for icon box specs
(already works for X geometry
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/08/19 09:17:27
Modified files:
. : ChangeLog NEWS todo-xinerama
fvwm : fvwm2.1 move_resize.c placement.c screen.h
update.c virtual.c
With the latest commits, I think Xinerama support is complete.
It needs a bit polishing of the documentation, thoug. Probably a
separate Xinerama section in the man page is a good idea.
Everybody is welcome to help testing the patches, specifically
Xinerama placement of modules, new module
Dominik Vogt [EMAIL PROTECTED] writes:
Dan, I looked at the icon box code in style.c because I wanted to
make it work with changes of the Xinerama state, but the matter is
too complex to write a patch in short time for me.
What I want to do:
1) Default to using the primary screen
Oops, ignore that comment about
XineramaSupportGetNumberedScrRect.
--
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 URL:http://www.fvwm.org/.
To unsubscribe
On Fri, 17 Aug 2001, Dominik Vogt wrote:
On Fri, Aug 17, 2001 at 11:46:45AM +0700, Dmitry Yu. Bolkhovityanov wrote:
On Thu, 16 Aug 2001, Dominik Vogt wrote:
On Wed, Aug 15, 2001 at 08:30:20PM +0700, Dmitry Yu. Bolkhovityanov wrote:
I've added an optional global switch,
On Thu, 16 Aug 2001, Dominik Vogt wrote:
On Wed, Aug 15, 2001 at 08:30:20PM +0700, Dmitry Yu. Bolkhovityanov wrote:
I've added an optional global switch, which means that
maximization should be made on a global screen, otherwise it is made on
the screen where the center of a window
On Fri, Aug 17, 2001 at 11:46:45AM +0700, Dmitry Yu. Bolkhovityanov wrote:
On Thu, 16 Aug 2001, Dominik Vogt wrote:
On Wed, Aug 15, 2001 at 08:30:20PM +0700, Dmitry Yu. Bolkhovityanov wrote:
I've added an optional global switch, which means that
maximization should be made on a
, maximize it
there.
BTW, Dominik, was it done intentionally that in Xinerama emulation mode
the vertical separator doesn't separate, but in fact overlaps two
left pixels of the second pseudo-screen? The result seems a bit
confusing ;-)
You would have to ask Olivier. He wrote
if they are by
some part (not entirely) on it.
BTW, Dominik, was it done intentionally that in Xinerama emulation mode
the vertical separator doesn't separate, but in fact overlaps two
left pixels of the second pseudo-screen? The result seems a bit
confusing
Dominik Vogt fvwm-workers@fvwm.org 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
On Mon, Aug 13, 2001 at 10:27:12AM -0400, Dan Espen wrote:
Dominik Vogt fvwm-workers@fvwm.org 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
CVSROOT:/home/cvs/fvwm
Module name:fvwm-web
Changes by: domivogt01/08/11 03:28:36
Modified files:
. : ChangeLog mod_f2m_communication.html
Log message:
* Updated Xinerama module interface description.
--
Visit the official FVWM web page at URL:http
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/08/11 16:28:18
Modified files:
. : todo-xinerama
libs : XineramaSupport.c
modules: ChangeLog
modules/FvwmButtons: FvwmButtons.c
modules
By the way, Matthias, is there anything that has to be done to
make FvwmGtk Xinerama compatible?
Well, its been a long time since I last looked at that code...
compatible is perhaps not the right term here. Any X application
should be Xinerama compatible, since after all its just an extension
On Wed, Aug 08, 2001 at 07:47:03PM +0700, Dmitry Yu. Bolkhovityanov wrote:
On Wed, 8 Aug 2001, Matthias Clasen wrote:
On Tue, 7 Aug 2001, Olivier Chapuis wrote:
Hello,
I have a very naive Xinerama question:
Is it possible to send to modules a M_NEW_SCREEN message
reasonable (now I understand my mistake --
I was thinking about something similar to FvwmBacker, but for Xinerama
screens, which is a nonsense ;-).
We have an option to add such functionality right now, but with
fvwm tracking screens itself (this is needed anyway for emulated
Xinerama
: it will be able to manage a new/strong sticky mode
for any applications.
Well, that sounds very reasonable (now I understand my mistake --
I was thinking about something similar to FvwmBacker, but for Xinerama
screens, which is a nonsense ;-).
We have an option to add such functionality
But it would certainly be a useful addition to the Xinerama extension to
send EnterXineramaHead and LeaveXineramaHead events - IIRC X
extensions can introduce new events. If these events contain the a
head number, interested applications can then easily maintain
information
about
On Tue, 7 Aug 2001, Olivier Chapuis wrote:
Hello,
I have a very naive Xinerama question:
Is it possible to send to modules a M_NEW_SCREEN message
when the mouse pointer change of screen?
Technicaly it isn't possible -- X server wouldn't generate
EnterScreenNotify events, since
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
On Wed, 8 Aug 2001, Matthias Clasen wrote:
On Tue, 7 Aug 2001, Olivier Chapuis wrote:
Hello,
I have a very naive Xinerama question:
Is it possible to send to modules a M_NEW_SCREEN message
when the mouse pointer change of screen?
Technicaly it isn't possible -- X
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/08/06 17:50:22
Modified files:
. : todo-xinerama
fvwm : placement.c
modules: ChangeLog
modules/FvwmIdent: FvwmIdent.c Makefile.am
1 - 100 of 145 matches
Mail list logo
