If I make a manual change to line width, the next net
that I route should typically go back to Constraint, because the constraint
generally determines the correct line width for all nets. So this new feature
means more trips back to the Options tab, wasting time.
If I'm working with a partially-routed cline, I usually
want to pick up the line width of that cline. This is also annoying because the retained line width isn't always (in fact, it usually isn't) the line width of the partially-routed
cline. Again, I have to make a journey to the Options tab which slows down my
progress. Sometimes the partially-routed line width is picked up, while other times the last-used line width is used; I haven't figured out what makes either condition occur.
I can think of two options to make my life easier:
Also, as I mentioned in the post linked above, I want to change line width with the mouse wheel during
routing without losing PCB canvas area due to the Options tab being open. Assuming
I can do that, this becomes even more of a problem because I now have the
ability to change the line width with the Options tab closed, and I have no way
to visually identify/confirm the current line width. Nor do I necessarily know what line width has been retained (I can guess and with fairly high accuracy, but there's no UI feature to show me for sure).
I rarely route to anything other then constraints/neck, so it hasn't been an issue for me. I also have the options tab open and the find filter closed. But a workaround would be a funckey to force it back to constraint.
funckey C "setwindow form.mini; FORM mini acon_line_width constraint; setwindow pcb"
In reply to aCraig:
It works great if you use constraints. The moment I type in a line width, then I start wondering what use case makes line width retention useful.
I used "button wheel_up FORM mini acon_line_width Constrain" to get back to the Constraint value without using the Options panel. But that doesn't help me scroll through the MRU list.
While pondering a better reply, can you answer the following?
1) Do you use dual monitors with one of them retaining the options mini window?
2) Do you use a trackball or mouse? With Cadence a mouse can be a lot of exercise. I have found a trackball is lightning fast for those quick selects in the mini forms.
I tried Craig's method but using default instead of constraint i.e.funckey a "setwindow form.mini; FORM mini acon_line_width default; setwindow pcb"I had a little play with it and it seems to work...
Jim O'MahonyStudiel Toulouse
In reply to redwire:
Thanks redwire! I'd love to hear your "better reply"! :)
This feature really aggravates me in a way that Allegro never has in the 6 years I've been using it. Especially when I go to complete a partially-routed Cline seg, and the line width of the partially-routed seg isn't picked up, I get upset. Maybe I work differently than most users, or I don't understand this feature and how to harnass it, but so far it wastes my time and I'd like to turn it off.
1. I have dual monitors but I keep the mini windows inside the Allegro window. I'd forgotten I could tear out the min windows, but it doesn't immediately make me excited. Maybe I need to play with it for a while to get used to it and see if it holds value for me. One reason is that I usually keep the schematic open on my other monitor while I do PCB design, and having the mini windows open clutters up the schematic screen.
At first blush, it does move things farther away (PCB is on the right monitor) so when I need to interact with the mini windows it makes that less pleasant.
2. I use a mouse. I can certainly understand the gyrations a mouse can induce, which is why I happily use loads of keyboard commands. That way, I can keep the mouse focused on a relatively small area of the screen.
In reply to EvanShultz:
First a few style tips. I have been on Allegro since '94 so I have seen a lot of unwanted changes but over time I get used to them. I also have gotten used to *not* using the keyboard except for a few Function keys (zoom in/out, next, rotate) which I keep at my fingertips. My hand *rarely* gets up to type in commands... And as I said above I have become a trackballer which kicks butt over mousing.
Recently I have had to use PADS and suddenly my thoughput has been reduced as I have to enter so many commands by keyboard! I have never seen such inefficiency in a layout tool...but I digress. I think your technique could use some skilled mentoring to show you have fast Allegro *can* be.
So, your issue. My Allegro does not do what you find. It *does* pick up the last routed width...unless...I have overridden the manual width options setting which is the override for that *session* of "Add Connect". Once you override, Allegro will honor that width. This can be very powerful or as you have found, detrimental.
One way around it is to select "done" and restart add connect which will go back to automatic width selection. Allegro will pick up the existing cline width until you override in the options box. Painful? It depends on your point of view.
I don't manually enter any entire command, except when I'm experimenting with SKILL or in very rare circumstances. I use the keyboard for funckeys and other shortcuts which I've customized. My left hand stays on the keyboard and augments my right hand on the mouse. Typing in commands would be painful and ridiculous and bear a huge mental burden to remember. I am fast with Allegro; I'm not a rookie.
Manually overriding the line width is what I'm talking about. I'm generally constraint-driven, but when I need to deviate from the constraint width Allegro sticks with my manual override. I still don't understand the scenario where line width retention is helpful, but I'm sure it exists. In my current workflow, I'd be happy to have the option to disable this feature.
I don't invoke Add Connect, either. Not very often, anyway. I stay in the EE mode while working with copper which allows me to click on a Cline, Pin, Ratsnest, etc. and just begin routing (automatically bouncing into Add Connect mode). Even if I enter Add Connect mode, begin routing, change a line width, select Done, re-enter Add Connect mode, and begin routing a different Cline/Ratsnest, the manually-entered line width is retained. It doesn't pick up the Cline's existing width. Maybe I'm following a slightly different process than you?
I may try a trackball, but that does not absolve line width retention. It may only make it faster to stop the manual override.
Not sure what you're doing wrong but it works fine here even in EE mode -- which by the way is just an overlay within the overall tool.
A user preference variable for disabling this behavior is now available. You will need to upgrade Allegro to version 16.60.011.
variable name - acon_no_width_override_retain