Start a new topic

Current object view

[This topic is migrated from our old forums. The original author name has been removed]

Hi, I think the new approach to tabs and windows is a step in the right direction. And it is great that the edit windows reappear when you restart dbvis! It does, however, take a bit longer when you want to first locate the information you are interested in. You may have to open and close a few tabs before finding what you are really after. One way to deal with this would be to have a "Currently selected object window". When you click on a node this window would show the current object. Then I could double click or select open if I want to keep the window easily accessible. Maybe there are other better solutions than this that you can come up with - but I thought I would mention it anyway! Regards Bengt

[This reply is migrated from our old forums.]

Re: Current object view
Hi, The 9.0.3 version has just been released with support to configure what Open action to run for Double-Click and Alt+Double-Click of database objects. http://www.dbvis.com/download/ Regards Roger
[This reply is migrated from our old forums.]

Re: Current object view
Vince, I will register a ticket for supporting modifier+double-click. Regards Roger
[This reply is migrated from our old forums. The original author name has been removed]

Re: Current object view
Hi Roger, I think this is too personal a choice to impose it upon users without some form of customisation available. I suggest that the preferences be altered so that users can choose what actions are performed by double-clicking an object and by double-clicking an object with a modifier key (I would suggest Alt) pressed. The Appearance>Tabs section seems to be a logical place for this. This way, the defaults could remain as they are in 90.1866, which is a sensible compromise for existing users, however those who wish to use extra tabs can choose to do so. Neither the dropdown nor the shortcuts address this issue as both require the user to hunt around either in the user interface or the keyboard to perform what should be a simple task. A modifier key would allow users the ability to quickly perform this task and extra preferences would enable users to specify exactly which behaviour they prefer. Regards, Vince
[This reply is migrated from our old forums. The original author name has been removed]

Re: Current object view
The new behavior (while different than 8.x) is better than earlier 9.x versions (tab explosion during browse is under control). Thanks
[This reply is migrated from our old forums.]

Re: Current object view
Hi, It seems that personal preferences play a big deal here. Some think that minimizing number of clicks is a great improvement while shortening mouse movement is great for others (independent of clicks). We will try consolidate all comments and come up with something that attracts the majority of users. I am sure you are aware of the associated key bindings but take the opportunity to mention them as they may improve working even further. - Open in Tab (Ctrl+L) - Open in New Tab (Ctrl+Alt+L) Regards Roger
[This reply is migrated from our old forums. The original author name has been removed]
[Attachment has been removed.]

Re: Current object view
Frankly speaking I never use this button and I can tell why. If I use only mouse, without keys, I should do next steps for opening code of a function/procedure in New Tab with this button: 1. Move mouse to the proper function/procedure in the object tree. 2. Click on it with left button. 3. Move mouse to the button on the databases tab toolbar. 4. Click on it.... Even you change this button to the "Open in New Tab", this way is toooooo long because of step 3. That's why now I do this: 1. Move mouse to the proper function/procedure in the object tree. 2. Click on it with left button. 3. Click on it with right button. 4. Select the menu item Open Object, wait until the submenu open (or click on it with left mouse button), 5. Select 'Open In New Tab' which is the second in the submenu. 6. Click on it with left button. See screenshort 1. The second path is much faster, because I don't need move mouse to the databases tab toolbar. That's why I propose the next path: 1. Move mouse to the proper function/procedure in the object tree. 2. Click on it with left button. 3. Click on it with right button (the context menu is shown). 4. Select in the context menu the first item 'Open In New Tab' (need make it the first) 5. Click on it with left button. This way is rather faster than the second and greatly faster than the first, with the button in the toolbar. The analog is Internet Browser, see screenshort 2. Edited by: Evg on Nov 23, 2012 9:49 AM
[This reply is migrated from our old forums.]
[Attachment has been removed.]

Re: Current object view
Hi, In the databases tab toolbar (and in the main toolbar) there is a two purpose button. Clicking the icon will currently "Open in Tab" for the selection. Click the drop-down arrow to select which of "Open in Tab" or "Open in New Tab" to run. One possible improvement is that the icon part of the button will run the last used Open command rather than always "Open in Tab". By this you would select "Open in New Tab" from the drop-down and the next time you just click the icon to "Open in New Tab". (The icon should change accordingly to show what action will be run). By this change you only need to single-click a button. What do you think? The screenshot show the button I am referring too. Regards Roger
[This reply is migrated from our old forums. The original author name has been removed]

Re: Current object view
A small suggestion. Now to open a function or procedure in a new tab, we must click on the right mouse button and then select the menu item Open Object, wait until the submenu open, and then select 'Open In New Tab' which is the second in the submenu. It's too long. I propose to move item 'Open In New Tab' in the main menu and make it the first in it. This will speed up opening in a new tab noticeably. Thank you.
[This reply is migrated from our old forums.]

