buttons hidden on button tab of dwtest

[abwillis]

This has been this way for probably the life of DW but when the buttons tab is first opened, at least here, the bottom button covers the second to the bottom button. I don't know if much can be done about it but if I hadn't resized the window at some point I would not have even known about the one button. Attaching screenshots, dwtest1 is when it is first opened and dwtest2 is after increasing the screensize of dwtest.

[abwillis]

dwtest1 -- initial open size

[abwillis]

dwtest2 -- window size increased

[bsmith]

Well I can increase the default size of the window. On most platforms the button is visible but on OS/2 the notebook control consumes a lot more space than similar controls on other platforms leaving less room for things packed into it. dwtest isn't however really meant to be an end user application or anything ;) ... it serves two purposes 1) To demonstrate some of the features of the library and 2) as a testing tool to make sure functionality works properly and in a similar manner across the different platforms.

[abwillis]

As dwtest is not an end user application increasing its size would probably not be of benefit. I was more thinking in terms of if the same thing happened in a real app which is why I wasn't sure if much could be done about it.

[bsmith]

I did commit a slight change to the layout and the size of the window so it should be visible now.

Regarding happening in an end user application... this can be avoided in several ways:

1) Making everything in the layout expand, thereby preventing clipping. 2) Using window autosizing which will make the window big enough to fit the contents. --- This wont't work for dwtest because autosizing doesn't work on notebook controls. (Since each page in the notebook could have different size requirements) 3) Using a scrollbox, if clipping is going to occur you can then scroll to see the item

Also there are times when you would want clipping to occur, like if you have an expandable side bar... you may want it to expand at times pushing other content off to the side...

So bottom line it isn't a bug and it isn't intended exactly. ;)