DeleD Community Edition

[fik]

Hi I am using Delphi Turbo express, the one that was free.
I am finding a odd problem when I run the compiled exe from this either in debugger or on its own, in that whenI open or merge a file, Deled stays running but loses focus completely. Cannot click on any control etc in deled. It seems to send focus to the last used window before deled was run.
Is anyone else using or have express and is this happening to you ?
I am at a loss to find what is wrong. The file loaded appears in deled and in debbuger it just returns control to delphi with deled still running pause and stop still avaliable.
Any ideas what I could have set wrong in project file etc?

[chronozphere]

Sounds weird.

So you can start DeleD, but It goes wrong as soon as you try to open a file right?

What happens when you try running your compiled version outside Delphi?

You could try to do a full build or try to disable the debugger to see what happens (Tools > options > Debugger options > Integrated Debugging). Any difference?

You can also turn the debugger back on, and step through the code using breakpoints.

[fik]

Deled Runs fine except for open/merge file seems to load, can see in views. then deled stops responding all borders light blue like not selected but clicking on them or anywher does nothing.

Exactly the same with running compiled exe outside of delphi.

No diference with debbuger off just jumps back to delphi as though i had exited program but it is still running.

trying single stepping from after file loaded but before routine ends. as where ebver i have put break point seems to either get to ok or has jumped out of before so slowly might track it down.

do you have delphi express to try and does it do same for you ?

very wierd problem

[chronozphere]

I just checked and I see I'm having the same issue.

I'll try some stuff.

Edit: The program is running fine, but it looks "frozen". I've noticed that there are still messages being processed. Other than that, I don't have a clue what's going on.

[fik]

Yes it's very odd. hope your stuff nore sucessful than mine been so far

[fik]

Ok I have got a little nearer.

Found it is in the 'frmProgressForm.pas' procedures 'formShow' and 'formHide' that the application.mainform.enabled gets switched on and off.

If i rem out the disabling in 'formShow' the problems does not occur. Still I am none the wiser why it dosen't get re-enabled correctly and pulls up the last open window??

[chronozphere]

FIXED!

Get Patch now!

The OnHide event never got triggered so the code was never executed. I added a fProgressForm.Hide() call to fix it.

[fik]

Great I had figured that to a little ago, your solution lot nicer than mine.

Strange that commercial version triggers hide event and explorer version doesn't

[Paul-Jan]

Excellent work. And yeah it's strange, but I think the code shouldn't have depended on the "hide" event in the first place, for something crucial as deblocking the whole application. Ah well, enabling/disabling it was a bit of quickfix to begin with, and the fix works great, so let's not bother ourselves with it too much.

Offtopic:

Oh, Chronoz, I now remove markers like "Chronoz, BUGFIX" from the comments when committing the patch. I only leave details that I think might be helpful to "future generations of developers", which is usually just the barebones comment. Or not even that, if the code speaks for itself.

However, such markers are incredibily helpful for me (or anyone else) while reviewing and merging the patches, so by all means please keep putting them in!

If you come across "INFO, PJ" (or other markers by me) feel free to cut them out as well. They have good use when working with a small fixed group of developers, but after giving it some thought I figure they really don't belong in an open source application that might have hundreds of people contributing to the source on and off.

[Jeroen]

[chronozphere]

It seems that this problem may also occur while lightmapping or CSG-ing. That's the reason I lost my beach scene the other day.

Fortunately it's fixed now.

PATCH!