ULP instantaneous command execution

On 21/08/14 09:06, Pavel Soukup wrote:

I'm starting to use ULP scripting, but I'm lacking some important

functions.

 

1. Some actions on the sch/brd seems to be only possible through

script/exit(), not through ULP

     for example I want to delete a part.

Yes, that is a known limitation of the user language. There are all

sorts of hacks to work around it but still, it sucks.

2. Some actions that are possible by clicking command buttons are not

possible in scripting. I'm not able to make a copy of a part in

schematic by script.

You can simulate mouse clicks by giving coordinates.

     Having part U1, "copy U1 U2" generates an error message (The copy

command with a name can only be used in a library!)

If U1 is located at (2.7 3.7) and you want U2 at (5.0 4.2) then you can

issue:

        copy (2.7 3.7) (5.0 4.2);

This will create a copy. It doesn't guarantee it'll be called U2,

especially if it's not allowed to be called U2 (because U2 already

exists, for example).

     Setting group and executing "Cut; Paste" requires action of a

mouse.

 

In theory, again, this should be possible :

        group (c 3.2 2.7) (c 5.2 2.8);

   defines a group containing the components located at (3.2 2.7) and at

(5.2 2.8). Note the "(c xxx)" syntax to simulate a mouse click with the

control key (see help for the group command).

        cut (4.2 2.7);

   will put that group in the cut/paste buffer with an anchor in the

middle, and

        paste (8 2);

   will place a copy off to the right.

The trick is to construct all these lists of coordinates by analysis of

the objects on the page, which is left as an exercise for the reader.

On 21/08/14 18:26, Rob Pearce wrote:

On 21/08/14 09:06, Pavel Soukup wrote:

I'm starting to use ULP scripting, but I'm lacking some important

functions.

 

1. Some actions on the sch/brd seems to be only possible through

script/exit(), not through ULP

     for example I want to delete a part.

Yes, that is a known limitation of the user language. There are all

sorts of hacks to work around it but still, it sucks.

 

Sorry, bad form to follow up my own post, but I forgot to say...

Although this limitation sucks, I can entirely understand why it might

exist. Being able to modify the schematic in the middle of a loop

iterating over the objects in that schematic raises all sorts of

gotchas. Enforcing a strict "analyse, decide, construct action list,

then act" order helps avoid foot shooting.

On 21/08/2014 8:06 p.m., Pavel Soukup wrote:

I'm starting to use ULP scripting, but I'm lacking some important

functions.

 

1. Some actions on the sch/brd seems to be only possible through

script/exit(), not through ULP

There are a bunch of actions that can be done from within the ULP. But

anything that changes your design is done on exit from the ULP.

Sometimes you exit and immediately re-enter the ULP to achieve a change.

e.g. exit (do something; "run my uLP";)

      for example I want to delete a part.

      The only way I had found is adding "detele partName" to the

(possibly very long) string that will be executed after the ULP finishes

      or a Copy part, is possible at the end of the ULP, but in this way

I cannot make any changes on it.

      Is there a better/instantaneous way to make serious changes (like

delete or duplicate parts)?

Sometimes you exit and immediately re-enter the ULP to achieve a change.

e.g. exit ("delete part"; "run my uLP";)

 

2. Some actions that are possible by clicking command buttons are not

possible in scripting. I'm not able to make a copy of a part in

schematic by script.

The part of interest is in a library so simply use the ULP to determine

the library and device name and ADD it to the schematic at the chosen

location once the ULP exits. Multiple gate devices may be tricky to get

right though.

If it's a sch/brd pair you have acquired and does not use your libraries

, you can use the ULP exp-lbrs.ulp to export and create a new library of

its parts and draw from that.

HTH

Warren