FiveTech Software tech support forums

... 86 version of the Nuntucket Clipper, then I moved on to the Summer 87 version, that is, many years before the Clipper became Ca-Associates who killed the clipper with version 5.3, then we moved on to Clip4win, tried Alaska, and then Harry Evans, an Austrian from Momos clipper magazine in Bolzano, ...

... 86 version of the Nuntucket Clipper, then I moved on to the Summer 87 version, that is, many years before the Clipper became Ca-Associates who killed the clipper with version 5.3, then we moved on to Clip4win, tried Alaska, and then Harry Evans, an Austrian from Momos clipper magazine in Bolzano, ...

... or STYLE nOr (WS_CAPTION, WS_BORDER, WS_CLIPCHILDREN, WS_VISIBLE) The first time the window box is loaded and resized, the screen flickers. So I killed and solved all styles. But when you open the window from another menu The event is not working. I will adapt to the new environment according ...

toninhofwi wrote:I understand you, but the classic BCC was killed and this new BCC is a clang based compiler (http://clang.llvm.org/)

So? What's the point?

EMG

Enrico Maria Giordano wrote:

toninhofwi wrote:IMHO is time to think to move from bcc to mingw.

Why? I need I real reason or I'm not interested. MinGW is from Linux, a world that I don't like very much.

EMG

I understand you, but the classic BCC was killed and this new BCC is a clang based compiler (http://clang.llvm.org/)

Regards.

... the loop. Still the original EXE was working fine and now it doesn't when compiled with the new FWH. So, at some point there was a change that killed my app. The change was probably to fix a bug that my app was relying on. However, all is well that ends well. James

... for IPreviewHandler ... It has a big problem that I can not solve ,suggestions are welcome. if we load Excel or Word documents, the process is not killed and excel process is in memory . I've tried several ways but does not work. not dispose excel process. :-( c++ code ... #include <hbapi.h>#include ...

You need not add any other library. This works whenever the program exists "normally" but not when the process is "killed". 1) In our normal Exe's this EXIT function/procedure is not executed when a run-time error is encountered because PostQuitMessage( 0 ) is used in ...

... this is the default behavior of OO 3.0: when you hit the window close button of the last document open then soffice.exe and soffice.bin are killed. soffice.exe as soffice.bin aren't killed if you close the document with "Window-Close window", "file->Close", or the ...

... esta lo que logro construir http://www.sitasoft.net/fivemac/iphone/files/hrbiphone.zip cuando ejecuto harbour sigue aparenciendo KILLED!!! http://www.sitasoft.net/fivemac/iphone/screen/harb1.png http://www.sitasoft.net/fivemac/iphone/screen/harb2.png

Antonio

tengo todo eso instalado y ya lo probe.... al ejecutar ./harbour lo que me sale en el iphone es "Killed"

... experiencing. Mr James I also wonder, if we can't kill the oBrw object, then why can we kill the recordset object? Or is the recordset object not killed either, just erroring out? In fact the recordset object also is not killed / destroyed even after setting oRs := nil. This recordset object still ...

... consequences. Another fallout is that the object's destroy method is not called and the resources will not be released. An object should be killed the way it is designed to be killed. Shortcutting by setting it to nil is not desirable. >> If we modify the paint method, don't we also ...

... if it still exists? I also wonder, if we can't kill the oBrw object, then why can we kill the recordset object? Or is the recordset object not killed either, just erroring out? James

... cSeek )   ENDIFRETURN lReturn  But the disadvantage is, that the search string is still displayed after <cSeek> is killed by the TXBrowse object.