Patchou,

How come now the Plus! Script Windows, and Plus! windows in general have an invisible titlebar and border? This has caused problems with Screenshot Sender and the select area function.

What made you decide to add this in?

I'm not sure but I think that hiding the borders using a window region instead of painting over them like before makes it easier to show them again when the window is maximized.

quote:

---

Originally posted by deAd
I'm not sure but I think that hiding the borders using a window region instead of painting over them like before makes it easier to show them again when the window is maximized.

---

It is internal to Plus! and it solves a couple of problems.

Let me know how it causes a problem for you and I'll try to make some suggestions .

The hidden title bar and borders causes extra space to show up. I cannot move the window up the screen because it is forced down as a default window behavior to make sure there is a portion of the titlebar still showing.



Using this code

code:

---

Interop.Call('user32', 'SetWindowLongW', objWindows['SelectArea'].Handle, (-16) /* GWL_STYLE */, Interop.Call('user32', 'GetWindowLongW', objWindows['SelectArea'].Handle, (-16) /* GWL_STYLE */) & ~ 0xC00000 /* WS_CAPTION */ & ~ 0x400000 /* WS_BOARDER */);

---

code:

---

<?xml version="1.0" encoding="UTF-16"?>
<Interfaces xmlns="urn:msgplus:interface" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsichemaLocation="urn:msgplus:interface PlusInterface.xsd">
    <Window Id="SelectArea" Version="1">
        <Attributes>
            <ShowInTaskbar>False</ShowInTaskbar>
            <TopMost>True</TopMost>
            <NoActivate>True</NoActivate>
            <LockOnClick>False</LockOnClick>
        </Attributes>
        <Titlebar>
            <AllowMinimize>False</AllowMinimize>
            <AllowMaximize>False</AllowMaximize>
            <AllowClose>False</AllowClose>
        </Titlebar>
        <WindowTmpl>
            <Corners Shape="Rectangle">
                <RoundSize>0</RoundSize>
            </Corners>
        </WindowTmpl>
        <Position Width="400" Height="300" />
    </Window>
</Interfaces>

---

I see... well, in order to do this kind of thing, you would probably be much better off creating the window yourself with a direct call to CreateWindowEx().

But if you really want to try continuing to use Plus! windows for this, try adding option 0x100 to your CreateWnd() call .

quote:

---

Originally posted by Patchou
I see... well, in order to do this kind of thing, you would probably be much better off creating the window yourself with a direct call to CreateWindowEx().

---

quote:

---

Originally posted by Patchou
But if you really want to try continuing to use Plus! windows for this, try adding option 0x100 to your CreateWnd() call

---

code:

---

    <WindowTmpl>
        <Corners Shape="Rectangle">
            <RoundSize>0</RoundSize>
        </Corners>
    </WindowTmpl>

---

quote:

---

Originally posted by matty
With setting that style you would assume the windows corners would be square however as shown in the graphic this is not the case:

---

quote:

---

Originally posted by SpunkyLoveMuff

quote:

---

Originally posted by matty
With setting that style you would assume the windows corners would be square however as shown in the graphic this is not the case:

---

Doesn't the number have to be odd? I know 0 is neither odd or even, but it accepts numbers like 1,3,5 etc so 0 might get rounded up...

---

Hmm... the scripting documentation says:

quote:

---

element Window/WindowTmpl/Corners/RoundSize
Only valid if shape is Round. Must be an odd value.

---

code:

---

    <WindowTmpl>
        <Corners Shape="Rectangle"/>
    </WindowTmpl>

---

The options parameter is a bit field so if you were using 0x0001 before, just set the option to 0x101 (0x1 + 0x100) and you will get what you want. This option is not documented because scripts are not supposed to use it, but well...

quote:

---

Originally posted by Patchou
The options parameter is a bit field so if you were using 0x0001 before, just set the option to 0x101 (0x1 + 0x100) and you will get what you want. This option is not documented because scripts are not supposed to use it, but well...

---

bump....

Matty, I'll check this, don't worry. If it's a bug, it will be fixed

More side effects from using 0x100 when creating the window. When the window is maximized the custom plus! system tools (minimize, maximize/restore, close) are removed. You can subclass the window and detect when it is being Maximized and you can use the ShowWindow api to show them but this should be fixed on Plus! side

quote:

---

Originally posted by matty
More side effects from using 0x100 when creating the window. When the window is maximized the custom plus! system tools (minimize, maximize/restore, close) are removed. You can subclass the window and detect when it is being Maximized and you can use the ShowWindow api to show them but this should be fixed on Plus! side

---

code:

---

function OnWindowIdEvent_MessageNotification(pPlusWnd, nMessage, wParam, lParam) {
    switch (nMessage){
        case 0x5 /* WM_SIZE */:
            if (wParam === 2 /* SIZE_MAXIMIZED */) {
                Interop.Call('user32', 'ShowWindow', pPlusWnd.GetControlHandle('BaseBtnMinimise'), 5 /* SW_SHOW */);
                Interop.Call('user32', 'ShowWindow', pPlusWnd.GetControlHandle('BaseBtnMaximise'), 5 /* SW_SHOW */);
                Interop.Call('user32', 'ShowWindow', pPlusWnd.GetControlHandle('BaseBtnCancel'), 5 /* SW_SHOW */);
            }
        break;
    }
}

---