problems with the new DataGrid tab

[expired user #1821]'s profile image [expired user #1821] posted 15 years ago in General Permalink
I'm having some issues with the new datagrid (using revision 1850)

[list:0db3d78c89]what happened to the LIMIT option? I can't seem to find it anymore. I checked the preferences and all that, but it seems to have completely disappeared.[/list:u:0db3d78c89]
[list:0db3d78c89]how do i clear a filter? if i apply a filter, the filter-section on the top appears and my filter is also shown. When i clear the filter and hit Refresh, the filter reappears again. Whatever i try: i can't get rid of it. Right now, the only sollution for me is to open an older version of Heidi and remove it there.[/list:u:0db3d78c89]
[list:0db3d78c89]it used to be very easy to quickly add some rows with data in heidi. i could just tab to next field, start typing and hit tab again to edit the next field. I've been using revision 1850 for two weeks now but i'm still not used to the new way of editing: having to hit enter first, then type and then enter again. even more frustrating is the fact that the 'cursor' moves to the top of the screen whenever i forget to hit enter first, but start typing right away. It would be very much appreciated if this enter-thing could be switched of in the preferences
[/list:u:0db3d78c89]

If some of these things are considered bugs let me know and i will file a bug report for them
ansgar's profile image ansgar posted 15 years ago Permalink
r1850 is not the current revision, you should upgrade and see at least the filter bug was fixed.

For that focus moving while typing, I agree, that should somehow be solved. Feel free to use the tracker to report it.
ansgar's profile image ansgar posted 15 years ago Permalink
The LIMIT option was optimized away, not needed any more. The data grid always let's you scroll through the whole table. Row chunks are loaded on demand while you're scrolling. That's not a bug, it's a great new feature, isn't it? Don't care about limiting anymore.
[expired user #1821]'s profile image [expired user #1821] posted 15 years ago Permalink

The LIMIT option was optimized away, not needed any more. The data grid always let's you scroll through the whole table. Row chunks are loaded on demand while you're scrolling. That's not a bug, it's a great new feature, isn't it? Don't care about limiting anymore.



Yes, that works fine in most cases, but not all. I sometimes deal with tables that have large chunks of information in BLOB fields which makes loading the data extremely slow. I miss being able to set the limit to, for example 10 and give an offset.

For that focus moving while typing, I agree, that should somehow be solved. Feel free to use the tracker to report it.



This seems to be solved.
However, i would still very much like an option with which i could switch back to the old way of entering data. It was so much easier when i could just hit the TAB key and start typing, instead of having to give ENTERs all the time.

Btw, In revision 1850, i sometimes got popups when i wanted to edit a varchar or text field, which would allow me to insert a newline (by hitting ENTER). This doesn't happen anymore in my current revision (2026).
Although these popup windows were annoying the hell out of me most of the time (since it would take so many actions to enter a simple value in a field), it would be nice if it was still available through a certain key-action (CTRL+ENTER for example), because in some cases it can also be handy
ansgar's profile image ansgar posted 15 years ago Permalink
All popup editors can be disabled via preferences. For text fields (varchar, text, longtext ...) we now don't popup the text editor at all but do it inline again, having a button which calls the popup window if needed.

And tabbing through fields while in editor mode is also possible now, at least for text and numeric fields.

See rfe #829 for details if of any interest.
[expired user #1821]'s profile image [expired user #1821] posted 15 years ago Permalink
You made someone very happy anse :)

* points at himself

Unfortunately it introduced a bug, which i have reported here:
http://code.google.com/p/heidisql/issues/detail?id=889

Great work though!

Please login to leave a reply, or register at first.