On 5/21/07, Benjamin Shine <[EMAIL PROTECTED]> wrote:
These fixes are in the most recent nightly build, 5133, available at http://download.openlaszlo.org/nightly/legals/5133 To get just the modified files, unpack http://svn.openlaszlo.org/ openlaszlo/patches/20070518-ben-m.tar then unpack files.tar in there -- but I'd recommend getting the complete nightly, because lots of things are getting fixed fast.
Thanks! They do indeed fix #1 and #2...
>> I don't understand what you mean by #3 or #4. Can you take a >> screengrab that shows the problems? > > See below... I understand. I think my fixes from the other tabpane bugs fixed this, too. Try build 5133 and you should be all set.
#3 also seems to be corrected by build 5133. #4 is not though. To maybe pinpoint you better on the issue, try the following: a) in an **unmaximized** browser window, reload the unmodified test program I sent earlier (dynamic_tabpanes.lzx). b) Create a second tab by clicking on teh newWorkTab button. c) debug-eval the 2 expressions: worktabs.width // width of tabs component worktabs.subviews[1].width // width of tabscontent subview If you snoop further down, the "tabscontent" subview contains a "borderedcontent" subview, where all tabpanes seem to appear as children... any idea why this additional intermediate view? Anyhow, note the 2 width values given by the above... d) Maximize the browser window. e) Repeat (c). Notice that the worktabs.width is changed, but the tabscontent width does not change. e) Unmaximize the browser.window. f) Repeat (c). Both width values are now as they were reported in (c). I would like that the child tabpanes (whatever that means in terms of the nested views) follow the size of the parent tabs component, that fills up the available space as per the size of the browser window. Do you need to add an onwidth and/or onheight handler somewhere. or is this an issue with the bubbling up/down of these events? Thanks a lot, mario
