Sorry; I should have sent an update on this.

The version in the nightly builds works properly. The test file is misleading: it doesn't look like a combobox so Max and I thought it was broken.

We will be including the newcombobox fix in a 3.1.1 update, due to be available this week. However, the change is in the nightly builds if you would like to grab it now.

jim

On Dec 19, 2005, at 10:33 AM, William Krick wrote:

Any updates on the status of newcombobox?

I don't want to download and install a potentially broken nightly build to
find out that it still doesn't work.

thanks



-----Original Message-----
From: Jim Grandy [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 29, 2005 11:47 AM
To: William Krick
Cc: Adam Wolff; [email protected]
Subject: Re: [Laszlo-user] is there any way to make this code faster?


William,

Max checked a fix in over the Thanksgiving break that will get
newcombobox compiling -- this is in the nightly build. Unfortunately,
even though it builds now it doesn't run properly. I'm going to take
a look at what might be wrong later this week.

jim

On Nov 23, 2005, at 8:11 AM, William Krick wrote:


I'm trying to get newcombobox-test.lzx example working and some of the
resources for the incubator version of floatinglist are missing
from the
installation...

    <resource name="shadow_right" src="resources/floatinglist/
v_shdw.swf" />
    <resource name="shadow_bottom" src="resources/floatinglist/
h_shdw.swf"
/>
    <resource name="shadow_corner"
src="resources/floatinglist/corner_shdw.png" />



-----Original Message-----
From: Adam Wolff [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 10:26 AM
To: William Krick
Cc: [email protected]
Subject: Re: [Laszlo-user] is there any way to make this code faster?


Check out lps/components/incubator/newcombobox

This is much more efficient for the kind of situation you describe.
It's a
data-backed combobox.

A

On Nov 22, William Krick wrote:

In our app, we have to be able to replace the list of items in
various
comboboxes often.  So we extended combobox and added a setItems()
method.
However, the part that removes the old
items is brutally slow.  In fact, it seems to be faster for us to
destroy
the combobox and create a new one than it is to remove the items.
However
destroying comboboxes at runtime just feels wrong and I'm sure
will lead
to
memory leaks and other problems.  Below is our code.  Any thoughts
would
be
appreciated...

<class name="comboboxex" extends="combobox">
  <method name="setItems" args="list">
    <![CDATA[
      //First, remove items...
      while(this.getItemAt(0) != null) {
        this.removeItemAt(0);
      }
      //Then, add items passed in
      for (var i=0; i<list.length; i++) {
        this.addItem(list[i], i);
      }
    ]]>
  </method>
</class>

_______________________________________________
Laszlo-user mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-user




_______________________________________________
Laszlo-user mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-user



--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.13.10/188 - Release Date: 11/29/2005


Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Laszlo-user mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-user

Reply via email to