Page 1 of 1
Not Responding ... its back ...
Posted:
Tue Sep 24, 2013 10:40 pm
by TimStone
A few months ago we had a problem where programs written using Harbour and MSVC 2010/12 would simply freeze if left unattended for a period of time. It was fixed.
Its back ...... with 13.07.
A mouse or keyclick comes up with the Windows error of not responding, and then aborted the program.
When trying to re-enter the program, my client reports the error "You must create a main window in order to use a Tsocket object". This error message is also appearing with xHarbour.com builds ...
Ideas on what might be causing this and how we fix it ?
Tim
Re: Not Responding ... its back ...
Posted:
Tue Sep 24, 2013 11:01 pm
by Antonio Linares
Tim,
Are you able to locate your messages regarding the freeze that you posted ? I am looking for freeze but don't find yours.
The socket errors because the main window of your app, somehow, it has not been created and it is nil. I asume that you create a socket after you DEFINE WINDOW ...
Re: Not Responding ... its back ...
Posted:
Tue Sep 24, 2013 11:02 pm
by Antonio Linares
Tim,
Also I would appreciate if you could test it with FWH 13.08 (3rd revision), thanks
Re: Not Responding ... its back ...
Posted:
Tue Sep 24, 2013 11:25 pm
by TimStone
Sorry ... here is my original post on THIS topic.
viewtopic.php?f=3&t=26544
Re: Not Responding ... its back ...
Posted:
Tue Sep 24, 2013 11:35 pm
by TimStone
And it was reviewed in detail in another thread:
viewtopic.php?f=3&t=26507&start=30In that case, it was a problem with tMsgItem. Is it possible that the correction was lost in the lasted 13.07 / 13.08 builds ?
Tim
Re: Not Responding ... its back ...
Posted:
Tue Sep 24, 2013 11:50 pm
by Antonio Linares
Tim,
I have just checked FWH 13.08 and Daniel's code is there.
I can not check 13.07 right now, could you please check it inside source\classes\tmsgitem.prg Method Refresh() ? thanks
Re: Not Responding ... its back ...
Posted:
Wed Sep 25, 2013 12:08 am
by TimStone
I have 13.08 on here now and out in testing. I will see if it is resolved.