HMG 3.4.1

[dhaine_adp]

Hi Pablo and Mustafa,

Hi Mustafa + Danny,

Thank you to report your experiences in 64 bits.

Would be interesting to describe where have you have taken Harbour-64 ? Which link ?

I used TDM-GCC bundle to recompile the HMG libraries and rebuild harbour libraries from the source (core-master). I used this link:
http://tdm-gcc.tdragon.net/ http://tdm ... /download
Instead of installing to the default folder as TDM-GCC I used MingW-64 and MingW-32. This is a minimum installation only. Then I rebuild the harbour from the latest source code. After the installation I did the commands below:

Code: Select all

c:\core-master
For 64 Bits
set path=c:\MingW-64;%path%
win-make

for 32 Bits
set path=c:\MingW-32;%path%
win-make

After compiling harbour, the binaries are located inside the folder C:\core-master\bin\win\mingw64. I simply move them to c:\hmg\harbour-64. I just followed the directory structure of the original hmg\harbour structure. But because of Ansi and Unicode I have now a directory structure like this:
c:\hmg\32bit\lib\ansi
c:\hmg\32bit\lib\unicode
c:\hmg\64bit\lib\unicode

[Pablo César]

Thank you Claudio for your answer.

I have read this comment in Google Harbour forum:

"IMO You have not advantages using 64 bit"

I've got some questions:

Upto what point this could be true ? Any advantages since this opinion to actual days ?
Or we can still using in 32 bits upto a even a necessity imposed by the OS ?

B.Rgds

[Pablo César]

I used TDM-GCC bundle to recompile the HMG libraries and rebuild harbour libraries from the source (core-master). I used this link:
http://tdm-gcc.tdragon.net/ http://tdm ... /download

Thank you Danny to share your experience.

May you inform us which Harbour version you got it, please ?

.. because of Ansi and Unicode I have now a directory structure like this:
c:\hmg\32bit\lib\ansi
c:\hmg\32bit\lib\unicode
c:\hmg\64bit\lib\unicode

Nice !

[srvet_claudio]

Thank you Claudio for your answer.

I have read this comment in Google Harbour forum:

"IMO You have not advantages using 64 bit"

I've got some questions:

Upto what point this could be true ? Any advantages since this opinion to actual days ?
Or we can still using in 32 bits upto a even a necessity imposed by the OS ?

B.Rgds

Partly is true, today the applications that benefit from the 64-bits are those who make a large memory allocations such as image processors.

[Pablo César]

Nice to know it, thank you Claudio.

32 / 64 bits, ANSI and UNICODE.

I'm happy to see that we are looking into the future...

[dhaine_adp]

May you inform us which Harbour version you got it, please ?

Pablo, please take a look the attached snapshot and compare the difference. The version from within the powershell is the one that comes from the latest HMG release.

[Pablo César]

Thanks Danny.

[dhaine_adp]

Partly is true, today the applications that benefit from the 64-bits are those who make a large memory allocations such as image processors.

Dr. Claudio,

Speaking of image processors, I am thinking to put digital watermark on my apps when it is running as a protection against screen snapshot from print screen or snippingtool or from camera (digicam, smartphones and tablets). Nowadays, people normally take snapshots and shared them instantly to social media. Sometimes they shared confidential record, reports, etc. To curve this behavior, if their logon ID becomes a watermark they would think twice. Aside from that the watermarks position is dynamic, they change every minute just like an RSA token. However any image editing can easily throw out the watermark unless there is an invisible digital mark that can be detected by watermark verification routine.

Example: Displaying records in grid, the watermark should appear on grid (transparent) while allowing users to navigate and perform normal tasks.

Well it seems like it's difficult to be made with HMG+Bos_Taurus.

[quartz565]

Many thanks Mr. Rathinagiri and Dr. Soto !

[srvet_claudio]

Partly is true, today the applications that benefit from the 64-bits are those who make a large memory allocations such as image processors.

Dr. Claudio,

Speaking of image processors, I am thinking to put digital watermark on my apps when it is running as a protection against screen snapshot from print screen or snippingtool or from camera (digicam, smartphones and tablets). Nowadays, people normally take snapshots and shared them instantly to social media. Sometimes they shared confidential record, reports, etc. To curve this behavior, if their logon ID becomes a watermark they would think twice. Aside from that the watermarks position is dynamic, they change every minute just like an RSA token. However any image editing can easily throw out the watermark unless there is an invisible digital mark that can be detected by watermark verification routine.

Example: Displaying records in grid, the watermark should appear on grid (transparent) while allowing users to navigate and perform normal tasks.

Well it seems like it's difficult to be made with HMG+Bos_Taurus.

Dhaine,
The insertion into Windows controls of invisible digital watermarks is very difficult because it requires direct access to the bits of the images on the screen.