-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node manipulation by level #47
Comments
Hey. |
As mentioned in #3 and gambitproject/gte#32
Quoting @stengel on 26th July 2015:
I enclose a new picture to illustrate this. This is not urgent but if in place would allow to grow game trees quickly, and I think it is not too difficult to implement in SVG, in particular since it is similar to something you have already done with the information set:
We consider these now separately. The important thing is that the EFFECT of clicking on the multiaction line should be UNIFORM, not the ACTION, which makes it more predictable (see also the discussion in
gambitproject/gte#32). To illustrate this point, suppose we ADD children to the
multiaction line highlighted in the enclosed picture multiaction.png
Here all nodes have two children except for the second node. Here, in mode "ADD CHILDREN" (+) clicking on the line should give two children to the leaf. After this all nodes have the same number of children, namely two, and clicking again on the line will then add a third child to each node.
General behaviour for "add children":
General behaviour for "delete nodes":
Again, the aim is to have predictable behavior.
General behaviour for "set player":
General behavior for "create information set":
I am not sure this is a very time-saving activity, hence postpone this.
However, for ADDING NODES and SETTING PLAYER the multiaction functionality would be useful to create a game tree quickly.
The UNDO operation (which we don't have at all yet) would naturally have to apply to the entire multiaction operation, so this is important when recording the state of the game before applying the multiaction operation.
The text was updated successfully, but these errors were encountered: