I've looked through the topics and I couldn't find a report for this, even though I am almost certain more people have had problems with it.
I don't know if this bug is presistent in large mode, as I never use it, but it happens quite a lot in small mode, and by "quite a lot", I mean 5 out of 10 times.
What happens is that when I scroll (using the wheel on my mouse) the combolist on the right side of the screen, zquest sometimes crashes. I'm not sure exactly why, but I'm certain it has something to do with the scrolling. It seems to be at random, though the placement of the pointer could possibly have a role to play in this bug. It does also seem to happen more frequently if I scroll quicker.
I haven't been able to test this in the newest build, due to downloading restrictions, but it's a bug that's been bothering me for a while, over multiple builds, so unless this has been fixed recently, I don't see why it shouldn't still be a problem.
- Robin
I'm currently on 1256. For every hour of Z-Questing (I use large mode?) I get a couple of combo-list crashes.
It doesn't seem to matter if I use select combo, scroll to combo, mouse scroll, up or down arrows... It happens often, and makes Z-Quest nearly unusable.
Can this be repeatable in N-steps? 😞
I've had it quite a few times. Not recently though, but I haven't been building screens recently =P
I have had some lovely crashes on start-up, about one every 5 times or something. But gdb's not working, yay!
Right. Well obviously you need to hurry up and get that working since you are getting these crashes. 😛
Step 1: Use ZQ to build screens
Step 2: Crash, usually sooner rather than later
....
Step 3: Profit!
It takes me about half and hour to transcribe a single screen. If usually happens every 2-3 screens.
Hey, I think I got it. Caught the little bugger trying to draw outside its bitmap. I put a check on the coordinates, so it shouldn't crash anymore, assuming that was the only problem there...
I myself am still getting this random crash in the latest windows build.
Forgot to recheck this one. Is it fixed now? Haven't seen it myself lately...