shiftedbits
Member
Crimson 3.0 IDE crashes and completely shuts down the development software when you you double click on grouped line primitives (don't know if it is true for other primitives as well).
Step 1:
Added three line primitives where each line is touching the end of the other. (Say a rectangular shape with the 4th line of the rectangle missing. I have not tried this with lines not touching)
Step 2:
Grouped all three lines in to one object (did not WIGITIZE). Afterwards, double clicking on one of the grouped lines(to edit its properties), causes Crimson to crash.
I mean,
POOF! GONE! BYE, BYE!
It does not happen all the time, but it does if you double click on it rapidly (even after groups edit dialog is open). Discovered this accidentally when the edit dialog did not pop-up at times after the first double-click. Hence, the manic double clicking that followed attempting to revive it. This crash can be duplicated easily now that I finally realized what was causing it. It had me worried for a while as all I was doing was adding and editing display pages when CRIMSON would crash out of the blue.
First Time, wiped out about 2 hours of work. 2nd time it crashed it asked if I wanted to use the Auto saved recovery file (or something similar to that). Clicking yes brought back most of the edits but not all of them (may have lost 5 or so minutes worth of work). But I'll take that over losing 2 hours. (It's possible Crimson may have a Auto save feature which I am not aware of yet as I have come to expect this feature to be a default feature on any type of development software.) This recovery dialog that pop's up is intermittent. Meaning, it does not re-appear after each crash. So there is inconsistency there as well.
Anyhow, has anyone seen similar behavior or have any recommended workarounds (besides the obvious: find the Auto save and set it immediately)?
(I remember in the past, Microsoft’s Visual Studio 6 IDE, and Rockwell’s RSVIEW Me constantly had this type of crashes in the early days. Hopefully, those days are not back).
