Custom layouts saved for the user | Voters

D-Tools System Integrator

Create

Roadmap

Feature Requests

1041

Custom layouts saved for the user

complete

Stephen Michaux

I use multiple computers to access D-Tools. It is frustrating to have to rebuild the custom layouts every time I log in on a different terminal. The layouts should be persistent for each user and not only dedicated to a single computer.

March 31, 2020

Stephen Michaux

Well done!

Seth

marked this post as

complete

Completed in v14. Each Custom Layout has a "Share with all users" option.

David Riberi

@Seth: Excellent! Any chance the same could be done with reports so people don't have scads of reports that are no longer current or should be hidden in archived folders? Thanks!

Naresh Nichani

marked this post as

in progress

Naresh Nichani

marked this post as

planned

We are adding ability to share custom layouts in V14

Cody Frisch

I will add if you want to copy them manually they are located at the following location:
C:\Users\USERNAME\AppData\Roaming\D-Tools\SIX\Data\Grid Layouts
You can also copy a GridLayout section out of one file and into another - so this is a poor mans way of getting a layout to another user.

Cody Frisch

Add my vote, maybe a Layout Library we can publish layouts to. With scoping for global, roles, and per user. These would then be selectable from the layout manager, pull from server and configure. 
There cannot be much data to a layout... list of columns and their widths.
With that, it could also include the panes locations etc.

hope shild

I agree! Having the ability to also share custom layouts to all my users so that as I come up with layouts I think would be most useful, they can just utilize them without every individual having to create the layout themselves.

Doug Melaas

Absolutely! +1000 up-votes. If there was a way we could create layouts and attach them to user profiles that would then push out to the users when they log onto the system (from whatever machine) that would save, literally, hundreds of hours a year.
Simplest example I can think of: 
PC #1 - I have my computer at my desk in the office, it is highly customized because that is where I do most of my work. I have lots of custom layouts and everything is the way I like it.
PC #2 - I have to go work through some of the project I'm working on in the conference room. I have to log into the conference room PC (because I don't use a laptop). That means that I need to have recreated those layouts on this computer. Any changes I make on one computer is not reflected in the other.
PC #3 - NOW, since we're working from home, add a third computer. I spent the better part of day, split-screen. Duplicating settings from my remote-desktop connected computer, screenshot the settings for a layout), log into my account on my local machine, set up that layout. Log out. Go back to remote desktop connection, log in to remote machine connection, get the next screenshot... on and on.
Hundreds of wasted hours, if you figure that everybody in the company is probably trying to do something along the same lines.

Shawn Lemay

We should also be able to push layouts to other users

Eric Kalpakoff

Agreed, this should be a server saved setting that is also exportable to other users so everyone could have the ability to use a common layout as well.

→