Tyre

[DLH]

Just so I can know where I stand, are these bugs well known or are they unique to my computer.

Sometimes the map goes black and the only thing I can do is shut down the program.

Sometimes when trying to move a waypoint to its proper position in the list, TYRE moves the wrong one and again the only way to get it to stop doing that is to back out of the program and reload it.

Both these things happen after I have been working in the program awhile.

Not a big deal, I just make sure I save often.

DLH

 

[canderson]

I don't run Tyre for extended periods - usually just muddling about with an existing file for a few minutes - so my experience (all good) may not be relevant. I've never seen what you describe.

If it only occurs after a considerable period of use, the most likely culprit in such cases is always a "memory leak" or "pointer error". You might want to let the author know about your specific environment and your experiences.

 

[dhn]

Have sent a link to this thread to the author of TYRE. We'll see if that helps.......

 

[Rick F.]

I stopped using Tyre ... not because the screen goes black, but because it bogs down my computer with each added waypoint. It's not like I'm crossing the country... as I'm only talking about going across the state of FL which is only about 150 miles. Something in the new coding doesn't like WinXP I think.

 

[DLH]

Thanks for the answers. Now I know I'm not alone.

Another problem I've had is a message pops up saying I'm out of memory. I have 2 Gig.

Interesting that I'm also using XP. I haven't noticed TYRE slowing my computer. One route I've planned has 23 waypoints over 730 miles.

Be nice if the bugs were fixed but I find the program so much easier to use that I don't mind saving often and having to reboot once and a while.

DLH

 

[Rick F.]

Not sure but I think I read that the developer of TYRE used a compiler to write this latest version. Compiler's are nice, but can be inefficient and make some errors.

When I worked for the FAA as a System's Specialist (software and hardware), we only used an assembler ? which then converted tasks to computer machine code. Yes, those days are long gone now, but it was very efficient.

 

[dhn]

The author, Jan Boersma invites anyone with issues to email him at:

tomtomrider at janboersma.nl

Screenshots, if relevant, will be useful for him.

 

[canderson]

Thanks for the answers. Now I know I'm not alone.

Another problem I've had is a message pops up saying I'm out of memory. I have 2 Gig.

The clear sign of one of those "memory leaks" I was mentioning earlier.

What is your typical use model for Tyre?

 

[DLH]

I'm not sure what you mean by this.

"What is your typical use model for Tyre?"

DLH

 

[patri]

Confirm there is something with Tyre, at least with version 5.82 (not sure if that is the version you are using).

Monitored with Rammap both with XP and Win7 (64b) and in both case on each changes in map mode, the memory usage increase by approx 12000 KB. Never decreasing even when removing all points!!! Apps memory leak it seems.

I do not have my install file of version 5.81 so cannot say if this was introduced with 5.82 or not

I am sure he will fix it, great program.

_pat

 

[dhn]

Email all concerns to the author (I gave his email address (written out ) in my 2:15 pm post of yesterday in this thread.

Jan told me he is eager to get feedback...........

 

[canderson]

I'm not sure what you mean by this.

"What is your typical use model for Tyre?"

DLH

For what specific purpose(s) do you use the application? Until the author gets things patched up (and Patri confirms my suspicions - it NEEDS patched up), I might be able to suggest alternate applications to accomplish your tasks. Tyre does a lot of things, and the function you need may be available elsewhere for the time being.

 

[patri]

For those of you interested in looking when the memory leak is addressed. This is the page for the release notes. New build correcting the issue will be indicated there.

_pat

 

[canderson]

Not sure but I think I read that the developer of TYRE used a compiler to write this latest version. Compiler's are nice, but can be inefficient and make some errors.

Rest assured that NOBODY writes Windows UI applications in assembler, and that compilers create "machine code" as well - they have to else there would be no way to run them. A typical compiler will, on request, even produce a list file of the 'machine code' that it generated.

The difference is that a compiler takes a higher level language and reduces those instructions into one or more "lines of assembler", if you will. Yes, they can have bugs, but as a mission critical tool for developers, the errata for them are published quickly (except for a few fly-by-night outfits), and most of the time, they're well wrung out in beta testing.

 

[DLH]

Email all concerns to the author (I gave his email address (written out ) in my 2:15 pm post of yesterday in this thread.

Jan told me he is eager to get feedback...........

Thanks dhn, guess I'm just not use to program authors being that available to the users.

patri, I'm using version 5.22

canderson, I use TYRE to build routes using roads that I want to take which often are not the ones that the TomTom would have me use. That's one reason why my route of 730 miles has 23 waypoints.

DLH