Author Topic: 64 bit Gui_Demo issues  (Read 539 times)

jcfuller

  • Sr. Member
  • ****
  • Posts: 260
    • View Profile
Re: 64 bit Gui_Demo issues
« Reply #30 on: November 02, 2020, 10:40:18 AM »

I finished going through all the gui demos and  posted all info where a BCX source revision might be needed.
All were tested with Clang-cl. Some (not all) tested with NUWEN and TDMGCC.
Waiting on BCX 7.6.1 now

James


MrBcx

  • Administrator
  • Hero Member
  • *****
  • Posts: 680
    • View Profile
Re: 64 bit Gui_Demo issues
« Reply #31 on: November 02, 2020, 12:15:33 PM »
JC -- I uploaded 761, so that you can move forward.

You said,  "...  posted all info where a BCX source revision might be needed."

Where did you post that info or are you referring to what you posted since 760?


jcfuller

  • Sr. Member
  • ****
  • Posts: 260
    • View Profile
Re: 64 bit Gui_Demo issues
« Reply #32 on: November 02, 2020, 12:17:46 PM »
What I posted since 7.6.0.
I revised my version per fixes you posted but I would rather be sure and use the real macoy.

James

Robert

  • Hero Member
  • *****
  • Posts: 527
    • View Profile
Re: 64 bit Gui_Demo issues
« Reply #33 on: November 05, 2020, 05:22:52 PM »
Kevin,
  I'm not sure if this is me or the BCX dpi settings or just the wrong sizes to begin with?
Editctrl.bas

James

Hi James:

Have you got -D_WIN32_WINNT=0x0501 on your command line? 600 and up or nothing, which defaults to 600?, may truncate the form size because of the change in borders after Vista. I stll like the idea of calculating BCX_FORM from the client area size as Patrice Terrier advocates. Not sure what José does.

jcfuller

  • Sr. Member
  • ****
  • Posts: 260
    • View Profile
Re: 64 bit Gui_Demo issues
« Reply #34 on: November 06, 2020, 03:59:41 AM »

Hi James:

Have you got -D_WIN32_WINNT=0x0501 on your command line? 600 and up or nothing, which defaults to 600?, may truncate the form size because of the change in borders after Vista. I stll like the idea of calculating BCX_FORM from the client area size as Patrice Terrier advocates. Not sure what José does.

Robert,
  I use -DWINVER=0x601.
I agree on calculating from the client area size and believe it should be added to BCX.
Here is an upcoming CWindow example.

James
Code: [Select]
$PP
$USE USE_AfxRemoveWindowStyle
$Include <Afx/CWindow.bi>
$Include <BCppXLib.bi>
'==============================================================================
Function WinMain()
    Dim As int iRetVal
    Dim As HWND hWin,hButton
    Raw As CWindow pWindow
    hWin = pWindow.Create(NULL, "CWindow with a button", &WndProc)
    AfxRemoveWindowStyle(hWin,(WS_THICKFRAME|WS_MAXIMIZEBOX ))    'no sizing or max box
    pWindow.SetClientSize(500,320)
    pWindow.Center()

    'Add a button
    hButton = pWindow.AddControl("Button",hWin , IDCANCEL, "&Close", 350, 250, 75, 23)
    iRetVal = pWindow.Do_Events()
    Function = iRetVal
End Function
'==============================================================================
CallBack Function WndProc()
    Select Case CBMSG
        Case WM_COMMAND
            Select Case CBCTL
                Case IDCANCEL
                    If CBCTLMSG = BN_CLICKED Then
                        SendMessage(CBHNDL,WM_CLOSE,0,0)
                        Exit Function
                    EndIf
            End Select
        Case WM_DESTROY
            PostQuitMessage(0)
            Exit Function
    End Select
End Function
$PP

Robert

  • Hero Member
  • *****
  • Posts: 527
    • View Profile
Re: 64 bit Gui_Demo issues
« Reply #35 on: November 06, 2020, 11:36:53 AM »

Hi James:

Have you got -D_WIN32_WINNT=0x0501 on your command line? 600 and up or nothing, which defaults to 600?, may truncate the form size because of the change in borders after Vista. I stll like the idea of calculating BCX_FORM from the client area size as Patrice Terrier advocates. Not sure what José does.

Robert,
  I use -DWINVER=0x601.
I agree on calculating from the client area size and believe it should be added to BCX.
Here is an upcoming CWindow example.

James
Code: [Select]
$PP
$USE USE_AfxRemoveWindowStyle
$Include <Afx/CWindow.bi>
$Include <BCppXLib.bi>
'==============================================================================
Function WinMain()
    Dim As int iRetVal
    Dim As HWND hWin,hButton
    Raw As CWindow pWindow
    hWin = pWindow.Create(NULL, "CWindow with a button", &WndProc)
    AfxRemoveWindowStyle(hWin,(WS_THICKFRAME|WS_MAXIMIZEBOX ))    'no sizing or max box
    pWindow.SetClientSize(500,320)
    pWindow.Center()

    'Add a button
    hButton = pWindow.AddControl("Button",hWin , IDCANCEL, "&Close", 350, 250, 75, 23)
    iRetVal = pWindow.Do_Events()
    Function = iRetVal
