I believe this bug is probably related to a policy of not tracking the current "mode" as an independent piece of state, and instead inferring the "mode" from the presence or absence of advanced reasoning nodes. Corroborating that hypothesis, the current mode is not visible anywhere in the interface. (BTW, I do not think modes are a good idea, but your shortcuts are explained referencing the idea of modes.) Probably, the ultimate source of the problem is a policy of developing and testing the mousing interface first, and only adding keyboard shortcuts afterwards. I have looked inside .rtnl files, and they have long sequences like Create("Claim"), SetText, CreateChild(mapN_M, "Claim"). I suggest that a policy of mapping the keyboard shortcuts to the file format might allow a completeness argument, something like "The keyboard shortcuts are sufficient to build any map, because the file format is sufficient for any map.", possibly with some caveats like "aside from sizes and positions of boxes." Thank you for working on argument diagramming! |
10 years ago |
Hi @Johnicholas, thanks for you bug report we will look into it and keep you posted! |
by rob 10 years ago |
Hi @Johnicholas, this is not a bug but is by design. You can only change the map type when you have two, or more, connected nodes. So do this:
thanks, Rob |
by rob 10 years ago |
Please sign in or create an account to comment.