Is it me or is it sourcelink

S

Svenn Are Bjerkem

Guest
that has becoms so slow?

I wanted to look for a way to make a bindkey to switch between 0.625 and
0.3125 snap in composer. Maybe this is already covered in Sourcelink, I
thought, and logged in. Building the pages take very long time. Am I the
only one to see this behaviour?

Kind regards,
--
Svenn
 
I tried and it works as usual for me, sorry...

as for your question, the following should do the trick:

procedure( XXToggleSnapSpacing( wnd snap1 snap2 )
wnd~>xSnapSpacing = if( equal( wnd~>xSnapSpacing snap1 ) snap2 snap1 )
wnd~>ySnapSpacing = if( equal( wnd~>ySnapSpacing snap1 ) snap2 snap1 )
) ; procedure

hiSetBindKey( "Schematics" "Shift<Key>S"
"XXToggleSnapSpacing(hiGetCurrentWindow() 0.0625 0.03125)" )

cheers,

stephane

Svenn Are Bjerkem wrote:
that has becoms so slow?

I wanted to look for a way to make a bindkey to switch between 0.625 and
0.3125 snap in composer. Maybe this is already covered in Sourcelink, I
thought, and logged in. Building the pages take very long time. Am I the
only one to see this behaviour?

Kind regards,
Click to expand...
 
S. Badel wrote:
procedure( XXToggleSnapSpacing( wnd snap1 snap2 )
wnd~>xSnapSpacing = if( equal( wnd~>xSnapSpacing snap1 ) snap2 snap1 )
wnd~>ySnapSpacing = if( equal( wnd~>ySnapSpacing snap1 ) snap2 snap1 )
) ; procedure

hiSetBindKey( "Schematics" "Shift<Key>S"
"XXToggleSnapSpacing(hiGetCurrentWindow() 0.0625 0.03125)" )
Click to expand...
It is a lot quicker to ask questions on c.c.c than to look for them on
Sourcelink. Thanks a lot for the script.

--
Svenn
 
S. Badel wrote:
Hum... if the x and/or y grid were changed, calling this code would
change to the snap1 grid.
It can be seen as choosing one of the two grids (snap1) as the "default".

Ok, if f.e. x would change but not y, then they would get 'out of sync'
as you say. to make sure they are sync you can set ySnapSpacing to be
equal to xSnapSpacing, this is more logical i must admit.
Click to expand...
I do not see this as a very big disadvantage for my work as I am working
mainly on schematics. Problem was always some smart people who think
that .03125 is better than .0625 and that give some interesting effects
when copying things between designs.

--
Svenn
 
"Svenn Are Bjerkem" <svenn.are@bjerkem.de> wrote in message
news:cs00sf$mb0$1@athen03.muc.infineon.com...
S. Badel wrote:

procedure( XXToggleSnapSpacing( wnd snap1 snap2 )
wnd~>xSnapSpacing = if( equal( wnd~>xSnapSpacing snap1 ) snap2 snap1 )
wnd~>ySnapSpacing = if( equal( wnd~>ySnapSpacing snap1 ) snap2 snap1 )
) ; procedure

hiSetBindKey( "Schematics" "Shift<Key>S"
"XXToggleSnapSpacing(hiGetCurrentWindow() 0.0625 0.03125)" )

It is a lot quicker to ask questions on c.c.c than to look for them on
Sourcelink. Thanks a lot for the script.

--
Svenn
Click to expand...
Good but not bulletproof ... if xSnapSpacing or ySnapSpacing were changed
( say by some routing skill ;^)
then you would get stuck ... (or x & y out of sync... )

What I have seen on a few kits is binding the 0 key to the "fine grid" and
the 9 key to the "coarse grid"

(more often found in layouts )

YMMV
 
Hum... if the x and/or y grid were changed, calling this code would
change to the snap1 grid.
It can be seen as choosing one of the two grids (snap1) as the "default".

Ok, if f.e. x would change but not y, then they would get 'out of sync'
as you say. to make sure they are sync you can set ySnapSpacing to be
equal to xSnapSpacing, this is more logical i must admit.

cheers,
stephane

G Vandevalk wrote:
"Svenn Are Bjerkem" <svenn.are@bjerkem.de> wrote in message
news:cs00sf$mb0$1@athen03.muc.infineon.com...

S. Badel wrote:

procedure( XXToggleSnapSpacing( wnd snap1 snap2 )
wnd~>xSnapSpacing = if( equal( wnd~>xSnapSpacing snap1 ) snap2 snap1 )
wnd~>ySnapSpacing = if( equal( wnd~>ySnapSpacing snap1 ) snap2 snap1 )
) ; procedure

hiSetBindKey( "Schematics" "Shift<Key>S"
"XXToggleSnapSpacing(hiGetCurrentWindow() 0.0625 0.03125)" )

It is a lot quicker to ask questions on c.c.c than to look for them on
Sourcelink. Thanks a lot for the script.

--
Svenn


Good but not bulletproof ... if xSnapSpacing or ySnapSpacing were changed
( say by some routing skill ;^)
then you would get stuck ... (or x & y out of sync... )

What I have seen on a few kits is binding the 0 key to the "fine grid" and
the 9 key to the "coarse grid"

(more often found in layouts )

YMMV
Click to expand...
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top