[posted to rush.general]
> Typically, we really don't care about the task level as we just want to
> move the entire job up or down in the priority list. Ultimately, we want
> to build something where we can affect priority at the
project/shot/scene/user
> levels. We're not expecting you to handle this but we need a clean way to
> identify these jobs with our own tools and then be able to apply blanket
changes.
> I think I can at least show the priority values in a user selectable
> field when I finish implementing the 'rush -lj -fmt FieldName[width]
Fieldname[width]',
> where one of the fieldnames would be 'Priority', which would show
all the priorities
> concatenated, eg:
>
> +any=4@999,+any=10@1
>
> At very least with that, you could highlight the job, and enter a
new
> priority value, or at very least supply a way so you can program a
hotkey
> that runs your own script to prompt the user for a new priority
value
> that you can apply in any way you want.
I think it would be great to see priorities in the jobs report. We too find
it more useful to change an entire jobs priority and if that could be done
from the jobs page all the better. We rarely use individual cpu priorities
and this would make managing many jobs a lot easier for us, we could sort
jobs by user/title and then select multiple jobs and assign a new priority
in one hit. Some of the guys here have custom scripts to do this using jobs
selected from the jobs report and firing off another perl script as you
suggest, but having the priority changeable from the jobs page gets a thumbs
up from me.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|