Mentioning this only because it tends to become an issue with the possibility of opening many panes, grids, panes in tabs, etc.

GDI Objects tend to really accumulate and never get released, and this slows down IQ over time. Passed 5000 (and this is a lot, by any standard, I think), IQ starts to get pretty sluggish.

Then, even if I close all panes, grids and tabs, GDI will remain at more than 3500 and never gets below, for some reason. Seems to be related to icons (see below**). By contrast, if IQ is freshly loaded, with one tab (and a few unopen tabs) it takes 1980 GDI.

So to get rid of GDI objects and regain responsiveness, one needs to close IQ and reopen it.
That might explain why, sometimes, IQ gets less responsive over time.

As the title says. 

Obviously, sort is set to apply to sub items.(Work around : play with the sort columns/fields, and the sort will apply to displayed subs)

 If you need specific steps, please ask.

Not sure how to reproduce this, but if  in the main workspace I load only 2 tabs with panes inside, one of the two tabs will work properly (usually the first loaded one), but the other tab with panes inside won't be recognized by the rest of the interface. looses shortcut ability, context menus, etc.
 

Quick screenshots.

First tab with panes behaves normally. Focus is in grid and the main toolbar (File, Edit, ...) appears normally.

 

Second one doesn't. Focus is in in grid, but the main toolbar at the top (File, edit, View, Tools) appear as if the focus isn't in a grid, or if IQ had just loaded, with no grids.

 The "Load column set" feature conflicts with column grouping and so loading a column set usually results in a mess here.

It's hard to use & unfriendly/unintuitive when all columns are mixed, half grouped, etc.

The result is that I don't use the feature, but I'd really like to. 

Suggestion: could the loaded column set be exactly the same one as the one from the original grid they're loaded from?

I'd use it a lot more if that's what it was doing, instead of constantly adding and removing fields to the scratch/search and other grids.

I think it would make more sense and be more useful. (And -- why not -- there could be this extra option to merge column sets.)

Personally, I think that the Hoisting process can be simplified if another command is added or the existing one "Hoist Selected Items" is expanded to check if there is hoist going on to turn it off when invoked.

 

It will bypass the need to go through the Hoist Dialog.

As it currently stands - I can assign shortcut to "Hoist Selected Items", but I need a different shortcut for the toggle of the Hoist Filter.

- focus is on a grid in a pane *outside* the main workspace

- if a popup is triggered in IQ and then closed, the focus first comes back to the main workspace and  "slowly" switches back to the pane(s).  

(like I said, I'm talking about panes NOT in tabs, outside the main tab workspace) 

 

The result is that the focus sometimes doesn't fully come back to panes when I start typing -- it's pretty slow... 

And then I'll type/modify some item I don't see, in the main workspace.

 

The workaround is to wait longer, each and everytime. I've seem a few cases where the focus never came back to the panes or came back to some other pane. Not sure why. Maybe a mistake on my part -- will keep my eyes open...

Each time I create a new item, the focus goes to the HTML Pane. Likewise moving to a new item.

 

Using 88c.

 

I had noticed in earlier versions of 88 that focus was sometimes going to HTML Pane when it shouldn't do - eg focus was on grid, I'd press down arrow, instead of going to next item it shifted focus to the HTML Pane.

 

Now it seems like it's doing it all the time.

 

DavidF.

 

-- I'd add that it seems a lot worse in some databases than in others. But at some point, navigating through items, focus will always jump to the Pane. It is also always particular items that do it. Other than the fact of having something in the HTML Pane, I can't see any common factor.

 - Select item

- Ctrl+B : takes more than a minute here to apply bold to the item and one CPU core is maxed out.