_ArrayDisplay()

[GEOSoft]

I'm not going to bother reporting this as a bug and I'm not even sure whose bug it would be anyway and besides it's just not important enough.

Using the above named (misnamed?) function (still in the wrong udf, IMO) if you resize the window you lose the vertical scroll bar.

If I have to write repro code for this then someone is in the wrong business. Just make sure that the array has over 30 items and you will see it right away.

Okay, so I shouldn't have said you were in the wrong business. Just ask (nicely) and I'll give you the repro code.

[Xenobiologist]

Hi,

already fixed for next version by jpm.

Mega

[GEOSoft]

Hi,

already fixed for next version by jpm.

Mega

jpm is da man!!!!

It didn't bother me, because I rarely use the function anyway, but I thought someone might want to look at it.

[jpm]

Hi,

already fixed for next version by jpm.

Mega

Not sure to understand why my resizing on Width only did the trick ...

[GEOSoft]

Not sure to understand why my resizing on Width only did the trick ...

When it works, don't ask why!

[Xenobiologist]

Hi,

sorry if I understood something wrong - jpm

Mega

[jpm]

Hi,

sorry if I understood something wrong - jpm

Mega

so it is a problem or not !!!

[randallc]

so it is a problem or not !!!

Hi, Off topic a little, sorry.

Is the _ArrayDisplay() func being updated to accept the new 65,000 control limit instead of 4000?

Thamks pm, Randall

[jpm]

Hi, Off topic a little, sorry.

Is the _ArrayDisplay() func being updated to accept the new 65,000 control limit instead of 4000?

Thamks pm, Randall

it should have no impact as you get it for free unless you compiled your script with previous beta/release

[GEOSoft]

so it is a problem or not !!!

Now we are all confused. Has the issue I mentioned been solved (bu any method)? If YES, then it doesn't matter how it was resolved. If NO, then my first post will probably still apply.

[jpm]

Now we are all confused. Has the issue I mentioned been solved (bu any method)? If YES, then it doesn't matter how it was resolved. If NO, then my first post will probably still apply.

Just check with the beta and report

[GEOSoft]

Just check with the beta and report

Well according to the Beta page, 3.2.11.5 is the latest beta and that's the one I spotted the problem under so I guess it is still an issue. Not a big one though, unless of course it's affecting AutoIt functionality.

[randallc]

it should have no impact as you get it for free unless you compiled your script with previous beta/release

Sorry again, 2nd topic here;

at least in 3.2.11.4 ;"$iLVIAddUDFThreshold = 4000", so does still affect this function...

Thanks,Randall

[jpm]

Sorry again, 2nd topic here;

at least in 3.2.11.4 ;"$iLVIAddUDFThreshold = 4000", so does still affect this function...

Thanks,Randall

Just check perhaps now the UDF is doing something that is not needed anymore

[jpm]

Well according to the Beta page, 3.2.11.5 is the latest beta and that's the one I spotted the problem under so I guess it is still an issue. Not a big one though, unless of course it's affecting AutoIt functionality.

Thanks I will check :)

[-Ultima-]

Just check perhaps now the UDF is doing something that is not needed anymore

Increasing the limit to something like 65500 should work fine. Indeed, you'd be hard-pressed to find any real reason to display an array of such a gigantic size, but with the AutoIt control limitation of 65532, any array of more than that many listview items (give or take a few) won't be fully displayed. There's no harm done in the extra bits of logic involving $iLVIAddUDFThreshold, since the only time it's really used is in the second for loop for adding listview items, meaning if the limit isn't reached, it won't do anything anyway. If it is reached, well at least we'll know the listview does display the full array size

That said, I made the number easy to change because of cases like this (where the limit can potentially change -- and it has).

Cheers!

- Ultima

[GEOSoft]

Increasing the limit to something like 65500 should work fine. Indeed, you'd be hard-pressed to find any real reason to display an array of such a gigantic size, but with the AutoIt control limitation of 65532, any array of more than that many listview items (give or take a few) won't be fully displayed. There's no harm done in the extra bits of logic involving $iLVIAddUDFThreshold, since the only time it's really used is in the second for loop for adding listview items, meaning if the limit isn't reached, it won't do anything anyway. If it is reached, well at least we'll know the listview does display the full array size

That said, I made the number easy to change because of cases like this (where the limit can potentially change -- and it has).

Cheers!

- Ultima

How will that affect the symptom I described? The symptom has nothing to do with the number of items except that a minimum of 30 items may be required to show what happens when you resize the window.

[-Ultima-]

It doesn't. I was referring to the case where AutoIt's control limit was increased -- a response to randallc's post. Off-topic indeed, so if you'd like, we'll let that little sub-discussion die here.

[GEOSoft]

Was this ever fixed?

[randallc]

Was this ever fixed?

Hi

Doesn't look like it in 12relaese;

Local $iColLimit = 250, $iLVIAddUDFThreshold = 4000, $iWidth = 640, $iHeight = 480

randall