Fix one thing break another....force vectors

[kittmaster]

Version 9 "partially" fixed this issue. So some background......when I unselect "force vectors" option, that means I don't want to see them.......ever.......until I call for them again. When I forward annotate, import netlist, return from autorouter.......guess what......force vectors return.....when I explicity turned them off at the beginning of the design....why does UB think that it can override my preferences when I turned it off???????????????

Version 9 had it 80% fixed.....but now 10.0.1 is running just like 7,8, and 10.0.0......arrrrrrrrrrrrrrrrrrr

[lacy]

I tried turning off force vectors by unchecking the box in the project view and then autorouting an unrouted project  that I had. Force Vectors remained off after I did the autorouting. I haven't tried it yet with the others that you mentioned yet. Once I try it I will give you my results.

Did this occur after doing each one individually or did it occur after you did them sequentially? 

[kittmaster]

Seems to do it when I import any new netlist or a forward annotate, if the autorouter doesn't get to 100% for whatever reason they return.

Seems like any variable passing scenerio causes the force vectors to become "rechecked" after I've turned them off. Also this is a clean install and not an upgrade from 9 to 10.

[lacy]

O.K. I tried the forward annote and it did turn force vectors back on. It is my opinion that this may being caused by the way Ultiboard is being updated from Multisim. When you forward annote it seems to me that you are overwriting the current project file with basically a new file. Based upon what I observed,  Ultiboard is treating the forward annote basically as new project.  even though everything looks the same on screen except for your changes.

These are just my observations. on this subject. Nestor or Max may have better information for you.

[kittmaster]

It will do it on other times to, like when UR kicks out.

Its a real PITA, it reactivates ratsnest and force vectors....this was addressed and partially fixed in 9 and now its returned in 10....

Its been recurring since version 7.

thanks for the follow up

Message Edited by kittmaster on 07-30-2007 10:26 PM

[lacy]

I kept trying the autorouter last night and I never could get it to reproduce this problem. I am going to continue investigating this and see if maybe there is a way to prevent the project view from resetting after changes are made to the project. I am hoping that maybe something in the main setting may need to be changed in order for this not to occur. If I find anything I will definite post my findings.

In the meantime, Nestor or Max may have some information that could help that we just don't know about yet.

[lacy]

No Joy. I have been through every menu I can find and I haven't found anything that I could change that would keep this from occuring. This may be something that needs fixed internally in software and not something we can alter through any settings. Nestor will have to look at this and let their R&D team take a crack at it.

I tried everything I know. Sorry I could be of more help.

Have a Nice Day.

[kittmaster]

lacy

I've gone round and round with ewb to get it fixed. It is an internal issue and not user settable globablly. It should remember this as part of the file save routine, but it doesn't. As mentioned they fixed it in 9 partially but is now acting like the old behavior of 7 and 8 and early 10.

Thanks for taking a look

[nestor-sg]

Chris, Lacy,

Yes, this indeed should be a global setting. I checked in v10.0.1 and I can reproduce it when you annotate or import netlists, on these cases the project makes a reset, therefore bringing the design toolbox to its default state.

However after autoplacing, autorouting, I can't seem to rpeoduce the behaviour, the ratsnest or force vectors keep turn off.

I checked with R&D and yesterday they filed the report to check how to make it remember the setting after project resets like annotates or imports...