How can I control the order on what tick methods are executed across components?











up vote
1
down vote

favorite












I have multiple components that define a tick method and I need to control the execution order. With the following components:



AFRAME.registerComponent('component-a', {    
tick: function () { console.log('ComponentA'); }
});

AFRAME.registerComponent('component-b', {
tick: function () { console.log('ComponentB'); }
});

AFRAME.registerComponent('component-c', {
tick: function () { console.log('ComponentC'); }
});


And the following entity:



<a-entity component-a component-b component-c></a-entity> 


I want to guarantee the following tick order: component-a, component-b, component-c










share|improve this question




























    up vote
    1
    down vote

    favorite












    I have multiple components that define a tick method and I need to control the execution order. With the following components:



    AFRAME.registerComponent('component-a', {    
    tick: function () { console.log('ComponentA'); }
    });

    AFRAME.registerComponent('component-b', {
    tick: function () { console.log('ComponentB'); }
    });

    AFRAME.registerComponent('component-c', {
    tick: function () { console.log('ComponentC'); }
    });


    And the following entity:



    <a-entity component-a component-b component-c></a-entity> 


    I want to guarantee the following tick order: component-a, component-b, component-c










    share|improve this question


























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I have multiple components that define a tick method and I need to control the execution order. With the following components:



      AFRAME.registerComponent('component-a', {    
      tick: function () { console.log('ComponentA'); }
      });

      AFRAME.registerComponent('component-b', {
      tick: function () { console.log('ComponentB'); }
      });

      AFRAME.registerComponent('component-c', {
      tick: function () { console.log('ComponentC'); }
      });


      And the following entity:



      <a-entity component-a component-b component-c></a-entity> 


      I want to guarantee the following tick order: component-a, component-b, component-c










      share|improve this question















      I have multiple components that define a tick method and I need to control the execution order. With the following components:



      AFRAME.registerComponent('component-a', {    
      tick: function () { console.log('ComponentA'); }
      });

      AFRAME.registerComponent('component-b', {
      tick: function () { console.log('ComponentB'); }
      });

      AFRAME.registerComponent('component-c', {
      tick: function () { console.log('ComponentC'); }
      });


      And the following entity:



      <a-entity component-a component-b component-c></a-entity> 


      I want to guarantee the following tick order: component-a, component-b, component-c







      aframe webvr webxr






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 11 at 4:12

























      asked Nov 10 at 23:46









      Diego Marcos

      1,5851913




      1,5851913
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          A-Frame does not have a built-in way to define tick execution order. Ticks will execute in the order in what components are initialized. One can easily control the execution by having a manager component that calls the components methods in the desired order:



          AFRAME.registerComponent('manager', {    
          tick: function () {
          const el = this.el;
          el.components['component-a'].print();
          el.components['component-b'].print();
          el.components['component-c'].print();
          }
          });

          AFRAME.registerComponent('component-a', {
          print: function () { console.log('ComponentA'); }
          });

          AFRAME.registerComponent('component-b', {
          print: function () { console.log('ComponentB'); }
          });

          AFRAME.registerComponent('component-c', {
          print: function () { console.log('ComponentC'); }
          });


          On the following entity:



          <a-entity manager component-a component-b component-c>





          share|improve this answer





















          • Is it a good idea to create a system exclusively for such managing, or is it an overkill ?
            – Piotr Adam Milewski
            Nov 11 at 11:44













          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














           

          draft saved


          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53244537%2fhow-can-i-control-the-order-on-what-tick-methods-are-executed-across-components%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          1
          down vote













          A-Frame does not have a built-in way to define tick execution order. Ticks will execute in the order in what components are initialized. One can easily control the execution by having a manager component that calls the components methods in the desired order:



          AFRAME.registerComponent('manager', {    
          tick: function () {
          const el = this.el;
          el.components['component-a'].print();
          el.components['component-b'].print();
          el.components['component-c'].print();
          }
          });

          AFRAME.registerComponent('component-a', {
          print: function () { console.log('ComponentA'); }
          });

          AFRAME.registerComponent('component-b', {
          print: function () { console.log('ComponentB'); }
          });

          AFRAME.registerComponent('component-c', {
          print: function () { console.log('ComponentC'); }
          });


          On the following entity:



          <a-entity manager component-a component-b component-c>





          share|improve this answer





















          • Is it a good idea to create a system exclusively for such managing, or is it an overkill ?
            – Piotr Adam Milewski
            Nov 11 at 11:44

















          up vote
          1
          down vote













          A-Frame does not have a built-in way to define tick execution order. Ticks will execute in the order in what components are initialized. One can easily control the execution by having a manager component that calls the components methods in the desired order:



          AFRAME.registerComponent('manager', {    
          tick: function () {
          const el = this.el;
          el.components['component-a'].print();
          el.components['component-b'].print();
          el.components['component-c'].print();
          }
          });

          AFRAME.registerComponent('component-a', {
          print: function () { console.log('ComponentA'); }
          });

          AFRAME.registerComponent('component-b', {
          print: function () { console.log('ComponentB'); }
          });

          AFRAME.registerComponent('component-c', {
          print: function () { console.log('ComponentC'); }
          });


          On the following entity:



          <a-entity manager component-a component-b component-c>





          share|improve this answer





















          • Is it a good idea to create a system exclusively for such managing, or is it an overkill ?
            – Piotr Adam Milewski
            Nov 11 at 11:44















          up vote
          1
          down vote










          up vote
          1
          down vote









          A-Frame does not have a built-in way to define tick execution order. Ticks will execute in the order in what components are initialized. One can easily control the execution by having a manager component that calls the components methods in the desired order:



          AFRAME.registerComponent('manager', {    
          tick: function () {
          const el = this.el;
          el.components['component-a'].print();
          el.components['component-b'].print();
          el.components['component-c'].print();
          }
          });

          AFRAME.registerComponent('component-a', {
          print: function () { console.log('ComponentA'); }
          });

          AFRAME.registerComponent('component-b', {
          print: function () { console.log('ComponentB'); }
          });

          AFRAME.registerComponent('component-c', {
          print: function () { console.log('ComponentC'); }
          });


          On the following entity:



          <a-entity manager component-a component-b component-c>





          share|improve this answer












          A-Frame does not have a built-in way to define tick execution order. Ticks will execute in the order in what components are initialized. One can easily control the execution by having a manager component that calls the components methods in the desired order:



          AFRAME.registerComponent('manager', {    
          tick: function () {
          const el = this.el;
          el.components['component-a'].print();
          el.components['component-b'].print();
          el.components['component-c'].print();
          }
          });

          AFRAME.registerComponent('component-a', {
          print: function () { console.log('ComponentA'); }
          });

          AFRAME.registerComponent('component-b', {
          print: function () { console.log('ComponentB'); }
          });

          AFRAME.registerComponent('component-c', {
          print: function () { console.log('ComponentC'); }
          });


          On the following entity:



          <a-entity manager component-a component-b component-c>






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 10 at 23:55









          Diego Marcos

          1,5851913




          1,5851913












          • Is it a good idea to create a system exclusively for such managing, or is it an overkill ?
            – Piotr Adam Milewski
            Nov 11 at 11:44




















          • Is it a good idea to create a system exclusively for such managing, or is it an overkill ?
            – Piotr Adam Milewski
            Nov 11 at 11:44


















          Is it a good idea to create a system exclusively for such managing, or is it an overkill ?
          – Piotr Adam Milewski
          Nov 11 at 11:44






          Is it a good idea to create a system exclusively for such managing, or is it an overkill ?
          – Piotr Adam Milewski
          Nov 11 at 11:44




















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53244537%2fhow-can-i-control-the-order-on-what-tick-methods-are-executed-across-components%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Xamarin.iOS Cant Deploy on Iphone

          Glorious Revolution

          Dulmage-Mendelsohn matrix decomposition in Python