So was there ever an answer to this question?
I'm running into the same issue.
The REASON that it's an issue, is that I have an exists() check going on to see if the trigger already exists.
Since the triggers being created are (I'm guessing) pid's or something, the names NEVER match, so I end up with many many duplicates.
So, other than assigning a variable, how can this functionality be fixed to work as intented (ie. naming your triggers the way that you want them to be.) ??
Code: Select all
function defDsplyTrigs()
if exists("Defs", "trigger") == 0 then
cecho("<white>Trigger Group: <gold>Defs <white> does not exist.\n")
else
for k,v in pairs(defenses) do
if exists(v.name, "trigger") == 0 then
permBeginOfLineStringTrig55ger( v.name, "Defs", { v.line, v.upline }, v.name .. [[:echo("]] .. v.display .. [[", "white", "c");selectString(matches[1]);replace("]] .. v.name .. [[" ,1)]])
-- cecho("<white>" .. v.name .. " <cyan>" .. v.line .. "\n")
end
end
end
This is my trigger creation line. I have a defenses table that is in the form of
Code: Select all
{name ="blah", display="whatever", line = " something", upline="something else"}
The cecho line that I have commented out shows the correct v.name with the correct v.line.
So, am I missing something here?
Assigning variables, as suggested below will do what? It was my understanding that when you assigned a variable to a trigger line (temp triggers if I remember right), that the variable got the idstring of that trigger.
If we go this way, then following the thought through is that I will need to maintain a separate list of the triggers that were created to keep track of what triggers were set up and what weren't. This seems to me, to be a very poor way to apply some of these functions. It makes a mockery of exists(), and now I'm rambling.
What needs to be done so that we can name our triggers from scripts?
