kicad-developers team mailing list archive

[Andrey Fedorushkov <andrf@xxxxxxx>]

In attach is one of the files.
For example, a macro is very simple to make the ground skip and via between the microwave lines.
I wrote the "mini-guide" in the newsletter, how to use macros when my colleague Roman Bashkov completed code.
I can briefly repeat.
For example, it is necessary to do the Via group (eg two via) with some (different) pitch:
use hotkeys
macros 1 record
<ctrl+1> - X - <move cursor> - V - <End> - <PgUp> - X - <move cursor> - V - <End> - <PgUp> - <ctrl+1>
Move cursor to new pad (or point) and press <1>.

The sequence hotkeys may be very different.

Move group parallel slope tracks (eg data bus):
move cursor to first need slope drag track
<ctrl+2> - D - <move cursor> - <End>  <ctrl+2>
move cursor to next slope track and press only <2>

I used macros for leveling length tracks and shove tracks (before CERN release PNS and tuning length)
and a more for what.


> Вторник, 19 апреля 2016, 22:10 +03:00 от Wayne Stambaugh < stambaughw@xxxxxxxxx >:
> 
> Did record your macro files or did you code them by hand with a text
> editor?  The reason I ask is that I have never been able to record a
> sensible macro.  I far as I can tell, the macro record feature only
> records hot key events which would make it's usefulness somewhat
> limited.  I do see the possibility of creating a macro file by hand
> using a text editor as useful but this requires an incredible amount of
> knowledge of how the hot key event system works which is way beyond the
> skill level of your typical user.  I will restore the macro feature for
> now but this really needs to be revisited.  Python scripting certainly
> provides much more flexibility and power for automating board layout
> tasks than the macro recording system.
> 
> On 4/19/2016 2:56 PM, Andrey Fedorushkov wrote:
> > Wayne, 
> > 
> > I can not read the newsletter for the past two weeks.
> > I did not see the negative reviews about macros.
> > 
> > I use macros to repeat a set of simple operations.
> > Moreover, a long time. When there was no opportunity to use python scripts. 
> > And transfer macros to python have neither the time nor the possibility.
> > 
> > Here are some examples of my pcb (2008-2015).
> > All are made in kicad.
> > Without the use of macros is not done :)
> > 
> > At the same time I have been involved in supporting Russian GOST in the kicad (starting with a revno of 62).
> > My daughter helped to draw and add Cyrillic characters in vector font 8 years ago (revno 1285). ;)
> > 
> >> Вторник, 19 апреля 2016, 15:14 +03:00 от Wayne Stambaugh < stambaughw@xxxxxxxxx >:
> >>
> >> Andrey,
> >>
> >> Users have complained in the past the macro code doesn't do anything
> >> useful and I could never get it to anything useful either.  I sent out
> >> message over a week ago about getting rid of the macro code.  No one
> >> complained including you.  You should have spoke up so I didn't waste my
> >> time removing it.  I'm curious exactly what it is you are using them for
> >> because I cannot seem to record anything useful.
> >>
> >> Wayne
> >>
> >> On 4/19/2016 1:39 AM, AndreyAF wrote:
> >>> Wayne!
> >>>
> >>> Remove macros code?
> >>> Why and what for?
> >>> I actively use this unique feathure.
> >>>
> > 
> 

-- 
Andrey Fedorushkov

Attachment: rad_fft.mcr
Description: Binary data