C1Menu not triggered by new node (client-script)

Originally Posted 3 February 2015, 10:27 pm EST

  • Originally Posted 3 February 2015, 10:27 pm EST

    HI

    I have a problem about C1Menu not triggered by new node (node added in client-script) :

    C1Menu :

      <wijmo:C1Menu ... TriggerEvent="Rtclick" Trigger=".wijmo-wijtree-node" ...>
    ...


    New node client-script :

    $(node.element).c1treeviewnode("add", { text: text, value: value });


    C1Menu.Trigger=".wijmo-wijtree-node" are works fine with original node (C1TreeViewNode added in server-side C#),
    but not works with client-script new node.

    I have check the htmls are the same of server-side node and client-script node :

      <li class="wijmo-wijtree-item" style="list-style-type: none;">
    <div role="treeitem" aria-expanded="false" aria-checked="false" aria-selected="false" class="wijmo-wijtree-node ui-state-default">
    <span class="ui-helper-clearfix wijmo-wijtree-inner ui-corner-all">
    <span></span>
    <a href="#" rel="nofollow">
    <span>Node 1</span>
    </a>
    </span>
    </div>
    </li>


    or is there have any official C1Menu.Trigger works for C1TreeViewNode(server-side and client-side).

    Best regards

    Chris
  • Reply

    Hello,

    I was able to replicate the issue at my end. I have escalated the issue to the concerned team. I will let you know as soon as I get any information in this regard.

    In the meanwhile, I could observe that in a sample provided by you in the other post(http://our.componentone.com/groups/topic/c1treeview-out-of-stack-space-with-client-script-new-node/), you have get it to working by resetting the trigger of C1Menu on the client side. You may use this as a workaround for this issue currently. We will update you as soon as we get any information.

    Thanks,
    Manpreet Kaur
  • Reply

    Hello,

    As per the development team, the cause of this issue is that when we set the Trigger for menu, it will add event to the node element which meet the "Trigger" selector. But if we create a new element, it has no event. So, to resolve this issue we need to use the workaround suggested above i.e. to reset the Trigger when ever a new node is added.

    Thanks,
    Manpreet Kaur
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels