So, I have a windows 7 computer that is my main one, but in my other apartment, I have a windows 10.
I installed VB6 on that machine awhile back and made it compatibility XP SP3.
I have subclassing*, safearrays, directsound/direct2d and other memory APIs that can crash the IDE if errors occurs.
Im quite used to subclassing and I always disable it in IDE to avoid crashes. but if errors occurs, it could crash from other sensible APIs, and thats whats happens from time to time.
I can cause a crash by simply run the project and use the "end" button in IDE.
in windows 10, if I run VB6 without compatibility mode I get the same result, "end" will crash the IDE.
but, if I use compatibility mode XP SP3, and I use the "end" button, no crash.
sure if I allow the subclassing in IDE, it will crash. so its not crash-safe. but its still good and could save me if I forgot to save before I run.
anyone noticed this and maybe knows why?
I installed VB6 on that machine awhile back and made it compatibility XP SP3.
I have subclassing*, safearrays, directsound/direct2d and other memory APIs that can crash the IDE if errors occurs.
Im quite used to subclassing and I always disable it in IDE to avoid crashes. but if errors occurs, it could crash from other sensible APIs, and thats whats happens from time to time.
I can cause a crash by simply run the project and use the "end" button in IDE.
in windows 10, if I run VB6 without compatibility mode I get the same result, "end" will crash the IDE.
but, if I use compatibility mode XP SP3, and I use the "end" button, no crash.
sure if I allow the subclassing in IDE, it will crash. so its not crash-safe. but its still good and could save me if I forgot to save before I run.
anyone noticed this and maybe knows why?