Reply to thread

Message

<blockquote data-quote="Kzach" data-source="post: 5730038" data-attributes="member: 56189">I find this an interesting comment because I have very little patience for programs that lack intuitive interfaces (Photoshop, I'm looking at you!). If I can't figure it out myself without having to resort to a guide, then I generally throw it out or give up on it.But with Maptools I was able to figure most things out without any guidance. Which meant that when I couldn't figure something out, I was willing to go to the RPTools forums and ask people and I almost always got an answer or could find one there already posted.This is one of my gripes about the DDI VT. When I first used it, I just assumed it did stuff automatically because it did SOME things automatically. But there's nothing intuitive or graphically obvious as to WHAT it does automatically and what you have to do manually. As it turns out, the very little that it does do automatically also means you have layers within layers of manual tasks for every single turn, none of which has an intuitive or graphically obvious interaction to let you know that you NEED to do it.Without either a higher level of automation or obvious graphical cues to let you know what needs to be done to maintain your character from round to round, without having to manually dig through obscure menus and unintuitive right-click contextual menus, I actually feel that the DDI VT is harder to use than even the most advanced Maptools framework.As for Maptools macros being buggy and cumbersome, I can't argue that; the JavaScript structure is a mess. Apparently they're working on version 2.0 which will be pure Java and apparently that will make macro building and framework building significantly easier and more powerful. It will also put it light years ahead of the DDI VT.</blockquote>

[QUOTE="Kzach, post: 5730038, member: 56189"] I find this an interesting comment because I have very little patience for programs that lack intuitive interfaces (Photoshop, I'm looking at you!). If I can't figure it out myself without having to resort to a guide, then I generally throw it out or give up on it. But with Maptools I was able to figure most things out without any guidance. Which meant that when I couldn't figure something out, I was willing to go to the RPTools forums and ask people and I almost always got an answer or could find one there already posted. This is one of my gripes about the DDI VT. When I first used it, I just assumed it did stuff automatically because it did SOME things automatically. But there's nothing intuitive or graphically obvious as to WHAT it does automatically and what you have to do manually. As it turns out, the very little that it does do automatically also means you have layers within layers of manual tasks for every single turn, none of which has an intuitive or graphically obvious interaction to let you know that you NEED to do it. Without either a higher level of automation or obvious graphical cues to let you know what needs to be done to maintain your character from round to round, without having to manually dig through obscure menus and unintuitive right-click contextual menus, I actually feel that the DDI VT is harder to use than even the most advanced Maptools framework. As for Maptools macros being buggy and cumbersome, I can't argue that; the JavaScript structure is a mess. Apparently they're working on version 2.0 which will be pure Java and apparently that will make macro building and framework building significantly easier and more powerful. It will also put it light years ahead of the DDI VT. [/QUOTE]

Verification