cursor location moves

[Wills]

I've just installed v2.0 on Windows Vista and found some strange behaviour in respect of cursor positioning. This problem may only happen when editing files created by v1.2. The problem is that after carefully laying out the cursor track in one frame (say 12) and moving to another frame (say 15), when I return to the first frame (12) the cursor has moved to a completely new position. This bug is so bad that I'm moving back to v1.2.

I moved to v2.0 because of the frequent 'out of memory' unhandled exceptions with v1.2 + lots of other bugs. I hope Madcap are investing $$$ in improving their software quality because it doesn't look good!

[RamonS]

One sure way to give MadCap a chance to fix the problem is to report it at the right place, which is here: http://www.madcapsoftware.com/bugs/submit.aspx
Besides that, do you have a working OS such as XP available to try and see if the issue exists there as well? In my experience with Vista the most likely cause for application problems is Vista. I cannot say if that applies to this issue, but most of the time the $$$ not spent on quality are in Redmond.

[Richard Ferrell]

We added a new feature in Mimic 2.0 to make cursor alignment easier from frame to frame. Although perhaps we did a bad job of letting people know.

If you right click on a cursor object, there is a new option called “Maintain cursor continuity”. This is on by default.

If you move the End location of a cursor, mimic will automatically move the start position of the cursor on the next Frame so you do not have to. Or if you move the start location of a cursor, mimic will automatically move the end location of the cursor in the frame before it. To turn it off, just right click on the cursor and de-select Maintain Cursor continuity.