1. I can not find any way to scroll up or down the grid while editing the text of a grid item without abandoning the current cursor position in the editor. If I use the mouse wheel or scroll bar, edit mode is cancelled entirely and I have to re-enter edit mode with the cursor re-appearing at the very beginning of the item text. On the other hand, if I use the cursor keys to move to the top or bottom of the text of the item I'm currently editing to get IQ to scroll there, I obviously have to manually move the cursor back to the position I was going to edit before scrolling. Also, Ctrl-Up and Ctrl-Down do not work here as they have different functions in edit mode. Most users may not notice this annoyance much, but I use large font sizes (see below) so it is often necessary to scroll while editing to see the preceding / following text inside the item.

 

The other aspect requires a bit of a rant, sorry:

 

2. I dislike how scrolling in IQ is (at some point) on a per-item rather than a per-line basis. I use largish font sizes and Windows settings to increase the size of UI elements, hence even though IQ limits the displayed area per grid item to around 2000 characters (I think), I have items in grids that cover slightly more than the entire screen height while scrolling. When I scroll grids with large items like that, the process is very choppy because when I reach the bottom of such a 'high' item, it disappears at once rather than sliding a couple of lines further up the screen. So before the crucial tick of the scroll wheel, my whole screen is filled with the item, after the tick, the item has completely disappeared above the current view and my reading of it is disrupted.

 

I accept that this may be a conscious design decision and that some users may like it that way though it boggles my brain.

 

However, I was able to work around this by using a tool called Autohotkey to send what I think is called the "VScroll" message (postmessage 0x0115, a Windows relic from before there were scroll wheels, I guess) to InfoQube instead of mouse wheel events. This works fine for the down scroll direction, and I can scroll down line by line without any of the choppiness - very sweet. The problem is, this does not work for the upward direction for some reason. After using vscroll to scroll, down, IQ will scroll up a single line when sending vscroll up messages, but will scroll up no further than that. Hence, I'm currently stuck with my nice slow scrolling speed going down but have to use IQ's native scrolling when going up, which is much faster and has the choppiness. The result is confusing to say the least.

 

Bottom line: Pierre, would it be possible to have a native option in IQ to make scrolling entirely line-based? If that's not something you want to tackle, maybe there is an easy fix to vscroll up not working?

 

Sorry if it seems I'm nagging you about my problems with scrolling, but the whole vscroll thing is new so I posted it here rather than send you another e-mail.