Figured it out... 
DVDProfileLoop will expose the ProfileID and sort name together.

a request... possibly just a suggestion...

add the "Field names" on the "1" record, so the batch file can be sure it's getting the correct stuff.

I didn't realize that it analyzed the batch file for field names until today... very clever.

but, what are the rules of same?

Also, serious bug... at least for me... SortTitle and Title are both passed with data from Title.

@bspeng:

Both those issues should be easy to rectify. I'm a bit busy for a few days, but I won't forget. Thanks for the report and the kind words.

Oh, the rules: um ... I forget. 

Take a look at the sample.bat files, by example:

Put in a Rem statement just like the others, and the field name spelling should match the spelling you see in the checkbox list during plugin operation, reading from left to right, up to and not including the space just before the "-" if there is one. If there is no "-", then just use the entire token. I think that's it. Actually, I'll bet your intuition, by looking at the examples, will get it right 99.9% of the time.

Let me know if you find any other issues.

Edit: Note to myself: did I ever fix the last problem that jusjoken reported? Maybe this is related. Try not to forget to double check.

result:
It is doing the job for me.

but fyi...
seems like the "Parms will be flagged..." is less persistent, thus the bat is less-often in-use.
but, if you force the review of the bat file, the file is left "open" until I exit dvdprofiler

Seems like "Title" is forced, thus it's check in the parm list even if it's not in the bat file

and a request:
Add field "HasChildProfiles" true/false.  This would be nice, but, if it's hard, forget about it...

thank you again for everything

Quote:
- what do you mean by "force the review"?

there is some logic that triggers the "parms will be flagged" thingy... it doesn't happen all the time... In other words, sometimes it just lets you run the bat file without intervention...  if it does the "parms will be flagged" thingy, then notepad can't save the bat file (already open in another window) until you exit dvd profiler.  This is not really a big deal, except during testing when you're making many minor tweaks to the bat file... and dvdprofiler takes it sweet time loading up...

Quote:
- curious as to how you plan to use the parent indicator

for me, there is no parent disc(iso), only children.  this give me a way to ignore parents.  (when running everything by doing "filtered" with no filters set)

Quote:
- wouldn't you also need the list of child profiles?

when running everything (do "filtered" with no filters set)  I have the children. it's the parents i don't need...

Announcing DVDProfileLoop 1.9

- Fixed .bat file left open after parm scan. Now closed.
- Added Box Set Content Count as a parameter, used in the same way as the others (case insensitive), e.g. rem %2 = box set content count, for auto scan recognition

@bspeng
I could not reproduce the phantom title issue you reported. The scan is not very smart, so
one of your other comments might have triggered it.

(Edit: And I'm sure you know that box set content count = 0 means no children.  )

Quoting bspeng:

Quote:
v1.9 works great!

one last request...

if the "show bat window" is checked, pass one extra data: "ShowWindow" or conversely if not checked, send "HideWindow"

This would be handy for selectively using "PAUSE" in the bat file.
(A hidden window with a PAUSE is pain in the butt.)

For that matter, this would be nice in LoadDVD too  (Play vs Play/s), but the way it's working now (with having to add "play"), this might be immaterial.

That's wonderful! 

So I think I'll let matters rest for awhile. I was glad to be responsive and I appreciate your support. Next release will be after we accumualte a number of requests and/or significant bugs. Putting small changes in one at a time is not very productive or fun.

You could implement the selective pause by simply passing your own pseudo flag in. For example, pass collection number when you want to pause, and don't pass it when you don't want to pause - something like that. In fact you may even be able to detect or control the window state from the batch file, using windows commands.