Default settings

Submitted by Al on 2014/02/04 13:43
Would it be fairly quick to add a check box to always automatically select the "Open and Restore Last Session" on start up, no manual selection?
Also can an option be added to always leave the Properties windows menus in last state, I like to always have the Contact pane open. Currently I have to open it every time I open IQ. Ideally I would like to individually choose the state for each property pane section, "Always Close" or "Open as in Last Session".

Default not working

Submitted by lucky_phil on 2014/02/03 21:23
 I have a DB, that I derived from the Sample, and have been using for some time, and some functionality, like Default for a date field being =int(now()) simply does not work any more. I cannot find any way to find out why???
 
I have confirmed that this does work as per the documentation in a new file, so would appear to relate to something I have done in mine, but how does one find out what the problem is? No errors, no debugging. Sorry, when I say that, if I turn on Error logging, I do get:
 
"4/02/2014 1:18:33 pm 91 2 MDIForm_Load 4/02/2014 1:18:33 pm 91 Object variable or With block variable not set(l=0) MDIForm_Load" in the ErrorLog file, but VBA modules compile all OK. I cannot find problem.
 
Can someone please help?

 

Reporting database Error warning Pre-Rel14

Submitted by Tom on 2014/02/01 19:45
(FWIW, the problem here is probably related to part two below)
 
Part one:
 
Okay, as often the case, we're not paying attention when things go wrong -
Here's how I remember it all:
 
I realised I wasn't up-to-date on this machine (Win7 x64) so I upgraded to version 14
Opened my main file;
 
 
I reopened the file and tried a repair, and got this:
 
 
OK, again I'm not sure if I restarted IQ, or just reopened the file, but either way it worked next time.
 
 
Part two:

Properties pane

Submitted by Jon on 2014/02/01 15:57
This is a long standing issue that as far as I can tell has not yet been resolved.
 
When I make a change to some attribute towards the end of the "All Fields" list, the pane refreshes and I have to scroll down to where I want to be. Can this please be fixed,or if this is seen as desirable behavior, can we have a setting to disable it?
 
Thank you.
 
Jon 

Editing problem when at bottom of screen

Submitted by Jon on 2014/01/31 11:30
Using 14 on Windows 7 Professional.
 
I thought this was resolved earlier but it is now back with a new twist.
 
I add items and eventually get to the bottom of the screen. In this state, I continue to add and type. However on my machine only the top third of the line is visible. Here is the twist: none of my typing appears until I begin a new line by hitting Enter. To avoid this I can us the touchpad or mouse to scroll slightly thereby revealing the entire line. My typing appears then, but I should not have to do this dance.
 
EDIT: I tried zooming. That made it worse, but while trying I noticed that using CTRL + Center Wheel on the mouse dose not work. didn't this work on earlier versions?
 
Jon

Coming up in v0.9.26PreRel15...

Submitted by Pierre_Admin on 2014/01/27 10:30
Hi IQUsers !
 
Coming up in the next release :
  1. New: Items can show up at multiple places in the Calendar.
    Ecco Pro users have long enjoyed this feature, whereby an item can show up in the Calendar for each of its date values. For example, a task could show for its StartDate AND its EndDate. Another example is a contact showing up for his/her birthday and wedding anniversary.
    This feature is now available in IQ !
  2. New: Grid > Show Columns (Alt+C) to show / hide all columns except the tree column
  3. New: Fully working Calendar
  4. New: Option to dismiss the Restore Layout dialog on startup
 

Hoisted scratch grid prevents new data to be seen

Submitted by Armando on 2014/01/17 18:45
This is not really a bug. However, it can be confusing.
 
When an item is hoisted in the scratch grid, the scratch grid can't display other data when opened from the properties pane or hyperlinks. This is easily fixed by removing the hoist, but it can be confusing.
 
I would personally prefer if new events triggering the scratch grid would cancel the current hoist. At the same time, if  the user is offered the choice to open a new scratch grid, maybe is that not necessarry.
 
What do you think?