Hi all,
I've been having a similar problem to #1 and #2 for a while now, so I
was very relieved to see that build 5133 is able to handle these bugs.
I just started up 5133, ran my app, and although the old warnings went
away, a new one has come in, and the app still doesn't work properly.
The following is the code that I am using (which works without any
problems in 3.3.3):
<tabs id="selectGameTabs" datapath="myGroups_ds:/allGroups"
width="430" height="270">
<CustomTabpane name="$path{'@groupName'}" datapath="myGroup"
text="$path{'@title'}" />
</tabs>
These tabpanes are drawing from xml that looks something like:
<allGroups>
<myGroup title="Test Group Cheeseburger" groupName="testA" />
<myGroup title="Test Group French Fries" groupName="testB" />
</allGroups>
The debugger prints out a warning message:
WARNING: base/basetabs.lzx:317: reference to undefined property
'datacontrolsvisibility'
Then the CustomTabpanes, although they all are created and have the
proper datapath (they appear as they should and I can
Debug.write(this.datapath.p) on them), the subviews randomly don't
appear. Textfields and views occasionally show up on some
CustomTabpanes, but not on others.
Any ideas?
Thanks,
Colin
On 5/23/07, mario ruggier <[EMAIL PROTECTED]> wrote:
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
