Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As far as an additional action goes, you can edit the LR config, namely default.usp and your [project].usr files. May I say from the outset though that mucking with config files may be <strong><em>risky</em></strong> and if you do so, take a backup of the files or project first and proceed with care.</p> <p>That said, this does seem to overcome the problem of "Create New Action" not being enabled (though I'd love to know the set of circumstances that causes that - @TheBlastOne indicates it's to do with the protocol used).</p> <p>Anyway, edit your default.usp to add a RulLogicRunRoot entry for your new action (say Action2) and configure it in the LR execution lifecycle, as follows:</p> <p><strong>default.usp</strong></p> <pre><code>[RunLogicRunRoot:Action2] MercIniTreeSectionName="Action2" RunLogicObjectKind="Action" &lt;-- "Action" in this case means LR object type Name="Action2" MercIniTreeFather="RunLogicRunRoot" RunLogicActionType="VuserRun" ... Profile Actions name=vuser_init,Action,Action2,vuser_end ... RunLogicActionOrder="Action,Action2" ... MercIniTreeSons="Action,Action2" </code></pre> <p>Not sure how much of your [project].usr file you need to edit but you should define the action and interpreter for your new action in any case:</p> <p><strong>[project].usr</strong></p> <pre><code>[Actions] vuser_init=vuser_init.c Action=Action.c Action2=Action2.c vuser_end=vuser_end.c ... [Interpreters] vuser_init=cci Action=cci Action2=cci vuser_end=cci ... </code></pre> <p>I'm unsure how much of the following is needed but it's probably sensible to create an entry for each (as per the Action script):</p> <pre><code>[Recorded Actions] ... [Replayed Actions] ... [Modified Actions] </code></pre> <p>Finally, don't forget to create an Action2.c (with appropriately named function to avoid clash with Action.c) in your project directory. Reopen your project in LR and it should contain Action2 in your scripts view.</p> <p>N.B. Sorry but I can't help with your question on threading... not that advanced yet.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload