Xailer & OZ Software

Hi,
Am migrating code from xHarbour to Harbour using Xailer 3.02.
All going well with a few #XTranslates for all the INET.... functions to HB_INET.... plus a few other changes.
Looking for simple equivalents Xailer/Harbour to :
IsDir() or IsDirectory()
Threadsleep().... tried FT_Sleep but not available.
Yes I could write something for these but would prefer to use anything built in.
Any suggestions would be appreciated.
Chris

Chris,
> IsDir() or IsDirectory()
Check ExistDir( <cPath> ).
> Threadsleep().... tried FT_Sleep but not available.
Maybe Sleep( <nMilliseconds> ) does it, but it only works on the main
thread, IIRC.
Regards,
José Lalí­n

ChrisGillard escribió el vie, 19 abril 2013 11:17
Threadsleep()....
I guess you must use mutexs
hb_MutexLock( pMtx )
hb_MutexUnlock( pMtx )
Regards,

Hi Ignacio,
Thanks for those suggestions ... I'm sure they will do what I want.
I will miss my xHarbour .chm docs. Sadly the only thing I have found for Harbour so far is a harbour Reference3 Guide, 3.2.0 .... its one huge html page but does appear to have a lot/most Harbour functions listed with some docs on each one.
Are there any other docs for Harbour that you know of?
Thanks again.
Chris

Chris is right. Include the Harbour documentation, and ensure that it contains descriptions and/or links to the Extend system. Also, links that cover the Mingw-Harbour interface, in more detail.
Even if you choose to insult customers by ignoring some of their questions, you can at least say, "Sorry, we don't really support this, but you might find further information at this site at www..., or in the Harbour documentation".

Hello,
Xailer 3.1 will have its own Thread implementation through classes. BTW, I attach the documentation I personally have create with all the docs I have found googling. I hope you can understand it with any translating engine. In case not, please ask for advice.
Regards,


Attached files Harbour Threads.txt (6.7 KB)Â

DGauss escribió el sáb, 20 abril 2013 14:07Chris is right. Include the Harbour documentation, and ensure that it contains descriptions and/or links to the Extend system. Also, links that cover the Mingw-Harbour interface, in more detail.
Even if you choose to insult customers by ignoring some of their questions, you can at least say, "Sorry, we don't really support this, but you might find further information at this site at www..., or in the Harbour documentation".


Sorry. I'm missing something? Who has insult anyone? Was me? I hope not.
Regards,

Hi Ignacio,
I don't know where that other comment came from either.
My only wish is that Harbour had general docs more like xHarbours excellent ones which I think cost xHarbour quite a lot of money to have written.
Regards
Chris

Well, I can forward a list of some of the emails which were simply ignored, but that would seem to be a waste of time, and wouldn't accomplish anything.
Anyway, glad you got some docs to work with, Chris. You could use a utility to pull web pages, in order to obtain the Harbour html docs online.