In Table Layout I clicked (righ mouse click) on "Erase Column" function because I thought that the selected column will disapear (will be hidden). Something completely different happend: GenoPro started delete all my data from this column step by step. I saw how many hundreds of records are erased - and what was terrible. there was nothing to do! I desperately tried to push Ctrl-C, ESC to stop the slow action of erasing, no chance. All my data from the field were erased. The only way was to do Undo manually for several hundreds of records.

I know that this was my mistake, I was not aware what "Erase column" mean, but in case of such strong action there should be confirmation window and the action should be possible to stop (ESC or Ctrl-C).

This has been a long time on my todo list, and I was seriously thinking of adding this to Beta 16d before someone had this misfortunate experience.

Don't you have Backups of your GNO files?

I send them all the time by email to myself . You can use a Gmail or Yahoo acount for that matter

Since all the operations have been grouped under a single operation, I was able to improve the code to take advantage of this behavior by eliminating redundant computing between each operation.  On my machine, erasing a column which was taking 30 seconds now takes less than 200 milliseconds.  I tried on a larger tree, where it would have taken about 7 hours to erase 40,000 individual's IDs.  With the new code, the same operation took 2 minutes.  You are welcome to do your own benchmarks to compare the speed increase from Beta 16c and the coming Beta 16d.

Although there is a significant speed increase, the code is still very slow... and can be improved.  For now, I won't optimize anymore because I don't want to introduce bugs.  As suggested, I wrote extra code to respond to the Escape key.  If the user presses the Escape key while pasting, erasing a column or doing a Find & Replace, then GenoPro will stop and return to an idle state.

Before this with my 17,500 names I had to start it and then leave the computer for half an hour or so and do something else, sometimes I came back to find genopro had crashed.

This time it took less than a minute! :P

iaintait (6/18/2006)

---

Before this with my 17500 names I had to start it and then leave the computer for half an hour or so and do something else, sometimes I came back to find genopro had crashed.

Yep, however GenoPro had not *really* crashed.  When a task takes too long, Windows stops drawing anything from the window not responding, making it appear as it had crashed.  Perhaps, if you had waited a few hours, you would have seen the final result P:P.

appleshaw: thanks for advise, I know it but that wasn't the solution.