Author Topic: Nasty crash in symbol browser  (Read 11696 times)

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: Nasty crash in symbol browser
« Reply #15 on: June 29, 2007, 04:05:31 pm »
Yiannis: Please share your reasons with us. I know that my approach is a "brute force quick fix", but until you manage to pinpoint the bug and find out why it crashes, i'm afraid there's no other way. I would have preferred to keep that code intact, but I fail to understand why it has to be that way.

Please tell me, why do we have only to delete the invalid nodes, apart from the aesthetical reasons? I want to know.

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: Nasty crash in symbol browser
« Reply #16 on: June 29, 2007, 05:27:47 pm »
Yiannis: I'm going to explore a different way of fixing that bug. I'll report when I have some results.

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: Nasty crash in symbol browser
« Reply #17 on: June 30, 2007, 07:05:33 am »
I finally realized why erasing the whole tree isn't a good idea... the tree gets refresed on EVERY FILE SAVE :(

..so THAT was the cause of the 1-sec delay on filesaves! :lol:

Sigh... I'll try changing that other code and see if there are any crashes.