Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • March 30, 2010 at 11:09 am in reply to: Feature Request: Remove The "info Bar" #30606
    iliask
    Member

    Usually, query error messages show in tab 1 “Result” (In version 8.22 that I use). Errors on that big tab always displayed nicely in many lines, and not squeezed into a line. I am not sure about the others, but that info bar is utterly distracting to me – to the point of not updating the application to avoid it.

    Thanks

    Ilias

    January 16, 2009 at 5:09 pm in reply to: #28160
    iliask
    Member

    Hi,

    Thanks for that and sorry for coming accross a bit too aggressive. If you run multiple queries it would make sense to have the infobar on, but for single queries it was more of a distraction.

    Ilias

    January 9, 2009 at 5:21 pm in reply to: #28157
    iliask
    Member

    Hi,

    It is clutter, as it provides duplicate informational already present in the system, and clutter is not an impolite world. Please understand that for a paying customer who was on the previous version for quite a while this a feature which just takes screen space – very annoying on small screen laptops that I happen to use. Had I known this I would not have paid for the upgrade. To me, separate important queries can be executed on different tabs and those who want more control should enable the bar from an option in preferences.

    When you spend so much of your time on a product like this even the slightest visual changes you make will matter to the users.

    October 13, 2005 at 8:54 am in reply to: Feature Req: Sql Template #19339
    iliask
    Member

    You mean that by accidentaly double clicking on a table with international characters you might get unreadable symbols on your editor?I guess then that a ALT+ shortcut would do fine…

    October 13, 2005 at 8:25 am in reply to: Feature Req: Sql Template #19337
    iliask
    Member

    How about pasting the SELECT statement after the user has double-clicked on the table? That would be more usefull compared to just placing the table name…

    October 11, 2005 at 1:53 pm in reply to: Feature Req: Sql Template #19336
    iliask
    Member

    Sorry hadn't notice that menu. A shortcut would be great… 😀

    October 11, 2005 at 9:09 am in reply to: Feature Req: Sql Template #19334
    iliask
    Member

    Exactly. That was the default behaviour of version 4.1 and was proven to be quite handy. For the time being i have to locate the last entry on the history pane and then manually copy-paste it to the sql pane. Most of the times you have to manually edit the where clause of the sql to get a different output on the Table Data pane and having the sql ready helps a lot.

    October 6, 2005 at 1:07 pm in reply to: Feature Req: Sql Template #19332
    iliask
    Member

    Tested 4.2B5 but all i could get was the database name every time i pressed enter on one of the tables, which is not much usefull. The SELECT * FROM table LIMIT 0,maxRows would be far better. A “Paste quick SELECT in editor on double click” on the preferences menu would allow people to swich it off.

    October 12, 2004 at 1:20 pm in reply to: Sorting Data #13712
    iliask
    Member

    The code which sorts the grid within SQLyog is doing fine as long as there is a lot of different values in the column you clicked. Otherwise it takes ages for more than 5000 rows. Ever thought of experimenting with different sorting algorithms?

  • Author
    Posts
Viewing 9 posts - 1 through 9 (of 9 total)