Menu
▾
▴
#3 CLR not clearing objects fast enough
For some reason the VB.net CLR is not cleaning up the
objects after the program exits, this is resulting in the
same computer generated candidates to be used again
if the user exits and then restarts the program quickly.
If there is somewhat of a wait, then new candidates are
generated. I'll have to read more about it. If anyone has
any ideas, let me know.
Logged In: YES
user_id=1165720
Strange. Does this problem happen when you use the 'Exit
Game' button from the Options menu?
Logged In: YES
user_id=1181239
It's very strange. I'm not testing it in our project, just a test
application. I just added a button to generate 4 new
candidates and it works fine each time I press the button,
although I'm seeing some names becoming familiar. That part
may have something to do with the random numbers, but the
other stuff (same candidates being shown) shouldn't. We'll
figure it out, it's not a big deal right now.
Logged In: YES
user_id=1165720
Might the familiarity be caused by not using Randomize() in
the Candidate Class?
Logged In: YES
user_id=1181239
I thought the same exact thing, but added Randomize
functions to the class and even built a function that retreives
a really random number to seed Randomize. I've found a lot of
quirky stuff with this .net version though. Maybe beta2 will fix
some problems (and probably destroy our code)