New FWH 2.7 February build

Post Reply
User avatar
Antonio Linares
Site Admin
Posts: 37481
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain
Contact:

New FWH 2.7 February build

Post by Antonio Linares »

The new FWH 2.7 February build is ready to be downloaded.

Please review the whatsnew section on these forums for all the new features.
regards, saludos

Antonio Linares
www.fivetechsoft.com
User avatar
TimStone
Posts: 2536
Joined: Fri Oct 07, 2005 1:45 pm
Location: Trabuco Canyon, CA USA
Contact:

New February Build

Post by TimStone »

Antonio,

You said the new February build requires the Feb xHarbour, and you said it would not work with the Jan release.

xHarbour released the February build in January, and did not have a January release.

Does this mean it requires the upcoming 2nd February release, or will it work with the one officially titled February 2006 ?

Tim
Tim Stone
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
User avatar
Antonio Linares
Site Admin
Posts: 37481
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain
Contact:

Post by Antonio Linares »

Tim,

If your FWH (February) application properly links with the xharbour that you have, then you have the right one. If not, you will get some missing external symbols.

xharbour introduced these changes before Harbour, so xHB February should be ok with FWH February build.
regards, saludos

Antonio Linares
www.fivetechsoft.com
User avatar
TimStone
Posts: 2536
Joined: Fri Oct 07, 2005 1:45 pm
Location: Trabuco Canyon, CA USA
Contact:

Error in linking

Post by TimStone »

I get an unresolved _hb_dynSymSymbol

Is this FWH or xHarbour ?

Tim :?:
Tim Stone
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
dpaterso
Posts: 142
Joined: Tue Jan 24, 2006 9:45 am
Location: South Africa
Contact:

Post by dpaterso »

I had the same problem but I found a temporary fix for this a few message threads prior to this one.

However!

Why has the default window background color changed from white to dark grey with this new (2.7 February 2006) release?

Regards,

Dale.
User avatar
Antonio Linares
Site Admin
Posts: 37481
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain
Contact:

Post by Antonio Linares »

Dale,

Is it a MDI window ?
regards, saludos

Antonio Linares
www.fivetechsoft.com
dpaterso
Posts: 142
Joined: Tue Jan 24, 2006 9:45 am
Location: South Africa
Contact:

Post by dpaterso »

Hi Antonio,

It is the first (parent) window in a small test application defined as:

Define Window oWnd MDI

I have fixed it by adding:

Define Window oWnd MDI Color CLR_WHITE, CLR_WHITE

but I was just wondering why such a small thing would have changed and for what reason?

Regards,

Dale.
User avatar
Antonio Linares
Site Admin
Posts: 37481
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain
Contact:

Post by Antonio Linares »

Dale,

We changed it by a suggestion from Enrico, who is a great FW expert, but it seems the change was not ok. We will review it asap.
regards, saludos

Antonio Linares
www.fivetechsoft.com
dpaterso
Posts: 142
Joined: Tue Jan 24, 2006 9:45 am
Location: South Africa
Contact:

Post by dpaterso »

Thanks.

It is not really a problem (unless something else is being affected). I was just wondering.

Put it this way - my rantings and ravings about the FiveWin ListBox Browse are far more important than the background window color :)!

Regards,

Dale.
User avatar
Enrico Maria Giordano
Posts: 7355
Joined: Thu Oct 06, 2005 8:17 pm
Location: Roma - Italia
Contact:

Post by Enrico Maria Giordano »

Antonio Linares wrote:Dale,

We changed it by a suggestion from Enrico, who is a great FW expert, but it seems the change was not ok. We will review it asap.
From MSDN:
COLOR_APPWORKSPACE

Background color of multiple document interface (MDI) applications.
EMG
Post Reply