Results 1 to 4 of 4

Thread: States in Girder

  1. #1
    Join Date
    Apr 2008
    Posts
    2

    Default States in Girder

    I think that the states in girder are not implemented in the correct way.

    My opinion is that states in girder should be implemented as in "Algorithmic State Machines".

    Description:
    On every event a state change should occur. The next state should be specified by the user and it can be diferent then the current state, but it can also be the same as the current state. This will give more power to girder.

  2. #2
    Join Date
    May 2004
    Posts
    2,588

    Default

    There is already an action to set the state. If that's not good enough, use variables in a script.
    Beware of the robot.

  3. #3
    Join Date
    Apr 2008
    Posts
    2

    Default

    Quote Originally Posted by quixote View Post
    There is already an action to set the state. If that's not good enough, use variables in a script.
    Hmmmm,
    I thought that the purpouse of girder is to simplify the automation.

    If I had the time or wanted to write scripts I would write a simple application that would do that and would not need girder.

  4. #4
    Join Date
    May 2004
    Posts
    2,588

    Default

    How is
    Code:
    State1=State1 or 0
    State1="whatever"
    not simple? I doubt that you could write an application with 2 or 3 lines of code.
    You should look at the variable conditional plugin.
    Beware of the robot.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •