Author Topic: Show stopper bug  (Read 6994 times)

alimamo

  • Jr. Member
  • **
  • Posts: 24
    • View Profile
    • My blog
Show stopper bug
« on: July 01, 2007, 07:42:14 PM »
Hi,

Since I am running the demo I hadn't updated Topofusion Pro for a while. I got online and downloaded the latest version, 3.12, and installed it over 3.0.

When the new version runs the splash screen comes up and I immediately get an error.

"Run-time error - 383"
"Text property is read only"

I am pretty sure nothing in the folder is set to 'read only'.
Clicking the 'OK' on the error box closes the error box and the program continues, but I get this:

http://img183.imageshack.us/img183/3564/topoga7.gif

Rather odd. The drop-down boxes work, but selecting an item doesn't. I click the X to close the program and the window goes away, but the splash screen is still there and the program is still running if I look at the task manager.

Running XP SP2 on a NON-English Windows system (Korean).

Luckily I got the data out of the GPSr before I tried to update the program. Looks like I'll have to stick with 2.97 on the old computer for now. (... the new computer is so much faster.  '<img'>  )

Thanks for any info or help.

Robert

Krein

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Show stopper bug
« Reply #1 on: July 01, 2007, 07:59:08 PM »
Wow, thanks for reporting the problem.  And special thanks for letting us know you are using the Korean setting.  I will be willing to bet we introduced a bug that only shows itself with non-english setting.

We'll check it out and let you know what we find.  Sorry about the bug.

I tried changing to Danish, and a few other settings, and it worked OK.  But I don't have a setting for Korean.  Must be a separate download?  I'll see what I can find.

Krein

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Show stopper bug
« Reply #2 on: July 02, 2007, 05:51:33 PM »
Well, I had a look at this today and couldn't duplicate the problem.  It doesn't make much sense.

I installed the east asian files, switched to Korean mode, then did a clean install of 3.0.  I then upgraded to 3.12 (both times demo versions) and it loaded with no problems, still in Korean mode.

Windows is kind of dumb about the way it handles changes between language settings, sometimes behaving unpredictably.  So it is likely something we can fix, but I don't know how to approach it.

One thing to try is deleting (or temporarily moving to another directory) your TopoFusion.ini file.  There may be a setting there that is not reading correctly.  It'll reset your TopoFusion to default values.

Let me know if that helps or not, or if you have any guidance on how to get my computer set up to match yours.  Maybe I'm not doing something right.

Thanks.

alimamo

  • Jr. Member
  • **
  • Posts: 24
    • View Profile
    • My blog
Show stopper bug
« Reply #3 on: July 06, 2007, 02:38:50 AM »
OK, I will have a go at moving things around next Monday.

So you know, this a actually a completely Korean Windows XP system. Not converted to Korean from language downloads.

If you want to let me know where the individual downloads are, I could go back to 3.0 and then try installing each version to maybe help you see when the problem was introduced.

I'll try the other stuff first. Is it enough to just move the ini file or should I clean the entire directory and try a clean install? Yeah, I am surprised that i haven't already tried that myself. but I was worried about the data and log, and since I have a working older version at home ....

Monday

Robert

Krein

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Show stopper bug
« Reply #4 on: July 06, 2007, 03:06:34 PM »
Great, thanks for the updated and patience with it.

For that particular error message, during the splash screen, just moving the .ini file is enough.  Doing a fresh install is unlikely to have any effect.

Let us know how it goes, and then it would be great for you to incremental go along in versions to pinpoint the bug.  My guess is there is something wrong reading a setting from the .ini file.

Thanks.

m38a1guy

  • Sr. Member
  • ****
  • Posts: 135
    • View Profile
Show stopper bug
« Reply #5 on: July 08, 2007, 04:14:10 PM »
I got that Error myself on the 3.08 beta version and it stayed until I uninstalled and then Rebooted and the reinstalled, otehrwise no matter the version installed that error stayed. Its the first time I ever seen that error before. I use the USA version of XP.

alimamo

  • Jr. Member
  • **
  • Posts: 24
    • View Profile
    • My blog
Show stopper bug
« Reply #6 on: July 08, 2007, 08:14:43 PM »
Apparently you were right on the money. Moving the ini out and running the program creates a new ini and the program seems to run fine.

I went into the preferences and pointed the program back to the right directories and everything seems to be there, log and all.

I had a look at the two ini files, but for the life of me I couldn't see what the problem could be. But I guess that is why I am just a user and you are the developer. Have a go at it ...
http://alimamo.googlepages.com/copyofTopoFusion.ini.zip

Thanks for the help and kudos for figuring out the problem with just my description.

Sincerely,

Robert

Krein

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Show stopper bug
« Reply #7 on: July 09, 2007, 05:16:00 PM »
Great, glad you're back up and running.

You probably wouldn't notice the difference in the .ini file unless you had a program do a "diff" on them.  It's probably something stupid like a string in quotes vs. no quotes.  We make the same function call, but it can give different results depending on windows language settings, even though it really has nothing to do      with it.  Thanks for the ini file, I'll see if I can come up with a workaround.