Community forum

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


Guest
2018-11-26T15:36:26Z
When editing jobs/tasks, the only window that you can interact with is the deepest level of the job/task that you have open. This makes sense for job and task windows, but would it be possible to stop these windows from making existing instances of non job/task specific windows (such as Server Tools and Global Objects) untouchable? This functionality often gets in the way of using the connection explorer, and the variables window when jumping between tasks, as opening a task after opening the variable explorer. Currently, if you wanted to access the variable explorer in this situation, you would have to open a new instance of the variable explorer and lose what you had in the previous instance. I believe it would be much more convenient if windows that were not job/task specific were independent of the window hierarchy that currently exists.
Sponsor
Forum information
Scroll to Top