FiveTech Software tech support forums

... Navigates the web view to a specified URL. SetHtml(cHtml): Sets the HTML content of the web view. Run(): Runs the web view. Destroy(): Destroys the web view and cleans up resources. Eval(cScript): Evaluates a JavaScript script in the context of the web view. Init(cScript): Initializes ...

... making a module and then if I have to work on it I don't have a capable zoom that magnifies that part up to 400% and then a line is crooked and destroys the whole module, but are we kidding? You do not realize what you are saying Fwteam should create a Visual Report Designer with balls not like ...

... including my changes http://www.pflegeplus.com/IMAGES/Xbrwsel6.jpg another test gives the needed result und moves to the top but destroys the new recordselector-counter maybe changing the contens of the codeblock ( it is just a test ) http://www.pflegeplus.com/IMAGES/Xbrwsel7.jpg ...

... := oNewFontForBtnCaption oPanel:oTextFont:End() oPanel:oTextFont := oNewFontForBtnText You do not destroy your fonts because oPanel destroys these new fonts when ends.

Antonio, i try to assign a font, stored in a public variable. I also make for a dialog a own font with same properties. In all this cases the error is present. It seems, that every control destroys the same font.?

TExplorerbar class correctly destroys the bitmaps it loads.
Please check your class catalogo for any problems. You appear to be creating new bitmap handles in the method LoadWindow() which you need to destroy yourself

... it still exists and is functioning. You are confusing two different levels. One is FWH level and the other is Windows API level. oBrw:End() destroys the Windows API level control from FWH level object but have no effect on the content of oBrw variable itself that is a FWH level object not ...

Enrico, >Please try this modified version of your test and you will see that oBrw:End() effectively destroys the browse: Yes, you will see that it is destroyed, but in fact it is not. Try this line instead: define button of oBar action (oBrw:End(), oBrw:display(), msgInfo(valtype(oBrw)) ...

Enrico Using 9.06 the sample closed the listbox but not the window .. It's the expected behavior. oCtl:End() only destroys oCtl control. oWnd:End() closes the window. oBrw:End() closes the listbox but leaves the Window open and subject to 'paint' Can you replicate this behavior ...

Please try this modified version of your test and you will see that oBrw:End() effectively destroys the browse: #include "FiveWin.ch"#include "xbrowse.ch"function Main()   local oWnd, oBrw   DEFINE Window oWnd   define ...

... Only the Path-defines in the Batch- and Link-file, You have to change. I used xHarbour. The Problem : Using the Brush-function in Gradtest1.exe, destroys the Result of the Folder-Tab-Area. Maybe the Tests can help, to solve the Problem and find out, what is wrong or my mistake, I have done somewhere ...

... to store the reference to the xHarbour object passed to the C function Basically you have to block the object to avoid that the garbage collector destroys it. I recommend you to review the source code of the extend system and the item api. We manage PHB_ITEMs (pointer to "items" managed by the ...

Antonio Linares wrote:In that case, no, because the control will destroy it.

Remember not to share the same cursor for different controls, because it a control destroys it, it will be no longer valid for the other controls.

Ok, thank you for the info.

Patrick

Patrick,

In that case, no, because the control will destroy it.

Remember not to share the same cursor for different controls, because it a control destroys it, it will be no longer valid for the other controls.

... the xhabour provided with FWH now. I too had this problem more than a month back. Its no more there. Mr Enrico is correct. XHarbour automatically destroys the Ole objects when all references to that object go out of scope.