CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/08/05 19:20:36
Modified files:
. : ChangeLog NEWS todo-xinerama
fvwm : commands.h functions.c functions.h fvwm2.1
move_resize.c move_resize.h
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/08/02 14:14:51
Modified files:
. : ChangeLog
fvwm : events.c events.h menus.c virtual.c
Log message:
* Xinerama / menu placement fix.
* Fixed button/key events over pan
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/08/02 18:06:20
Modified files:
. : ChangeLog NEWS todo-xinerama
fvwm : fvwm2.1 menus.c style.c virtual.c
libs : XineramaSupport.c XineramaSupport.h
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/08/02 18:08:47
Modified files:
. : todo-xinerama
Log message:
* Updated xinerama to do list.
--
Visit the official FVWM web page at URL:http://www.fvwm.org/.
To unsubscribe from the list
On 28 Jul 01 at 18:00, [EMAIL PROTECTED] wrote:
There is a problem with Xinerama Edgeresistance and different
screen sizes on the screens:
Layout:
screen 1 screen 2
+--++
| |+--+|
| || ||
| ||window
, but perhaps I wnat one on
both screens.
What I meant is that introducing Xinerama support into fvwm2 binary, but
leaving modules still use XParseGeometry() is inconsistent -- the pieces of
code responsible for window's placement should be modified too (sorry for my
not-so-perfect english ;-). Otherwise
XiSupp.c (think
about XMMS and various toolkits) or a similar thing, and they have no
standard means of communicating to FVWM.
Ah, okay. The solution to both problems is the module interface.
Some settings like Colorset are communicated to the modules over
the module pipe. The state of Xinerama
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/07/28 10:53:33
Modified files:
. : ChangeLog
fvwm : move_resize.c
libs : XineramaSupport.c
Log message:
* Fix for snapping at Xinerama screen edges
There is a problem with Xinerama Edgeresistance and different
screen sizes on the screens:
Layout:
screen 1 screen 2
+--++
| |+--+|
| || ||
| ||window
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/07/28 18:59:10
Modified files:
. : ChangeLog todo-xinerama
fvwm : modconf.c module_interface.c
libs : XineramaSupport.c XineramaSupport.h defaults.h
are communicated to the modules over
the module pipe. The state of Xinerama{En,Dis}abled can be easily
communicated too. In fact I have already done this. Take a look
at the code in virtual.c:
void CMD_XineramaDisable(F_CMD_ARGS)
{
XineramaSupportDisable
, and they have no
standard means of communicating to FVWM.
Ah, okay. The solution to both problems is the module interface.
Some settings like Colorset are communicated to the modules over
the module pipe. The state of Xinerama{En,Dis}abled can be easily
communicated too. In fact I have already
that I'll have
the time.
Dominik, I have a question/correction regarding your changes to XiSupp.c.
The XiSuppDisable() was intended as a mechanism to hard-disable Xinerama,
while XiSuppSetState() -- to turn it on/off on the fly. As I understood,
you changed XiSuppSetState() to be internal
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/07/27 04:55:15
Modified files:
. : ChangeLog
libs : XineramaSupport.c XineramaSupport.h
Log message:
* Applied next Xinerama patch with some modifications, commented
On 27 Jul 01 at 11:56, fvwm-workers@fvwm.org wrote:
- Code is written with 80 characters per line, a basic
indentation width of 2.
- Always compile the code with and without your ifdefs. Remove
all warnings (compile with 'make CFLAGS=-Wall -Werror -g).
Okay. I usually set
() (the first of them
appeared in XiSupp after february version).
Dominik, I have a question/correction regarding your changes to XiSupp.c.
The XiSuppDisable() was intended as a mechanism to hard-disable Xinerama,
while XiSuppSetState() -- to turn it on/off on the fly. As I understood,
you changed
Based on the man page, Solaris 8's Xserver supports Xinerama.
There is no libXinerama so the configure test fails.
There is also no header in X11/extensions.
I don't know if there is some other way to detect Xinerama.
I didn't see anything obvious in libs/XineramaSupport.c.
Perhaps the man page
On 25 Jul 01 at 10:06, [EMAIL PROTECTED] wrote:
Based on the man page, Solaris 8's Xserver supports Xinerama.
There is no libXinerama so the configure test fails.
There is also no header in X11/extensions.
Can you compile fvwm w/Xinerama under XFree86 and run it with -display
to Solaris
Dmitry Yu. Bolkhovityanov [EMAIL PROTECTED] writes:
On 25 Jul 01 at 10:06, [EMAIL PROTECTED] wrote:
Based on the man page, Solaris 8's Xserver supports Xinerama.
There is no libXinerama so the configure test fails.
There is also no header in X11/extensions.
Can you compile fvwm w
On 25 Jul 01 at 21:24, [EMAIL PROTECTED] wrote:
I don't know if there is some other way to detect Xinerama.
I didn't see anything obvious in libs/XineramaSupport.c.
No, AFAIK, what is currently used is the only way (well, how can we
support Xinerama w/o libXinerama)?
BTW
On 25 Jul 01 at 11:04, [EMAIL PROTECTED] wrote:
[SNIP]
Odd that it doesn't list Xinerama.
The Xsun man page says I should do xinit +xinerama to get Xinerama
support. Perhaps the extension only shows when you do that.
Right. An interesting fact is that Xnest also supports Xinerama
On Wed, Jul 25, 2001 at 11:04:43AM -0400, Dan Espen wrote:
Sun had a habit of shipping various libraries and utilities in separate
optional packages, so... Anyway,
find / | egrep -i 'xinerama|panoramix'
A find like that would run for months on our file systems,
For installed
On 23 Jul 01 at 18:55, fvwm-workers@fvwm.org wrote:
On Mon, Jul 23, 2001 at 06:34:52PM +0700, Dmitry Yu. Bolkhovityanov wrote:
Content-Description: Mail message body
Hi!
Attached is a new version of Xinerama patch. The .tgz contains a diff
file (against 05-Jul-2001 snapshot
of Xinerama patch. The .tgz contains a diff
file (against 05-Jul-2001 snapshot), two new files in libs/, and a
description of what was done.
Could you by any chance update this patch for the current CVS
version? The risk that I do something wrong if I merge the patch
with the current
syntax in
general. There are several places where Xinerama specific
parameters would be useful (Move, Resize, ResizeMove, Maximize,
MoveToPage and others).
As to Maximize, the syntax can be extended with a single optional switch:
Maximize [absolute] ...
By default maximization occurs
On 22 Jul 01 at 13:37, [EMAIL PROTECTED] wrote:
What is RandR?
RandR is a Resize and Rotate extension -- an ability to change screen
dimensions of a live X server. It is available in the CVS version of
XFree86, and is currently limited to KDrive (aka TinyX). But it is being
ported to
Hi!
Attached is a new version of Xinerama patch. The .tgz contains a diff
file (against 05-Jul-2001 snapshot), two new files in libs/, and a
description of what was done.
This patch has a very basic RandR support, which is disabled by default.
Also new from previous version
On Mon, Jul 23, 2001 at 06:34:52PM +0700, Dmitry Yu. Bolkhovityanov wrote:
Content-Description: Mail message body
Hi!
Attached is a new version of Xinerama patch. The .tgz contains a diff
file (against 05-Jul-2001 snapshot), two new files in libs/, and a
description of what was done
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: olicha 01/07/23 15:23:02
Modified files:
libs : XineramaSupport.c
. : ChangeLog
Log message:
* Draw the xinerama simulation screens with some orr windows
--
Visit the official FVWM web
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/07/23 17:38:29
Modified files:
. : ChangeLog todo-xinerama
fvwm : menus.c menus.h windowlist.c
libs : XineramaSupport.c
Log message:
* Make the blank
virtual.c
libs : XineramaSupport.c
modules: ChangeLog
modules/FvwmEvent: FvwmEvent.c
modules/FvwmForm: Makefile.am
modules/FvwmScript: Instructions.c
modules/FvwmWharf: FvwmWharf.c
Log message:
* Added Xinerama emulation
CVSROOT:/home/cvs/fvwm
Module name:fvwm-web
Changes by: domivogt01/07/22 07:27:19
Modified files:
. : ChangeLog mod_f2m_communication.html
Log message:
* Minimalistic description of Xinerama support.
--
Visit the official FVWM web page at URL:http
Here is a list of features Xinerama support may or may not
support:
1) Window placement
2) Icon placement
3) Menu placement
4) Menu position hints
5) Sizing menus for different screen sizes
6) Position of the geometry window
7) Maximizing windows
8) Limit SnapAttraction to windows
Hi!
I've almost made a very improved version (as compared to February), but
still have to spend a few days finishing it. It is now based on 2.4 instead
of 2.3.28.
As I understood from conversation in the list, there were plans to do
2.4.1 as a bugfix-only release, so I didn't hurry
On 22 Jul 01 at 1:48, [EMAIL PROTECTED] wrote:
On 21 Jul 2001 14:29:27 -0500, FVWM CVS wrote:
Log message:
* First version of Xinerama support.
I don't think that HAS_XINERAMA is ever defined (because XINERAMA_CPPFLAGS
is nowhere used) and thus parts of the xinerama code are ever
(HAVE_XINERAMA is put into config.h), general code
structure (changed library user interface a bit), xinerama
emulation (for people with one monitor).
As you may have noticed I already started another thread to
discuss the details of the Xinerama implementation. Before we
continue patching we should think
xinerama code be ever compiled in;
_ fixed linking of libfvwm.a by adding -lXinerama; small corrections
* fvwm-config: added shape support and resorting
--
Visit the official FVWM web page at URL:http://www.fvwm.org/.
To unsubscribe from the list, send unsubscribe fvwm-workers in the
body
On 22 Jul 2001 16:49:43 +, Mikhael Goikhman wrote:
Yes, Xinerama support is on after configure; make install.
The same problem happens with configure --disable-xinerama.
BTW, I can't reproduce the problem with WindowShade now.
Only interactive Move is problematic.
Regards,
Mikhael
On Sun, Jul 22, 2001 at 06:18:57PM +, Mikhael Goikhman wrote:
On 22 Jul 2001 16:49:43 +, Mikhael Goikhman wrote:
Yes, Xinerama support is on after configure; make install.
The same problem happens with configure --disable-xinerama.
BTW, I can't reproduce the problem
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/07/22 18:38:20
Modified files:
. : ChangeLog NEWS todo-xinerama
fvwm : fvwm2.1 menus.c menus.h move_resize.c virtual.c
windowlist.c
On Sun, Jul 22, 2001 at 09:32:38PM +0700, Dmitry Yu. Bolkhovityanov wrote:
On 22 Jul 01 at 12:57, [EMAIL PROTECTED] wrote:
Here is a list of features Xinerama support may or may not
support:
1) Window placement
2) Icon placement
3) Menu placement
4) Menu position hints
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/07/22 19:56:03
Modified files:
. : ChangeLog
fvwm : menus.c windowlist.c
Log message:
* Several menu placement/Xinerama fixes.
--
Visit the official FVWM web page
move_resize.c
move_resize.h screen.h virtual.c virtual.h
libs : Makefile.am defaults.h
modules/FvwmForm: FvwmForm.c Makefile.am
tests/menus: menus.read
Log message:
* First version of Xinerama support.
* Reformatted man page suorce
On 21 Jul 2001 14:29:27 -0500, FVWM CVS wrote:
Log message:
* First version of Xinerama support.
I don't think that HAS_XINERAMA is ever defined (because XINERAMA_CPPFLAGS
is nowhere used) and thus parts of the xinerama code are ever compiled in,
although it is reported as such.
It is also
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/07/01 10:57:22
Modified files:
. : ChangeLog NEWS configure.in
Log message:
* Set development version to 2.4.0.1 (for xinerama support in 2.4.1).
--
Visit the official FVWM web page
101 - 145 of 145 matches
Mail list logo
