Bug#342793: ion3-scripts: Twinview new windows always open on main screen
Package: ion3-scripts Version: 20051205-1 Severity: normal In a twinview (two screen) setup, regardless of where the focus or mouse is, new windows always open on the main screen. The expected (and previous) behavior is that new windows open on the screen with the focus. This problem disappears if I revert to 20051011-1, which indicates that it is some change between these two versions that causes the problem. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-1-amd64-k8-smp Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages ion3-scripts depends on: ii ion3 20051029-3 keyboard-friendly window manager w ion3-scripts recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342793: ion3-scripts: Twinview new windows always open on main screen
On 10.12.05, Liam M. Healy wrote: > This problem disappears if I revert to 20051011-1, which indicates > that it is some change between these two versions that causes the > problem. Hello Liam, which of the scripts in the ion3-scripts package are you actually using in your ion3 configuration? This information would help a lot in tracking down the issue. Regards, René signature.asc Description: Digital signature
Bug#342793: ion3-scripts: Twinview new windows always open on main screen
On 10.12.05, Liam M. Healy wrote:
Hi Liam,
> That makes sense. How do I determine which scripts I'm actually
> using?
If you do not know what scripts you are using, the fact is likely that
you are using none at all. You must have taken manual action to use
scripts from the ion3-package, i.e. having included lines like
"dopath('scriptname')" in your ion3 configuration somewhere.
Per default, none of the scripts in ion3-scripts package are
loaded.
If you feel unable to find out which scripts you load, you can -- if
you don't mind -- send me your ion3 configuration and I'll try to
figure it out. If I know your scripts, I can investigate the changes
in those between the two package versions and see what could be
related to a multiheaded configuration.
Since I do not use multiheading, I'd be unable to reproduce the
problem otherwise.
Thanks and Regards,
René
signature.asc
Description: Digital signature
Bug#342793: ion3-scripts: Twinview new windows always open on main screen
René,
detach.lua appears to be the only script from this package that I am
using. All the rest begin with mod_ or dfg_, neither of which occurs
in the package.
Liam
> "René" == Ren writes:
René> On 10.12.05, Liam M. Healy wrote:
René> Hi Liam,
>> That makes sense. How do I determine which scripts I'm actually
>> using?
René> If you do not know what scripts you are using, the fact is likely that
René> you are using none at all. You must have taken manual action to use
René> scripts from the ion3-package, i.e. having included lines like
René> "dopath('scriptname')" in your ion3 configuration somewhere.
René> Per default, none of the scripts in ion3-scripts package are
René> loaded.
René> If you feel unable to find out which scripts you load, you can -- if
René> you don't mind -- send me your ion3 configuration and I'll try to
René> figure it out. If I know your scripts, I can investigate the changes
René> in those between the two package versions and see what could be
René> related to a multiheaded configuration.
René> Since I do not use multiheading, I'd be unable to reproduce the
René> problem otherwise.
René> Thanks and Regards,
René> René
Bug#342793: ion3-scripts: Twinview new windows always open on main screen
On 10.12.05, Liam M. Healy wrote: Hello Liam, > detach.lua appears to be the only script from this package that I am > using. All the rest begin with mod_ or dfg_, neither of which occurs > in the package. Thank's a lot, I *think* the problem is the following new function in detach.lua: function detach.clientwin_manager(cwin, table). It is called to manage to-be-opened client windows and contains the following passage: local screen = cwin:screen_of() if screen == nil then screen = ioncore.find_screen_id(0) end It seems as the screen of not-yet-placed but to-be-placed windows is not known at that time and therefore screen 0 is used as a fallback. I am unfortunately unable to verify that conclusion right now, not being at home and only having access to a windows machine. But expect it to be fixed by the next weekend. :-) René signature.asc Description: Digital signature
