Code center > Bug reports
Unassigned variable when using InstaWin
EricL:
Pressing the InstaWin button on the Contest Results dialog in 2.4A (VB version) during a contest results in a crash at line 16 of Contest_Form.frm. The variable nd is declared but never used or initalized. Since nd is never used, commenting out the line (t=nd.robn) addresses the problem and appears to result in correct behaviour.
"Doctor, it hurts when I do this."
"Then don't do that."
Griz:
thanks eric.
I ran into that in earlier versions of 2.4
but in 2.4.A ... I haven't been able to get leauges to run ...
crashes anytime I try to create a leauge ...
or to load an existing one, even F1.
I've asked about this a number of times here ... got no reply.
so let me make sure ...
you are able to load and run leauges in 2.4.A, yes?
do they work except for this InstaWin button?
thanks ...
one reason I stopped using 2.4 and went back to 2.37.6 ...
so this may be good news. ;)
Numsgil:
I always feel bad working on 2.4 since it postpones the C++ development...
If you'd really like me to I can go through and try to make the leagues work. To be honest though the code is a mess (I wrote the code I admit, not one of my cleaner hacks).
Griz:
--- Quote ---I always feel bad working on 2.4 since it postpones the C++ development...
If you'd really like me to I can go through and try to make the leagues work. To be honest though the code is a mess (I wrote the code I admit, not one of my cleaner hacks).
--- End quote ---
well it sounds like Eric has it working to some degree ...
and is finding/fixing bugs so ... ???
the errors I get may be due to something else ...
I get path errors sometimes ...
and I didn't want to spend more time on it if it wasn't working at all ...
but if he has it up and going ...
then maybe the problem is I don't have all the folders and
league tables in the right place or something.
that he has it working makes it worthwhile for me to play with it again.
so I wouldn't sweat it.
eventually, it would be nice to have ...
as I don't see being able to alter the c++ version myself ...
so the VB programs are more interesting for learning.
maybe we'll keep poking around and figure it out.
EricL:
Nums, I'd say you should stay focused on the C++ version. I'm just filing bugs on 2.4A as I find them mostly because I can I guess, just to have a record of them to make sure they get picked up in the C++ fork (yea, I know. I expect the value of 2.4A bug reports is marginal for the C++ fork given the magnitude of the re-write but what the hey...). I'm not on a mission to make anything specific (like leagues) work in 2.4 - just fixing crashing bugs at this stage - though if there is high demand to make a specific feature work in 2.4 that used to work in previous versions, I could probably be of some use there.
I have a pretty fast machine, so it's pretty easy for me to run things in VB all the time and identify/investigate/fix simple things as/when I hit them. I don't really have to know the code that well to fix simple overflows and such, not in depth and those who do know it like yourself are IMHO better utilized working on the new architecture and the port. I certainly don't expect any more 'official' work on the VB fork given the focus on C++ and I'd be happy to share my private VB exe with anyone who can't build the post 2.4A cumulative fixes themselves. I'd also be happy to spend a little bit of time (ephansis on 'little') making specific functionality work in 2.4A if someone really needs something (I really miss the gene activation form for debuigging bots and may spend some time on that this week) but at some point in the not too distant future, I plan to volunteer to help on the C++ version so I don't want to do too much down level....
So, I do think we want to track 2.4A bugs, expecially crashing bugs, but that doesn't mean you or anyone else has to fix them much less make specific features work. My vote is to keep the big guns full speed ahead on the C++ port.
If someone is dying for something specific to work in 2.4A, let me know and I can spend some time on it, letting Nums work on the real deal.
-E
Navigation
[0] Message Index
[#] Next page
Go to full version