Checkbox text disappears Harbour/MSVC

[Enrico Maria Giordano]

I tried with and without manifest and found no problem.

EMG

[Antonio Linares]

Enrico,

Are you using Borland ?

According to Tim this may be only related with MSVC

[Enrico Maria Giordano]

Antonio,

Yes, I'm using BCC690 but how the C compiler could make any difference? I don't understand...

EMG

[Antonio Linares]

Enrico,

Its not the C compiler itself, but several modifications that MS does to the final EXE (segments organization, etc.)

I have seen that inspecting the EXEs with PEInfo and similar apps

https://bitbucket.org/fivetech/fivewin-contributions/downloads/peinfo.exe

[Enrico Maria Giordano]

Antonio,

I still don't understand...

Anyway, what is the solution?

EMG

[Antonio Linares]

Enrico,

Never mind

First of all we need to be able to reproduce it. Up to now I haven't be able to reproduce it. Here it is working fine

[TimStone]

Antonio,

It will not build with that in the .rc file because Visual Studio creates it's own manifest file, and thus the conflict throws a linker error.

Tim

[nageswaragunupudi]

Antonio,

Yes, I'm using BCC690 but how the C compiler could make any difference? I don't understand...

EMG

Off-topic.
I am using bcc582.
Are there any advantages in using bcc690 and where can I get it from?

[Richard Chidiak]

Tim

I remember a similar problem in folders when the dialog had a "Capion" clausure, try to remove it and see if it makes a difference.

viewtopic.php?f=3&t=27601&p=154059&hilit=caption#p154059

Hth

Richard

[Enrico Maria Giordano]

Rao,

Off-topic.
I am using bcc582.
Are there any advantages in using bcc690 and where can I get it from?

At least it's an updated version. You can try it from here:

http://www.whosaway.com

EMG

[TimStone]

The issue becomes more complex. I began to wonder if perhaps the control should be True for TRANSPARENT ( the autocheckbox ) so I tried clicking on that property. Visual Studio wants to rebuild the .rc, and does a nice job of it, but then when trying to build it can't find the definitions for WS_POPUP which is a standard windows style.

So ... to use the windows controls, there must be a library I am missing, or an include file, for compiling the .rc within Visual Studio. More likely there is a configuration property that I am missing which would automatically bring in the include files.

If I use Windows.h ( which the builder eliminates ), it has a parameter RC_INVOKED which is evidently set by NOWINRES but I can't see where to set this.

Antonio, thoughts on this ? I know one other thread said we couldn't use the Resource Editor in VS 2013, but we should be able to get past this. It's a good tool.

Tim

[Antonio Linares]

Tim,

I just tested this example using FWH 15.02 and FWH\samples\buildh32.bat:

test.prg

Code: Select all | Expand

#include "FiveWin.ch"

function Main()

   local oDlg, lValue := .T.

   DEFINE DIALOG oDlg RESOURCE "test"

   REDEFINE CHECKBOX lValue ID 100 OF oDlg

   ACTIVATE DIALOG oDlg CENTERED

return nil

test.rc

Code: Select all | Expand

#include <windows.h>

LANGUAGE 0, SUBLANG_NEUTRAL
test DIALOG 0, 0, 255, 138
STYLE DS_3DLOOK | DS_CENTER | DS_MODALFRAME | DS_SHELLFONT | WS_CAPTION | WS_VISIBLE | WS_POPUP | WS_SYSMENU
CAPTION "Dialog"
FONT 8, "Ms Shell Dlg"
{
    AUTOCHECKBOX    "Checkbox", 100, 94, 50, 48, 8, 0, WS_EX_LEFT
    DEFPUSHBUTTON   "OK", 1, 67, 112, 50, 14, 0, WS_EX_LEFT
    PUSHBUTTON      "Cancel", 2, 128, 112, 50, 14, 0, WS_EX_LEFT
}

And it is working fine. Could you try this example there ? thanks

[TimStone]

Antonio,

1) Please remember that I am trying to get this working with Visual Studio 2013 itself ( the IDE ). Using a make file is different. Especially for the future, we want ALL settings correct in VS 2013 ( and soon 2015 ).

2) With that said, I looked at your build file and noticed that I have several additional libraries linked in:

hbssl.lib, hbtipssl.lib, and ws2_32.lib are needed for email
libeay32.lib and ssleay32.lib are necessary for additional functionality

gtwin.ib, libcmt.lib, libcpmt.lib and oldnames32.lib are ones you recommended previously. I'm wondering if they are still needed, and perhaps one of them is conflicting here.

Tim

[TimStone]

Antonio,

I've spent the day researching this and testing.

1) If I build the project inside UE Studio, using their .mak system, the controls work properly.
2) If I build the project inside MSFT Visual Studio 2013 with it's IDE, the controls behave as noted
3) The .prg, .rc, and .lib files used are exactly the same in both cases.

Thus, the problem has to be in the Properties of the VS 2013 build. Some option is different, but I have been unable to determine what it is.

I will look at it further tomorrow. If you have any ideas please let me know. Perhaps you can try building it within VS in the same way using one of your samples and see what you get. If it works properly, you could send me the settings you are using. I think what I have now is pretty much what you shared when you built the initial projects using it.

Tim

[Antonio Linares]

Tim,

Solved. All you have to do is add

1 24 WindowsXP.Manifest to your resource file