Hi again,
I'm not sure if this is something the developers would want to see or know about, or if it's just MS "BS". And here I might add that I have no idea what a runtime library is, so I have no basis upon which to decide whether to contact Inkscape developers. I recently learned I'm using v .44, and since v.45 is the most current release, I'm guessing they won't be interested. But I'd be interested to know your (Inkscapeforum.com staff) opinion on whether to report this MS Visual C++ Runtime Library Error? [Edit: Also, is this something I need to worry about stressing out my machine?]

That's the generic "whoops shit happened" error message. It isn't any useful on its own.

However, if you can reproduce the bug, it would be interesting to know if it still happens with 0.45 or with the latest build. So, if you can reproduce it, please post the steps here. You can also try searching the bug tracker... it might be a known (or already fixed) issue.

Oky-doke!
I do know exactly what I did that caused the error. Well, I mean, I didn't do anything wrong, it just happens that I remember what I was doing and the last button I clicked when the error popped up. (I did get this error once or twice B4, but I was so confused and trying to learn whatever it was that I was trying to do, that I had no idea exactly what I clicked when the error popped up.) So I probably can reproduce it, that is if it's safe to do so. Then I could download v .45 and try it again. But for several complicated reasons, it's going to be a few weeks B4 I can download it. Then I don't know how long it might take me to figure out how to use the new version, whether it's basically the same, or whether it's very different from the version I have now.

Anyway, will it be sufficient to reply to this topic, at such time that I finish trying to reproduce the error in v .45? Or would you prefer that I PM you? As I said, it will be a few weeks (at least).

I wouldn't bother reporting it unless you can reproduce it in 0.45. I'm not sure if I ever used 0.44 but I doubt there will be much of learning curve for you when you upgrade.

>Then I don't know how long it might take me to figure out how to use the new version, whether it's basically the same, or
>whether it's very different from the version I have now.

It's pretty much the same. Just nicer here and there and a few more features. You can also install different versions in parallel. It's really a non-issue.

>Anyway, will it be sufficient to reply to this topic, at such time that I finish trying to reproduce the error in v .45?

Ye, you can reply here. However, you might want to post it directly over at the tracker (if it hasn't been reported yet).

>Then I don't know how long it might take me to figure out how to use the new version, whether it's basically the same, or
>whether it's very different from the version I have now.

It's pretty much the same. Just nicer here and there and a few more features. You can also install different versions in parallel. It's really a non-issue.

LOL!! I got my 1st pc back in the era when developers liked to make big, sweeping changes with each new release (especially MS). As a new user, I was quite flummoxed by it, and to this day, put off installing the next version of anything. But honestly, as I said, many complicated reasons. So it'll be "asap"