AWS Thinkbox Discussion Forums

monitor, autodocking

Is there a way to turn off autodocking? If i open a job event log, and just move its window around, it instantly docks to whatever is behind it.

In beta 11, we’ll be adding a new “Lock Panels” option to the View menu and the tool bar. When locked, you will not be able to move or dock the panels. This will prevent floating windows from trying to dock when you move them over the main window.

You’ll still be able to close the panels, and you’ll still be able to float them. You’ll also still be able to double-click the title bar for a floating window to attach it back to its original location in the Monitor.

Cheers,

  • Ryan

Thats Ryan, do you have an ETA for beta11?

Also, i wanted to ask when self-updating of the clients is expected to be added?
We would like to roll out deadline 6 on a couple hundred machines, but i noticed in another thread that this feature is still missing. We would most likely need to hold off on the rollout till that feature is added.

cheers,
laszlo

A rough estimate for beta 11 would be later next week. Most of the major stuff was wrapped up with beta 10, so with only smaller stuff remaining, we can probably start pushing out betas once a week.

We will probably start looking at the auto-updating after beta 11 goes out. Basically, we want to make sure that we’re set with the current Qt and Python libraries, since those aren’t included in the auto-updating. As long as nothing comes up, we will be sticking with the libraries that went out with beta 10. We just want to give it a couple of weeks with people testing it to make sure there aren’t any issues.

Cheers,

  • Ryan

Cool, thanks for the update!

So would you say that its probably a good idea to keep farm rollout of beta 10/11 to a smaller scale, and prepare for a mid february full rollout?

Yeah, that’s probably a good idea, especially if you’re waiting for the auto-updating.

Cheers,

  • Ryan

Its more that i dont think we can roll it out on 500 boxes and then do repeated reinstalls. Its just not very manageable.

Sort of off-topic, but if you’re ever looking at having to manage that many machines, you should really consider a generalized deployment/image management system (Puppet, etc.) if you don’t already have one available.

That’s out of my hands, there is an IT department that handles all that. Im sure they have their tools, but whenever there is a manual rollout, machines are missed (boxes that are offline due to maintenance, etc)

Privacy | Site terms | Cookie preferences