PDA

View Full Version : [CLOSED] Position of triggers added to DropDown



RCN
Nov 28, 2014, 6:01 PM
On version 2.x, the triggers added to DropDown were placed before "open" trigger

http://forums.ext.net/attachment.php?attachmentid=16701&stc=1

but on version 3.x, the triggers added to DropDown were placed after "open" trigger

http://forums.ext.net/attachment.php?attachmentid=16711&stc=1

Any ideas to overcome this issue?



<!DOCTYPE html>
<html>
<head id="Head1" runat="server">
</head>
<body>
<ext:ResourceManager runat="server" SeparateUIStyles="false" Theme="Gray" />
<ext:DropDownField
ID="_ddd"
Editable="false"
Width="800"
runat="server" TriggerIndexOnEnter="1" >
<Triggers>
<ext:FieldTrigger Icon="Clear" />
</Triggers>
<Component>
<ext:Panel Title="Inner Panel" runat="server" Height="600">
<Loader Url="http://www.ext.net" Mode="Frame" runat="server" />
</ext:Panel>
</Component>
</ext:DropDownField>
</body>
</html>

RCN
Nov 28, 2014, 6:11 PM
It's possible to overcome the issue presented above by setting FieldTrigger's Weight property to -1.

Description of FieldTrigger's Weight property: An optional weighting to change the ordering of the items. The default weightis 0. Triggers are sorted by weight in ascending order before being



<ext:FieldTrigger Icon="Clear" Weight="-1" />




<!DOCTYPE html>
<html>
<head id="Head1" runat="server">
</head>
<body>
<ext:ResourceManager runat="server" SeparateUIStyles="false" Theme="Gray" />

<ext:DropDownField Margin="10"
ID="_ddd"
Editable="false"
Width="800"
runat="server">
<Triggers>
<ext:FieldTrigger Icon="Clear" Weight="-1" />
</Triggers>
<Component>
<ext:Panel Title="Inner Panel" runat="server" Height="600">
<Loader Url="http://www.ext.net" Mode="Frame" runat="server" />
</ext:Panel>
</Component>
</ext:DropDownField>
</body>
</html>

RCN
Nov 28, 2014, 6:14 PM
I think that it would be interesting to add this information to Breaking Changes document.

Daniil
Nov 30, 2014, 10:07 AM
Hi Raphael,

Thank you for pointing out the problem. Rather than adding it into the breaking changes document we considered it as a defect and fixed in the revision #6187 (v3 branch).

By the way, regarding the SeparateUIStyles="false" setting. This setting has been removed. I am adding this breaking change item:


34. [EXTNET] The ResourceManager's SeparateUIStyles setting has been removed.
If you previously used SeparateUIStyles="false", it is now the behavior by default, i.e.
all the UI styles are loaded at once if any UI is used.
We don't consider SeparateUIStyles="true" (default in Ext.NET v2) is required anymore.
If you disagree, please feel free to initiate a discussion on the forums.

RCN
Nov 30, 2014, 5:03 PM
Thank you Daniil. Please mark this thread as closed.