Error 9. Subscript out of range.

[KLASS]

Enter the following commands from the help in the address bar:
text font("m", "Consolas", 12, 0, 1);
font(, "Segoe UI", 9, 0, 0);

[admin]

Thanks, happens since 20231117. Won't happen again from next beta.

[jupe]

Unrelated to the above posts (besides topic matching, no ladybug though!), and not sure if this is helpful, but you seemed to fix another similar issue using just this error output here, which made me think it is worth mentioning, the screenshot is from latest ver, but it happened in earlier .0102 too (text in code box below)

The error appears multiple times, it happens as the list pane is being updated, each time the dialog is dismissed more lines are added/updated in the pane.

2024-01-05_125429.png

Code: Select all

Error:  	9 (0x00000009)
Desc:   	Subscript out of range
Dll:    	0
Proc:   	pRowDet@249
Count=5, RowFirst=4, RowLast=4, Hovering=True

Source: 	XYplorer
XY ver: 	XYplorer 25.40.0102 - Lifetime License Enterprise
OS:     	Windows 10 Pro, 64-bit, Version 22H2, Build 19045.3803 (10.0)
Locale: 	1033 (en-US)
ANSI:   	1252, ACP: 1252  (ANSI - Latin I)
Font:   	Segoe UI 11, Segoe UI 9, DBCS: No
DPI:    	120 (125%), 1920x1080

Date:   	2024-01-03 10:22:42

[admin]

Cannot really see it yet. I'll add some additional error trapping to the next beta.

PS: I saw a possible cause now and fixed it. So maybe it'll be history in the next beta.

[jupe]

Ok great!

I'll let you know if I encounter it again.

[jupe]

Unsure if this is useful info, but received this followed by a crash today,

2024-07-26_120348.jpg

[admin]

Strange. Was it a live-filtered list?

[jupe]

From memory, it happened during a tab switch, I don't think the tab I was on was live filtered, and the pane was visibly empty when it crashed, which at that point I think was on the tab I was switching to, so not sure about that one. I wasn't expecting the crash so didn't take much notice, but after the pictured error dialog, the smaller err9 dialog with the yellow icon displayed, followed by the crash.

It was probably a freak occurrence, so if the info in the error dialog isn't helpful, don't worry about it.