On Fri, Apr 19, 2013 at 07:11:48PM -0500, Dick Hollenbeck wrote:
LAYER_NUM is mostly used as an iterator in our code, used to walk through for
loops.
Also as a parameter for indexing into stuff and especially LAYER_MSK
stuff. The main 'practical' reason for its introduction was finding
Is this still supposed to work?
IIRC it dragged the module with all the tracks (without drc or stuff).
The result was ugly but at least a little useful.
Now it seems that drag is like move (i.e. tracks remains there).
Is this because of the new 'track attached to the pad' code (considering
the
On Saturday, 20 de April de 2013 at 11:16, Lorenzo Marcantonio wrote:
Is this still supposed to work?
IIRC it dragged the module with all the tracks (without drc or stuff).
The result was ugly but at least a little useful.
Now it seems that drag is like move (i.e. tracks remains there).
On Sat, Apr 20, 2013 at 11:57:13AM +0200, Miguel Angel Ajo wrote:
Wow, we have that now? (tracks connected even without pointing tip to pad
center), I missed that feature a lot :-)
I don't like that too much since it's easy to forgot to clean up, but I agree
it can be convenient. It's not a
Tracks used to be dragged with the component IIRC.
IMO, to make the drag more beautiful, we would just need to have the tracks
keep the same orientation and angles as before the drag.
This would be beautiful combined with the push-n-shove that I think is
being worked on by a certain Mr.
5 matches
Mail list logo
