I'm getting behavior which is not desired at all. I have split 1.1 and 1.2 and I have many apps which when used I always need maximized to 1.0 (full screen, ignore splits). With DF not running I get this native Windows functionality as expected. With DF running it seems to select one or the other split and never allows for full screen (1.0). If I create a Trigger, Event > Window Created > Run Function: "Maximize Windows (ignore monitor spits)" it DF always crams the app into one of the splits and then moves it to the full monitor.

1. Frankly, this is a concern on 100% of the displaying of any Window/Dialog. I always want to move, resize, maximize, etc. BEFORE the Window is Created. I don't want the flashing and moving of windows after the fact.

HOW CAN THIS BE ACHIEVED?

2. How can an Window/App (or see #3 below) be allowed to use use its Windows Native screen location and sizing AND 'ignore monitor splits' (default behavior)?

3. How to apply a script to provide a list (1..N) of apps which I want the "ignore monitor splits"?

4. There's a problem when you using the 'ignore monitor splits' in this example.
(a) Initially displayed maximized within the split (not desired)
(b) A second or two maximized to full screen (desired, except delay, and app movement)
(c) Click on restore and you get the app back into the split (I'd expect the split didn't apply to the app until and unless the app was explicity moved into the split and DF behavior would be everything except as if the splits didn't exist.

Thanks

Have you attempted to keep the "new window" hidden/invisible until the location and sizing has been performed, and then change to your location/size and display?

Different WindowClasses need to be handled in different ways, at least that was my experience when I was doing these things.

Sounds like someone was retaining a local variable for location/size and not using the window's properties. Have you considered the ability to use this method and then provide either by you or the end-user a method to black-list (or white-list) troubled apps/windows? Would rather see it working on some rather than none.