End Function
'==============================================================================
CallBack Function WndProc()
    Select Case CBMSG
        Case WM_COMMAND
            Select Case CBCTL
                Case IDCANCEL
                    If CBCTLMSG = BN_CLICKED Then
                        SendMessage(CBHNDL,WM_CLOSE,0,0)
                        Exit Function
                    EndIf
            End Select
        Case WM_DESTROY
            PostQuitMessage(0)
            Exit Function
    End Select
End Function
$PP

Hi James:

Did changing -DWINVER=0x601 to -D_WIN32_WINNT=0x0501 solve the problem of truncation of Editctrl.bas that you expressed in Message

https://bcxbasiccoders.com/smf/index.php?topic=391.msg1664#msg1664

Thanks for the CWindow example. Any timeline yet for the the  première début release of your BCX port?
« Last Edit: November 06, 2020, 11:51:35 AM by Robert »

jcfuller

  • Sr. Member
  • ****
  • Posts: 260
    • View Profile
Re: 64 bit Gui_Demo issues
« Reply #36 on: November 06, 2020, 01:39:35 PM »
Robert,
  No change with 0x501
BcxAdp is just about ready. I did get off on a tangent but I am back.
I suffer from the nemesis of many coders DOCUMENTATION (present company excluded).
I think I might try the XBox Game Bar. Have you any experience with it?

James


Robert

  • Hero Member
  • *****
  • Posts: 527
    • View Profile
Re: 64 bit Gui_Demo issues
« Reply #37 on: November 06, 2020, 02:03:15 PM »
Robert,
  No change with 0x501
BcxAdp is just about ready. I did get off on a tangent but I am back.
I suffer from the nemesis of many coders DOCUMENTATION (present company excluded).
I think I might try the XBox Game Bar. Have you any experience with it?

James

Hi James:

No XBox, No PS2 No Nothing. I don't play games although at times I feel like games are being played with me.

I've been playing with Visual Studio Code and the Go programming language this morning while sporadically checking your election results. This too will pass.

I wonder what's truncating the display of Editctrl.bas on your setup? I think I will fool around with that for a while and see how much I can screw up.

jcfuller

  • Sr. Member
  • ****
  • Posts: 260
    • View Profile
Re: 64 bit Gui_Demo issues
« Reply #38 on: November 06, 2020, 02:32:58 PM »
Robert,
  Xbox Gaming Bar is part of Win10 and allows you to record the actions taking place in a Window. It is aimed at pc gamers but also can be used to record  how an app is used. You can overlay voice from a mike at the same time describing your actions.
Just type xbox in the "Type here to search" box.

James

Robert

  • Hero Member
  • *****
  • Posts: 527
    • View Profile
Re: 64 bit Gui_Demo issues
« Reply #39 on: November 06, 2020, 02:45:25 PM »
Robert,
  No change with 0x501
BcxAdp is just about ready. I did get off on a tangent but I am back.
I suffer from the nemesis of many coders DOCUMENTATION (present company excluded).
I think I might try the XBox Game Bar. Have you any experience with it?

James


Hi James:

No XBox, No PS2 No Nothing. I don't play games although at times I feel like games are being played with me.

I've been playing with Visual Studio Code and the Go programming language this morning while sporadically checking your election results. This too will pass.

I wonder what's truncating the display of Editctrl.bas on your setup? I think I will fool around with that for a while and see how much I can screw up.

Hi James:
Yes, on my Windows 10 x64, changing the compiler -D_WIN32_WINNT=0x502 and linker /SUBSYSTEM:WINDOWS,5.01 to anything higher, truncates EditCtrl.bas display and I suspect all other GUIs.

I'm going up to Windows 10, -DWINVER=0x0A00 /D_WIN32_WINNT=0x0A00 for the compiler and /SUBSYSTEM:WINDOWS,6.00 for the linker for MSVC compiles. And reimplement Patrice Terrier's sizing on the Client Area for BCX_FORM. Enough of this living in the past. It's time to get with the program.

Robert

  • Hero Member
  • *****
  • Posts: 527
    • View Profile
Re: 64 bit Gui_Demo issues
« Reply #40 on: November 06, 2020, 02:50:18 PM »
Robert,
  Xbox Gaming Bar is part of Win10 and allows you to record the actions taking place in a Window. It is aimed at pc gamers but also can be used to record  how an app is used. You can overlay voice from a mike at the same time describing your actions.
Just type xbox in the "Type here to search" box.

James

Wow! Thanks for that.

jcfuller

  • Sr. Member
  • ****
  • Posts: 260
    • View Profile
Re: 64 bit Gui_Demo issues
« Reply #41 on: November 07, 2020, 03:34:43 AM »
Robert,
   I just discovered this link to an old thread in some of my notes.
http://forums.codeguru.com/showthread.php?557721-Display-issues

James

Robert

  • Hero Member
  • *****
  • Posts: 527
    • View Profile
Re: 64 bit Gui_Demo issues
« Reply #42 on: November 07, 2020, 12:12:06 PM »
Robert,
   I just discovered this link to an old thread in some of my notes.
http://forums.codeguru.com/showthread.php?557721-Display-issues

James

Hi James:

I've got this and a couple of your other threads from other forums.

Thanks