This seems like a worthwhile change to me. I would file an
improvement request in Jira.
I suspect just an oversight in the original design, and a belief that
once constraints are more efficient than always constraints. (They
might be, but it is more important to have correct behavior than
efficient implementation IMO.)
On 2008-05-16, at 06:55 EDT, Marco Lettere wrote:
Hello everybody,
I noticed that the basecombobox (I'm using lps-4.0.10) has a different
behavior depending whether it is in editable_state or not.
In non editable_state the width of the cbtext node is ALWAYS bound to
the width of the interior:
[snipped form basecombobox.lzx line 151]
<state name="non_editable_state" >
<text x="2" y="1" name="cbtext" width="${parent.width - 4}"
clickable="true" focusable="true">
<attribute name="text" type="string" />
Whereas in the editable state the cbtext node gets bound only ONCE to
the editbkgnd node width.
[snipped form basecombobox.lzx line 203]
<state name="editable_state" >
<view name="editbkgnd" bgcolor="white" width="100%" height="100%" />
<inputtext x="2" y="1" name="cbtext" width="$once{parent.width
- 4}">
This forces me to write extra code in my app when an editable combo
gets
resized because the inputtext remains always at the starting wdth.
If the $once constraint could be changed to default then everything
would be ok (I tried it).
Is there a reason for that issue or is it a small bug?
Thank you,
M.