When using IQ once the user has entered enough items to fill the page you use scroll bars to get to the bottom item (as with any program).  But the last item shows up literally at the very bottom of the page.  This is very disconcerting from a user interface point of view.  Now every time the user enters a new item the page is jumping up one cell at a time and you feel like you've run out of space.  It's also not comfortable always having to do all your typing at the very bottom of the screen, which is how every grid operates as soon as you've entered a fair number of things in it.

 

Pierre, please consider adjusting the grid (and HTML pane) so you can keep scrolling so that at a minimum the last line is appearing in the middle of the page.  SOP is just about any program that allows row/column type entries or outlining, as it's natural for the user to want to be typing in the middle of the page.

 

Not to be

I am having fun as I am figuring out IQ again but still need some help :D.

 

1. The title says it all.  I'd like to create one grid that shows all items in it, including the TLI.  I'd like a second grid that shows all the items in the first grid, EXCEPT for the very TOP TLI.

 

2. In the grid that shows the TLI, would there be a way for the TLI to be bolded ONLY if it has an active (not done) task beneath it?

 

Thanks

Is it possible to create two text columns and have the values of the first column affect the values that are available for the second column?  For example:

 

Column 1 Selections:

Learning

Inventory

 

Column 2 Selections:

If Learning was selected on Column 1

- Books

- Internet Resources

If Inventory was selected on Column 1

- Books

- Music

 

Thanks

IIRC one of the limitations of Ecco was that when an item showed up in a different folder than its parent you could not tell what TLI it was assigned to.  IQ does not have that limitation.  However there are many times I don't want the TLI to show up in a particular grid, just the single item.  Where do I set that in a grid?  I've tried various settings under Manage Grids>View with no luck.  Also looked through documentation with no luck.

 

Example, I want to create a grid called "high priority tasks".  I don't want to see TLI, I ONLY want to see items checked as "high priority tasks".

 

Thanks

I note with interest and approval something really good coming up in release 35:

New: WYSIWYG Print Preview: Option to save as a file in PDF, JPG, PNG or EMF format

This will be invaluable to me as I complete my PhD thesis. Since I have made extensive use of InfoQube, I need to be able to get data out of IQ and into Microsoft Word – the software in which I am writing my thesis.

My thesis concerns the personal information management system that underlies the personal working model which each and every one of us possesses – even though for nearly all of us that model is anything but explicit. I expose just a little bit of my thinking in the website www.markrogergregory.net.

I'm still getting my feet wet so I'm making some assumptions with this post that might be incorrect, if so you can correct me.  Let's suppose I want to create two grids, one for professional projects and one for personal projects.  This is just one example, this question could apply to many similar scenarios.  I'm assuming I could:

 

In other words, do I use only one projects field, and use other attributes to decide the type of project, or just create multiple projects fields.  Is there any reason to prefer one approach to the

Is there any reason to limit the number of items in a grid?  Since there is no way to nicely categorize or group grids in IQ, I am going to try to limit the number of grids that I use.  This would mean for instance, using a single grid for all projects, past (done and filtered out) and present, so there would be tons of items.

 

Thanks

I am about to give IQ another twirl.  I have some memory of it from when I used it several years ago so i should catch up pretty quick.  Like most users, I'll be customizing it heavily to my needs.  It'd be nice to start out with some sample data just because it also includes some grids to get started with.  On the other hand, if I start to use those, do they contain a lot of settings that I'll ultimately have to dig through and adjust/delete etc.?  Any reason not to start with the default grids, or should I just start fresh even though it'll mean more time before I can use it.

 

Thanks for your thoughts.