FORScan does not start : FXList::setCurrentItem: index out o

[solesz]

Hi,

2.1.18 beta

I read the system requirements. Windows 8.x is not listed in the supported OSs. However I downloaded the software and started up on my win 8.1 system.
I received the "FXList::setCurrentItem: index out of range" message.

Is there anybody who can succesfully run this application under win 8.1? UPDATE: or Windows 7? especially hungarian version?

Thanks,

solesz

Important UPDATE: I tested it on Windows 7 Home edition, DID NOT work again.
Both OS system is hungarian, I tried to switch the input language, but did not helped.

[solesz]

FYI
2.1.17 version is working on Win 8.1 HUN, Win 7 Home HUN version.
solesz

[FORScan]

This seems to be a GUI bug and most likely it is not related to the version of OS or language. Most likely, it is related to the environment or vehicle (some specific conditions it happens in). Please tell us, at what moment does the error appear (start app, connect to ELM, connect to vehicle, any specific operation)? What does happen after you close the error window ? Does the application freeze?

[solesz]

Hi,

The error message prevents the application to run.
Dismissing the alert window cauase the software quits.

/BR
solesz

[FORScan]

So application crashes this way immediately after the start (no attempt to connect to ELM/vehicle etc), right?

At this moment, no idea about this bug.

Have you ever tried older version of FORScan, for example 2.1.16 or 2.1.17 (available on the download page)?

[solesz]

Yes, i tried version 17. That is working flawless.
I try to investigate the error message later on.

[solesz]

Hi,

Because of the error message above I installed previous version 2.1.17.
Now, today, I reinstalled the 18 version to check - by rude tools - how the errormessage come up.

But now, I can tell, the error message gone. Both machine I experienced the error now works the 18 version.
One or many or all of the following reason could have occured:
- simple reinstalling solved
- installing previous version then again the new version solved (but then a common file - i.e. a dll - should be present somewhere in a common directory)
- during the installation I forced to use english (instead the proposed Hungarian) UPDATE: I reinstalled using Hungarian, still working
- better stage of stars above the sky - not too technical reason I admit

So far, the software is working.

Solesz

[FORScan]

Thanks for the information. Now the problem looks clear. The key seems to be the Hungarian language (you mentioned this from the first post, but we didn't pay enough attention to it as we believed Hungarian is not supported by FORScan)

It was planned to add the Hungarian support to the 2.1.18 but it didn't happen because the translator had no chance to finalize the work. Intermediate builds were made with Hungarian, but in beta release we removed it. It seems we forgot to remove it from the installer itself. This is what caused the troubles you described above (first installation adjusted FORScan for using language that is not really supported by application). We will remove the Hungarian option from installer until the moment the translations are ready.

[solesz]

It was such a good feeling to contribute even it was only a small bug.