changing action of strokes

 First, I'm glad to see you are on IC6.1.

Set your path to the software on Solaris, it can be IC5141 or an older software as the strokes editor has not changed. It is in the <CDS_INST_DIR>/tools/bin directory - in my case /net/redneck/cds/sun4v/IC5141USR6/tools/bin. The resulting file (your def.strokes file) and other SKILL necessary to support the strokes should be in your home directory or your .cadence directory. Your .cdsinit should load it from where ever it is.

 Ted

Austin CAD Guy said:

 First, I'm glad to see you are on IC6.1.

Set your path to the software on Solaris, it can be IC5141 or an older software as the strokes editor has not changed. It is in the <CDS_INST_DIR>/tools/bin directory - in my case /net/redneck/cds/sun4v/IC5141USR6/tools/bin. The resulting file (your def.strokes file) and other SKILL necessary to support the strokes should be in your home directory or your .cadence directory. Your .cdsinit should load it from where ever it is.

 Ted

I think I found the sted executable here:

 /usr/local/met/apps/IC5033_sun4v.ISR200312121550/tools.sun4v/vframe/bin/

However, when I run "./sted", I receive the following error:

"Can't initialize the selected window system".

I am using rsh to connect to the Solaris machine from my Linux machine.  What do I need to do to run sted? 

I would suspect that the rsh window does not have the display properly set. Use the command: echo $DISPLAY to show the display and make sure it is set to your system display. Rsh usually does not reset the display.

If this does not work, you need to run a thin client which uses the native Solaris windows system.  Use VNC or some other Solaris based thin client to display back to your screen.

Austin CAD Guy said:

I would suspect that the rsh window does not have the display properly set. Use the command: echo $DISPLAY to show the display and make sure it is set to your system display. Rsh usually does not reset the display.

If this does not work, you need to run a thin client which uses the native Solaris windows system.  Use VNC or some other Solaris based thin client to display back to your screen.

I did a "setenv DISPLAY <myIP>:0.0", and now when I run "./sted", it just says "Segmentation fault".  How can I debug this? 

 I usually run VNC on my systems to handle the displays so is anyone who can answer the question:

How do I get a Solaris based tool to display on a Linux box?

Don't forget to 'xhost +' on the client side.  Also check that you can display back an xterm.

Andrew. 

aplumb said:

Don't forget to 'xhost +' on the client side.  Also check that you can display back an xterm.

 

Andrew. 

I am able to launch an xterm window when I am logged in to the Solaris machine.  I also ran "xhost +" on my local machine, but I am still getting the "Segmentation fault" error when I run "./sted". 

 Hi,

There is a new executable "stroke_editor" in the IC612 release under the tools/bin directory. This is even implemented for the Linux platform.  It looks a little different to the original "sted" but it should read and write the same format def.strokes type of file.

Also, I tend to work with "infix" turned on, in this case, if you perform a stroke (e.g. draw a C for Copy) over the instance/item in question, the command should take the current stroke/cursor location as input for the command.

Anyway, good luck with "stroke_editor" - it should solve your problems!

 Regards,

Lawrence.

 Wow! I didn't know that they had updated this. It is much nicer than sted. Thanks, Lawrence, it is a great day, I learned something new!

 Ted

skillUser said:

 Hi,

There is a new executable "stroke_editor" in the IC612 release under the tools/bin directory. This is even implemented for the Linux platform.  It looks a little different to the original "sted" but it should read and write the same format def.strokes type of file.

Also, I tend to work with "infix" turned on, in this case, if you perform a stroke (e.g. draw a C for Copy) over the instance/item in question, the command should take the current stroke/cursor location as input for the command.

Anyway, good luck with "stroke_editor" - it should solve your problems!

 Regards,

Lawrence.

Thanks for tip.  I was able to launch the stroke_editor application without any issues.