if i right click and hit disable slave, and want to enable it agian, i have to right click on the slave and hit “disable slave” a second time. have to hit disable button to turn back on. not a big deal and im sure people will figure it out, just fyi i guess 
It’s a toggle option, which is why the text doesn’t change (ie: untoggle the “Disable Slave” option to enable it). It was that way in v5 so we didn’t put much thought into it when we brought it into v6.
Maybe we could do away with the toggle option and instead have it change the text to suit the context…
Cheers,
- Ryan
oh, so it is! didnt notice the graphic change somehow. thanks!
also, it seems like often times, even after i disable a slave, it still gets queued and gets put to work rendering
Disabling a slave only prevents it from starting up. If it’s already running, it will continue to pick up jobs. Just to confirm, when you disable the slave, do you click the “Stop Slaves” option?
aah, i see, that makes sense. sorry about that! youre totally right, I should have tested a bit more before yelling wolf.
ok this time i think this is a real thing:
sometimes the right click menu color changes to this, which is a bit hard to read. it happened before in deadline 6 beta version 5 as well. (could have something to do with switching monitor resolution and not restarting possibly?)
and, as circled in the image below, in the “status” column, where the number of nodes working on a job are shown in parentheses, it seems like if priority gets shifted mid job, the slaves do exactly what they should, but the UI gets stuck or something, showing the number of slaves that there were maybe.
also, possibly the least important thing ever, but since the rest of the UI is so slick thought id mention: the alt tab logo for deadline submission is super pixely (attached)
The menus turning white is a known bug. It’s currently on the todo list for 6.1.
The fuzzy icon occurs because the application icons for the Deadline plugins are only 16x16. The only time this becomes an issue is when the Monitor scripts use them, since they get used to represent the window in the task bar. We’ll probably look at scaling these up at some point.
The next time a job goes out of sync like this, can you try restarting the Monitor to see if that “fixes” things? Someone else has reported a similar problem, and we’re trying to determine if the issue is on the database or Monitor end. If restarting the Monitor fixes it, that means it’s on the Monitor end.
Thanks!
- Ryan
For us, restarting the monitor fixes these oddities (task list and job list not showing the same thing)