Julian

@vattila Hi and thanks again for the welcome! I'm sorry about posting anonymous. I didn't realize that I was logged out. ^^' I found a way to solve the issue, "probably" by changing the linking order. The Lua-library was included by adding the lib-file to the c++-Builder project. It is unclear to me how the order of lib-files in the project compare to files requested in the code. I also didn't find a way to change the linking order of static libraries with IDE settings. However, by removing the lib-file...

I found yet another approach that seems to work best so far. a custom class derived from owl::TGadgetWindow its constructor uses direction=TGadgetWindow::TTileDirection::Rectangular content of its constructor sets the initial dimension using SetRectangularDimensions(width, NULL); (height-parameter is ignored) It overrides nothing else in the window-EvSize dialog I void TMDIwindow::EvSize(owl::uint sizeType, const owl::TSize& size){ owl::TRect rec; MDIwindow->GetClientRect(rec); //fetch window width...

I found yet another approach that seems to work best so far. a custom class derived from owl::TGadgetWindow its constructor uses direction=TGadgetWindow::TTileDirection::Rectangular content of its constructor sets the initial dimension using * SetRectangularDimensions(width, NULL); (height-parameter is ignored) It overrides nothing else in the window-EvSize dialog I void TMDIwindow::EvSize(owl::uint sizeType, const owl::TSize& size){ owl::TRect rec; MDIwindow->GetClientRect(rec); //fetch window width...

I found yet another approach that seems to work best so far. a custom class derived from owl::TGadgetWindow its constructor uses direction=TGadgetWindow::TTileDirection::Rectangular content of its constructor sets the initial dimension using ` SetRectangularDimensions(width, NULL);` (height-parameter is ignored) It overrides nothing else in the window-EvSize dialog I void TMDIwindow::EvSize(owl::uint sizeType, const owl::TSize& size){ owl::TRect rec; MDIwindow->GetClientRect(rec); //fetch window...

I had some time again to write a work-around. In the dialog EvSize function the dialog with is compared to the width of the gadget buttons. If the dialog width gets to small, the buttons are removed and added to a second TControlBar. owl::TButtonTextGadget* G_ButTurnText; bool twoRowToolbar=false; void TMAcMDI::EvSize(owl::uint sizeType, const owl::TSize& size){ //owl::TMDIClient if(size.cx<590 && !twoRowToolbar){ controlBar1->Remove(*G_ButTurnText); //owl::TControlBar in a owl::TDecoratedMDIFrame...

Is it possible to make TGadgetbuttons in a TControlbar wrap if the window is too small? I could probably set the TGadgetWindow has a direction mode Rectangular where one could adjust the rows and columns in the window EvSize event. But TControlbar states it's eitehr vertical or horizontal.

Yes, now that I think about it, TileChildren of course removes the WS_CAPTION from the minimized windows and they fall back to the old design. However, I think there is a misunderstanding. If I remove the WS_CAPTION before minimizing by calling ShowWindow(SW_SHOWMINIMIZED); then the control buttons do not appear and the application froze when I clicked there.

I'm not sure what you refer to. When MDIChildren are minimized, they become small windows on the bottom-left. If you add the caption before, they have just enough space for the three buttons. calling TileChildren on minimized windows interestingly switches the windowsstyle, but both styles work.