Crashes if # of items < list_limit

[checkist84]

For 1.5.0, if total number of items are less than 'list_limit' for current filter/list, the program crashes.

Seems 1.4.1 also has this problem...

[rogalian]

I don't have that problem here (and didn't with 1.4.1 either, my "Top 10" worked fine when it was still being populated with stats).

[checkist84]

If that's the case (some people does/doesn't have this problem), I think it might be helpful to add my system spec...

Tested on two Windows 7 (64bit) machines. Both 32/64bit executables had this problem.

[rogalian]

Same configuration here. Post the full filter?
On 28 Feb 2015 15:55, "checkist84" [email protected] wrote:

If that's the case (some people does/doesn't have this problem), I think
it might be helpful to add my system spec...

Tested on two Windows 7 (64bit) machines. Both 32/64bit executables had
this problem.

Reply to this email directly or view it on GitHub
#109 (comment).

[mickelson]

Hi I found this one, thanks for the report.

The crash happens when you start with a list that is less than the list_limit... so in your case rogalian the list would probably have been padded out still with games with stats at zero since the total list you were starting with was probably more than 10.

There's also a really dumb bug for emulator configurations that I've just fixed. I'm not sure how I didn't stumble over it earlier. I'm going to put together a 1.5.1 release to address these issues.

[rogalian]

Ahh, yeah that would make sense, the list is large generally.

Only thing genuinely affecting me is the -config thing reported, I've not
been able to find a workaround.
On 28 Feb 2015 16:21, "Andrew Mickelson" [email protected] wrote:

Hi I found this one, thanks for the report.

The crash happens when you start with a list that is less than the
list_limit... so in your case rogalian the list would probably have been
padded out still with games with stats at zero since the total list you
were starting with was probably more than 10.

There's also a really dumb bug for emulator configurations that I've just
fixed. I'm not sure how I didn't stumble over it earlier. I'm going to put
together a 1.5.1 release to address these issues.

Reply to this email directly or view it on GitHub
#109 (comment).