Shoutbox

quote:

---

Originally posted by whiz
I've done all that, and the parent/child windows are loaded, but as soon as I resize the window, the child disappears.  It leaves just an empty parent window...

---

That's odd... Can you pack your script and upload it so we can have a better look at it?

Attached.

I do not exactly have time ATM, but still: you must place the PlaceHolderElement in the parent window, not the child window like you did

quote:

---

Originally posted by SmokingCookie
I do not exactly have time ATM, but still: you must place the PlaceHolderElement in the parent window, not the child window like you did

---

Umm...

xml code:

---

<Window Id="WndCommandBar_Shell" Version="1">

    <Attributes>
        <Caption>Command Bar</Caption>
        <TopMost>true</TopMost>
        <ShowInTaskbar>false</ShowInTaskbar>
    </Attributes>
   
    <TitleBar>
        <AllowMinimize>false</AllowMinimize>
        <AllowClose>false</AllowClose>
    </TitleBar>
   
    <Position Width="186" Height="27">
        <IsAbsolute>true</IsAbsolute>
        <Resizeable Allowed="BothSides">
            <MinWidth>150</MinWidth>
            <MinHeight>27</MinHeight>
        </Resizeable>
    </Position>
   
    <WindowTmpl>
        <Borders Type="Simple"/>
    </WindowTmpl>
   
    <Elements>
        <Element xsi:type="PlaceHolderElement" Id="PhlChild">
            <Position Left="10" Top="0" Width="172" Height="26"/>
        </Element>
    </Elements>

</Window>

---

...I have, haven't I (the parent is actually second in the interface file - the first is the old one, to be ignored)?

EDIT: were you looking at the code in the first post? 

Fixed it!

• OnWndCommandBar_ShellEvent_MessageNotification always has to return something. Because we want all messages to be processed normally, we always return -1.
  
• You defined the element in your XML as "PhlChild" but you're referencing it as "PlhChild"! This is why RetrievePos always gives 0 for position and size.
  
• The place-holder needs to size with the window, so it needs anchoring.
  
• The place-holder should be the same size as the child window it holds in order to make the child size properly.

Attached is the script package with these fixes included. You still need to resize the other child window as well. Here's a tip: only resize the currently displayed child window, so store the current child in some global variable, size that one when receiving WM_SIZE and swap it when the child changes (don't forget to resize the new child after swapping!).

Like I said, I didn't have the time this morning. I had a few hours off at school, so I rush-finished some homework (still too late for school though ).

Anyway, seems like I was confused by the window IDs. I'm used to a system like this:

JScript code:

---

//Some example code demonstrating Window IDs and child IDs

var PlusWnd = MsgPlus.CreateWnd("Wnd.xml","WndTest");
var ChildWnd = MsgPlus.CreateChildWnd(PlusWnd,"Wnd.xml","WndTest_Child",0,0,true);

---

You might wanna try this yourself

And I think I've found the error:

XML code:

---

    <Elements>
        <Element xsi:type="PlaceHolderElement" Id="PhlChild"> <!-- Check the element ID here -->
            <Position Left="10" Top="0" Width="172" Height="26"/>
        </Element>
    </Elements>

---

JScript code:

---

function OnWndCommandBar_ShellEvent_MessageNotification(PlusWnd, Message, wParam, lParam)
{
    if (Message == 0x5)
    {
        var posChild = RetrievePos(WndCommandBar_Shell,"PlhChild"); // Check the element ID here too
        Interop.Call("user32","MoveWindow",WndCommandBar_CMain.Handle,posChild.x,posChild.y,posChild.Width,posChild.Height,true); // Thought this would solve it...
    }
}

---

That's one common error I've experienced MANY times.. ^0)

* Even more angry at Matti....
AGAIN!!

Great, it works!    Except that I installed the script and didn't think to copy all of the changes I had made with the actual workings of the script...  that I've now lost...    Ah, well.

EDIT: I've managed to recover most of my changes from my online backup, which (luckily) hadn't synchronized that bit yet...