Would it be possible to show groups with only a single entity in them as “flat”, without any grouping? Or maybe an option to have that behavior?
In 7.1, job batch rows that only have a single job will still show up as a batch, but they will behave like single jobs (ie: all columns will be the same as the single job, and you can interact with it like a single job).
Cheers,
Ryan
Won’t that be a bit confusing? As the group itself won’t behave the same in different scenarios, and also, you would basically see 2 identical jobs in a hierarchy.
Can you elaborate on the different scenarios you’re referring to?
To clarify what I mean, the Monitor treats a selected batch like you’ve selected the jobs within that batch. This is why you can modify the properties for all jobs in a batch by right-clicking on the batch row itself. So if you have a batch selected that only has a single job, it’s like you’ve just selected that single job.
The batch rows are also distinguished by having the expansion arrow, being bold, and having the batch name shown in the job name column. In 7.1, we’ll also have the job count for the batch in brackets next to the batch name under the job column. So they’re not exactly identical.
Cheers,
Ryan
I mean that the ‘group’ node would have all props of the child job if it only had 1 job, but would not have them if it had more than 1 job. So its behavior would be inconsistent.
Also, if it was just a duplicate entry point to the same job, isn’t it redundant? Its simply a parent, that has a child, and they share all their properties.
Basically, we have cases where we submit groups of jobs at a time, but we do not know in advance how many jobs will be in the group. So we preassign the group name to all jobs as a property. But then if the artist only submits one job, we now get a redundant group entry in the monitor. Sometimes, the jobs themselves spawn further child jobs, in which case we want the group to appear.
What i noticed, is that artists now turn off the group display, simply because they need to keep expanding their single job submissions, and i find that worse then having an option somewhere to not add a group node if there is only one job in it…
This is actually intentional in 7.1. Note that this is part of the improvements mentioned here so that you don’t have to always expand batches to work with them (viewtopic.php?f=206&t=12891). In 7.1, most of the columns are now populated with data to make them easier to work with. If there is a single job, then pretty much all the columns of the batch row match it’s child. If there are multiple children, the batch row will show a value if they’re the same across jobs, or if they’re not the same (there will be exceptions in the case of numeric values, in which case the highest of the values is shown).
By having all the single job’s properties showing up in the batch row, they shouldn’t have to expand it any more, correct? So you don’t need an option to disable batch rows for single jobs.
Lets see how it is in action. To me, it still sounds redundant, since you have 2 entries visible for the exact same job (with 15k+ jobs, any additional entry listed just adds to the noise).