After using the fields more for entry of larger text I have noticed an interesting thing.

 

Scenario:

- Item field in wrap mode (field setting for the grid), no Maximum Height set in the Manage Grids for the grid in question:

- 2 items: A: one with lots of text, B: one with lots of empty characters, spaced (e.g. VBS code)

 

Item A does not display all of the text and it is shorter than B which presents all the text.

So I assume that there might be a setting that checks how many characters there are in a field and once a certain threshold is crossed it doesn't display additional text even in Wrap Mode.

 

Is this correct?

 

 

 

 

There is a nasty bug in v74a which I have noticed, not present in v72.

 

When I am moving with the left and right arrows in text-edit mode, if the field that I am editing is the the leftmost in the Grid, the left-arrow does not move the cursor but selects the item instead. The same is true for the right arrow.

hi,

 

I'm using the portable version of IQ, and keeping it in sync between 3 different machines. I have two questions about settings and customisation:

 

1. I'd like to keep my settings synched so that no matter what machine I'm using IQ on, I have the same keyboard shortcuts, it always starts up the way I want it, the fonts are as I want them etc etc. When I say "portable", I mean I'm running the portable version from each machine locally. I also have it on a USB stick, but that's just for keeping the machines in synch, I'm not actually running IQ from it.

 

Settings all seem to be stored in the users folder. The problem is that on each of these three machines I have a different user name. So I end up with three users in effect and separate settings for each one.

 

Is there any way I can have a single set of settings I can carry around from one machine to another?

74a introduced spell check but it does not work for me on either computer that I use IQ on.  I run the portable version on Windows 7 64-bit.  Is it not working for anyone else?

 

Thank You

<UPDATE> 2016-05-20 Confirmed FIXED in version 77 - Thanks!>

<UPDATE> 2016-04-24 This problem is still present in version 75. </update>

 

The add new item dialogue has recently been improved. However, at some point, a bug appears to have crept in. Pressing the down arrow in the wikitags box correctly brings up the multiple-value selector. However, any values selected here are not copied into the dialogue box and are not recorded as new values with the item.

 

In 74a the grid-line colors are next to impossible to change to the right color. The last digit gets changed each time I exit the input-field.

 

Video comparing v72 vs v74a.

Hi there,

 

I am testing a few things with column equations for date fields.

 

Scenario: Parent getting the maximum (latest) date from a child.

 

Field: colDate

 

Column Equation: max(Children).

 

Bug: Cannot get the exact time (seems to be +-5 minutes or so).

 

 

Can this be mitigated by duplicating the max function from the System Code and change something specific for Dates?

 

Subject-line sums it up pretty well.

I've started using large grids with many columns and with cells containing varying amounts of text.  There are some issues with how horizontal scrolling is done that I'd like to discuss.

 

As you scroll horizontally, the grid view changes dynamically based on the height of the cells displayed.  This means that the location of your selected grid row jumps up, down, and all over the place as cells of varying heights pass into and out of view.  It's even possible for your selected row to disappear completely then reappear again.

 

I guess the advantage of this behavior is it allows you to display more rows at a time if you're showing a section of your grid that has only cells with one or two lines.  But I don't think this advantage offsets the jumping around behavior, which I find strange and disorienting.  Maybe there are other advgs/disadvgs that I'm not seeing. 

 

The other op

 (Not hiding a column, but actually removing it...)

 

[EDIT] : messes columns headers grouping to the right of the removed column. Haven't done much testing, but it's happened quite a few times.