GeoControl hangs after loading own projectsettings

[AndyWelder]

After the update to v1.06 GeoControl I can load the projectsettings that came with the program, I can create new projects and I can save these as .gcs file.
However, after loading a .gcs, GeoControl says "Done" but if I click on a button or a layer the program freezes and I see the hourglass for an "eternity". The program can be terminated normally and there are no Error screens; GeoControl simply freezes.

The XP Task manager shows that GeoControl.exe takes 99% CPU and that there are two instances of GeoControl active.

[cajomi]

I have this just tried here. Clicking and pushing buttons while generating a layer, but it all works fine.
Does it happen with all or most presets or may be some special presets?
Of course, the buttons should be disabled while loading a project preset, I will fix this, but I think, that may not be the real problem.

[AndyWelder]

As I wrote the clicking is done AFTER GeoControl says "Done". There is no loading or such going on anymore.
It happens with ALL .GCS files: The ones I made (including the one made with 1.06!), the ones I downloaded and the ones that can be found in the "Layermethods" directory.

[cajomi]

before loading a gcs GeoControl works normal?
After loading a gcs the terrain is shown correct, so that done really is done?

[Darthmagus]

I used and built several projects with the 1.06: I can't reproduce Andy's freeze, GC works fine.

[AndyWelder]

"After loading a gcs the terrain is shown correct, so that done really is done?"
Yes, the terrain is shown correct, the only "anomaly" I can see is that always the second layer is selected.
I'll uninstall GeoControl now, delete the directories that are left after uninstall and remove all references in the registry. Then I'll reinstall GeoControl.
Oh, btw, I didn't receive a notice someone replied to this thread...

[lachsack]

"After loading a gcs ... GeoControl freezes"

yes, the same here

my system WinXP SP2

[AndyWelder]

"I'll uninstall GeoControl now, delete the directories that are left after uninstall and remove all references in the registry. Then I'll reinstall GeoControl."
Done this all, installed GeoControl 1.0 and Update 1.1 (1.06), problem stays.

Uninstalled GC, reinstalled GeoControl 1.0: Problem is gone, I can load a .GCS and edit the terrain. Then Install Update 1.1 (1.06) and the problem is back...

Uninstalled GC, reinstalled GeoControl 1.0: Problem is gone, I can load a .GCS and edit the terrain. Then Install Update 1.05: No problem, it works fine...

Found out two other things:
The freezing up of GC creates a "NewProject_#" directory each time.
The Task Manager shows GeoControl_Update 1.1.exe is still active though I didn't install it the last time.

I'll stick to 1.05 for the time being.

[cajomi]

that is very tricky. I have tried a small correction, may be it solves the problem.
Please download extract and try this test exe:
www.cajomi.de/Download/GeoControl_test.zip (http://www.cajomi.de/Download/GeoControl_test.zip)

[AndyWelder]

Thanks, Johannes for the swift response and going through the trouble of compiling a new .exe!

Looks like this new .exe made things worse.

This is what I did and the result:

After unzipping the GeoControl_Test.exe I moved the original .exe to a backup directory and the GeoControl_Test.exe to the GC directory.
GC started up fine, the splash screen said v 1.05 was loaded.
Next I loaded a .gcs from the layermethod menu. This did load fine, the preview didn't refresh however (but this could be expected from the v 1.05), a rebuild made the right preview appear.
Then I loaded one of my own .gcs's, waited a few minutes to make sure the file was fully loaded, clicked on the "terrain" tab and now GC froze the same way as with v 1.06.


I observed a few things and made screendumps of these.
Voorbeeld.jpg shows the XP Task Manager: Two instances of the .exe are active during the freeze. Not shown is the tab with CPU usage: GC uses 99% of the CPU.
Voorbeeld2.jpg shows how GC looks during the freeze; notice that Layer2 is selected... Normally, if a .gcs loads fine, the last layer is selected.

Edited to ad this: The problem occurs if the .gcs has more than two layers, my own gcs's with one or two layers are no problem.