[FIXED] [#779] [3.2.0] ComponentLoader issue

  1. #1

    [FIXED] [#779] [3.2.0] ComponentLoader issue

    Hello, when upgrading ext.net 2 to ext.net 3 I found following
    <script>
            
            <%=  ComponentLoader.ToConfig(new Window("xxx")) %>
        </script>
    produces

    [new Ext.window.Window({renderTo:Ext.getBody(),width:200,xtype:"window",title:"xxx"}).show();]

    which is not even valid javascript

    Is there any way how to translate AbstractComponentInstance to the json config?

    Note that the same problem appear if I try to do that using userControl

    Regards
    Zdenek
    Last edited by Daniil; Apr 10, 2015 at 2:07 PM. Reason: [FIXED] [#779] [3.2.0]
  2. #2
    Hi @Zdenek,

    Thank you for the report! Created an Issue:
    https://github.com/extnet/Ext.NET/issues/779

    Fixed in the revision 6414 (trunk). It goes to 3.2.0.

    You can update from SVN or use
    new Window("xxx") { LazyMode = LazyMode.Config }
    as a workaround.

Similar Threads

  1. [CLOSED] ComponentLoader and Ext.JSON.decode() issue
    By pgodwin in forum 2.x Legacy Premium Help
    Replies: 10
    Last Post: Jul 11, 2013, 10:55 PM
  2. ComponentLoader and Explicit Id
    By ETICS in forum 2.x Help
    Replies: 0
    Last Post: Jun 26, 2013, 4:21 PM
  3. [CLOSED] ComponentLoader inconsistency
    By RCN in forum 2.x Legacy Premium Help
    Replies: 10
    Last Post: Jun 07, 2012, 12:24 PM
  4. [CLOSED] ComponentLoader issue
    By RCN in forum 2.x Legacy Premium Help
    Replies: 3
    Last Post: Apr 12, 2012, 9:28 PM
  5. [CLOSED] ComponentLoader - DirectEvents
    By PatrikG in forum 2.x Legacy Premium Help
    Replies: 1
    Last Post: Mar 15, 2012, 1:20 PM

Posting Permissions