Re: Current object view
Bengt, > However, I still think the interface could be made simpler. Compare with the Windows explorer on Windows 7. If I press on a directory node with the mouse in the tree, the corresponding content of the directory is shown. If I, on the other hand, move around in the tree with the arrow keys no updates are made. This allows me to move to the node I am interested in without a lot of flickering and slowdown taking place. When I reach the node I am interested in I press return. This means they treat mouse click as a combination of select/open, while a an arrow move is select only, and return is open. File Explorer only shows directories in the tree (no files) and they don't support multiple selections. And there is only one pane (at the right) showing folder/file meta data. Imagine if files were also displayed in the explorer tree and the consequence of letting select also imply open. DbVisualizer supports multiple selections and multiple object view tabs whereas a tab maybe in an unavailable state (edited, busy, etc). All operations that can be performed on an object are launched from the objects tree whereas opening an object is one operation. > I think dbvis would benefit from a similar scheme. I would be able to accomplish the task with a single click rather than double-clicking. With the current implementation clicking a node with the mouse does not serve any real purpose. The purpose with single-click is to only select the object(s) you are interested in and then activate the appropriate action on it such as open, launch action, drag&drop, etc. If you double-click you make an active choice to open an object. Open isn't something that should happen implicitly by just selecting in the tree. > My guess is that this will also translate into better behavior when using touch-sensitive screens. We will most certainly need to look into reviewing most of the UI once touch screens gain in popularity. > For new users this is an easier way to learn what is behind each node in an easy and very intuitive manner. I would rather say that it may be a short adoption phase for existing users getting used to the updated UI in general. As always we carefully monitor and collect all response and act from there. Regards Roger
[This reply is migrated from our old forums. The original author name has been removed]

Re: Current object view
Hi, I think that the latest beta behaves much better than the previous one! Now you do not have to close a lot of tabs when moving around the window. However, I still think the interface could be made simpler. Compare with the Windows explorer on Windows 7. If I press on a directory node with the mouse in the tree, the corresponding content of the directory is shown. If I, on the other hand, move around in the tree with the arrow keys no updates are made. This allows me to move to the node I am interested in without a lot of flickering and slowdown taking place. When I reach the node I am interested in I press return. This means they treat mouse click as a combination of select/open, while a an arrow move is select only, and return is open. I think dbvis would benefit from a similar scheme. I would be able to accomplish the task with a single click rather than double-clicking. With the current implementation clicking a node with the mouse does not serve any real purpose. My guess is that this will also translate into better behavior when using touch-sensitive screens. For new users this is an easier way to learn what is behind each node in an easy and very intuitive manner. I cannot judge if this suggestion fits in well or not on other platforms, and from your (Roger) reasoning earlier that may be a problem. On the Windows platform I believe this behavior is consistent and very easy to use! Regards Bengt
[This reply is migrated from our old forums.]

Re: Current object view
David, Thanks for coming back to us confirming these changes. It has taken some time getting were we are but we're now quite confident with 9.0 and how it deal with the new functionality, yet keeping the basic behavior similar for existing users. We're overwhelmed with the response during this beta testing and the feedback has been amazing and very constructive. Thanks again! Best Regards Roger
[This reply is migrated from our old forums. The original author name has been removed]

Re: Current object view
I just installed 90.1866 and like the changes to the tab handling. The ability to browse objects in the database without getting lost in a sea of open tabs or having to drag objects to a target tab is a great improvement. This model seems much more intuitive and retains the benefit of being able to work with multiple objects at once. Amazing how quickly you were able to implement this change. This was the last major issue in DbVis 9 that made me think twice about upgrading our licenses. Overall a fantastic job! Regards, David
[This reply is migrated from our old forums.]

Re: Current object view
Hi, We feel that consistency and simplicity are more important than backwards compatibility in this case: single-click means "select", double-click means "open in tab", in all cases, no exceptions. Using single-click to "open" is common in user interfaces where only a single object can be selected, as it used to be in DbVisualizer. Now when multiple selections are allowed, it is no longer obvious that this is the best behavior since a single-click then means different things depending on if it selects the first object or extends a selection. Compare, for instance, to file browsers. The tree view is often single-selection and shows the content of the selected folder to the right. In the folder content list to the right, however, multiple selections are allowed and single-click means just "select." We don't believe the main issue reported so far on this topic is related to double-click vs single-click but rather that tabs seem to be opened "uncontrolled". The strategy has been that opening an object not already visible should open it in a new tab. Compared to previous versions this seem to be a big difference since then only a single object view tab was available. Based on the feedback this new behavior may be a little too flexible for existing users. In the just released beta we have made a few changes so that opening an object first will try to re-use a "free" object view tab. The standard behavior if only needing a single object view tab will then be similar to pre-9.0 versions (except that double-click is used). In addition will the user have the option to open multiple objects and show them in separate tabs. If then double-click, DbVisualizer will re-use the first available tab (which is searched starting at the current tab) or open a new if no free tabs are available. The result of this is that as long as the user is satisfied with a single tab it will be re-used over and over again and this will then mimic the old behavior quite well. Please give the new beta a try: http://www.dbvis.com/download/beta/ Regards Roger
[This reply is migrated from our old forums. The original author name has been removed]

Re: Current object view
I also agree that this single click to static tab and double click to new tab seems very intuitive after years of using DBVis. Thanks, Shaun
[This reply is migrated from our old forums. The original author name has been removed]

Re: Current object view
I feel that your suggestion is still too difficult for new users. It would be fine for advanced users. I suggest the following instead: Single click always displays the object in a dedicated window that is reused as soon as anything else is single-clicked (if the window does not exist it is created. The window may be explicitly closed by the user). Double click opens a new window as in the current beta. This window remains until it is explicitly closed. Regards Bengt