I have a working dual screen setup using twinview on a nvidia card, with the left monitor at a resolution of 1680x1050 and the right with a resolution of 1280x1024.

I'm trying to run 2 instances of the same application in Wine, each having a whole screen of it's own. I'm using the window specific rules where I use the tool to select the window I want on each screen, and specify size, position and border so that each fills the entire screen (I select by window class and window title).

If I close down the applications after the initial configurationa and restart them, none of the rules are applied. I have to open the settings dialogue, select a rule, close it again without doing anything and press "apply" in the settings module to enforce some of the rules. This fixes size and position, but the window border still remains. Is there a way to work around this and make it apply all the rules without having to go back into the settings dialogue each time?

(Each Wine instance is started as "wine explorer /desktop=window1,1680x1050 application" and "wine explorer /desktop=window2,1280x1050 application", so they have different names. Each application resides in a wine directory of its own.)

For the Window specific rules, which of the "Force" options have you selected? "Force Initially" may not work if the application shows, hides then reshows the window.

I'm using plain force rules on all the custom settings, as can be seen in the screenshots of each tab.

Tab 1
Tab 2
Tab 3
Tab 4
Tab 5

I've also discovered that the rules seem to be applied in bunches. Ie, I open the programs and they both start on the same screen. Then I enter the rules dialogue, open any custom window rule, press ok to get back to the rules dialogue so the apply button is unlocked, click this and some of the rules are applied. If I do it one more time, the remaining rules are applied.

It might have something to do with the window title. If I remove the requirement of an exact match in the window title, all the rules are applied when the application is opened. In this case, I can't distinguish between the windows, so they are both set to fill one of the two monitors. It might be that wine initially have a different title, and thus no rules are applied as the window doesn't match any rules. Only when I ask it to reapply the rules after the windows have aquired their final titles. I don't get why I have to apply the rules 2 times though.

Anyone know a way to monitor the title of a window, to check the initial title? Or know how kwin behaves in this matter (Does it monitor the window title continously or just when a new window is opened)?

I do not know how it monitors the window titles, if it does not dynamically detect the change however, I would consider it to be a bug.

KWin only applies rules when the window is created--if any window information changes afterwards the rules are NOT applied.

Bug 92914 refers to the window title only but as Marco found out a few days ago (When trying to add some Netbook-specific rules) it applies to all window info.

Is there a way to check if the window title is changed after startup? It is most likely the case, since the rules are matched when I remove it, but it would be nice to actually see this.

Also, even if the rules aren't applied initially, why do I have to manually apply the rules two times after the windows are created?

I opened Bug 207670 some days ago. It might be invalidated now, but part 2 still puzzles me.

The KWin window rules system is quite ancient and no active developer fully understands it and are all preoccupied with other tasks. Unfortunately this means that if you require this bug to be fixed you will need to provide your own manpower. =(

I've pondered about contributing back to the KDE project for some time. I usually dismiss the thought when I try to figure out how to set up a dual environment, so I can have a stable KDE alongside.

You may wish to look at kdesvn-build which makes the process of building Trunk KDE quite easy.
If you wish, I can provide a copy of the script I use to configure environment variables before login, which ensures that Trunk KDE is used.