forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Usability
- This topic is empty.
-
AuthorPosts
-
-
November 10, 2004 at 6:08 pm #8650wagMember
We have been using the sql yog tool for some months. I haven't had a chance to look at the 4.0 versions so maybe some comments are out of date. Generally the program is easy to use, however there are some serious usability snags.
– The grids are a bit difficult in sizing the column widths at the right of the grid. Almost impossible for the last columns in fact.
– Blob fields are rendered much too wide in the update grid. A small button would suffice.
– If you tab across a very wide blob field in the update grid you lose all visual cues as to which is your activecell
– It is frequently impossible to reach some columns at the right end in the update grid by means of the scroll bar if you have wide fields in front.
– The width of the scroll buttons in the update grid doesn't size properly with the amount of content out of view
– The structure synchronization doesn't take reference information into account (not a usability issue)
– A right click on a database table doesn't update the active database dropdown even if you view the table data which is confusing
– There is no keyboard shortcut for viewing the data in the currently selected table
– If you have multiple decimal columns in the view as well as update grids you get the decimals setting of one column on the other columns as well
Please let me know if any of these have already been addressed in the 4.0 versions. Keep up the good work. 🙂
Monk
-
November 11, 2004 at 3:44 am #16533RiteshMemberQuote:The grids are a bit difficult in sizing the column widths at the right of the grid. Almost impossible for the last columns in fact.
Blob fields are rendered much too wide in the update grid. A small button would suffice.
If you tab across a very wide blob field in the update grid you lose all visual cues as to which is your activecell
It is frequently impossible to reach some columns at the right end in the update grid by means of the scroll bar if you have wide fields in front.
The width of the scroll buttons in the update grid doesn't size properly with the amount of content out of view
We have improved the functionality of grid (specially the width issues) in 4.0. Please download SQLyog 4.0 from http://www.webyog.com/sqlyog/download.html.
Also make sure that you have unchecked Truncate column headers to max data size… option in Tools->Preferences
Quote:The structure synchronization doesn't take reference information into account (not a usability issue)This feature is in the TO-DO list of SQLyog.
Quote:A right click on a database table doesn't update the active database dropdown even if you view the table data which is confusingWe will fix this issue in one of next minor upgrades of SQLyog.
Quote:There is no keyboard shortcut for viewing the data in the currently selected tableF11 or press Enter while the focus is on the Object Browser.
Quote:If you have multiple decimal columns in the view as well as update grids you get the decimals setting of one column on the other columns as wellI am not sure I understood your problem. Can you explain it a little more?
-
November 15, 2004 at 10:51 am #16534wagMember
Hello,
Thanks for the informative reply.
Unchecking Truncate column headers to max data size is a great help in grids with a blob although a bit against intuition and pressing enter to view data is good to know about.
I haven't been able to reproduce my problem with the decimal view. It appears in one table in one database where one column shows 4 decimals while its setting is 2 and that of the column next to it is 4. Copying the table in the same database shows the same behaviour but copying it to another database gets rid of the extra decimals. Strange but not of immediate importance.
Greetings
-
November 15, 2004 at 5:17 pm #16535RiteshMember
I am still unable to understand the decimal problem. Maybe you can upload a pic to describe it.
-
November 16, 2004 at 11:39 am #16536wagMember
Hello Ritesh
I have found that the incorrect number of decimals behind the decimal separator probably is caused by mysql. I had truncated the column to have less decimals behind the separator earlier. But somehow the internal representation is only updated when you edit the values. When I edit the values the false decimals drop off and I even see two different decimal representations in the same column!
Greets
-
-
AuthorPosts
- You must be logged in to reply to this topic.