Seventeenth post of a series, translated from the "WinDev and PowerBASIC",
to explain the use of GDImage64 in procedural* programming mode with Visual Studio 2022.

About Tutor_17
This is a C++ transcription of a PowerBASIC demo written in 2009 with the official release of GDImage 5.00.
It was the first version able to mix 2D and 3D OpenGL into the same graphic control.
The application itself is skinned with WinLIFT, and share the same background wallpaper with all child controls.

The Cube
Is using 3 OpenGL cubes (1 main and 2 clones), with each face using a distinct texture.

Wallpaper background
You can click with the right mouse button on the main cube, to change the wallpaper background.

WinLIFT 6.00
Is an experimental version converted to VS2022, the whole code has been revisited for further code size reduction.
New API skMinTrackSizeX ();
return the minimum width size of main window once skinned.
New API skMinTrackSizeY ();
return the minimum height size of main window once skinned.
New API skUseThisBackground(IN HWND hWnd, IN WCHAR* zItem);
To change on the fly the wallpaper background without using the top left icon,
even when the .sks parameter is disabled "BACKGROUNDPATH,      resource\Background"
The skInitEngine API has an extra optional parameter:
skInitEngine (IN WCHAR* zSkinFile, IN WCHAR* zUserKey, IN HWND hParent);

GDImage 7.16
Is an experimental version converted to VS2022, with a new API named "ZD_GLtoBitmap" to dynamically turn the OpenGL context into a ZOBJECT sprite bitmap (see the RenderAnimation() procedure).


Last but not least,
the size of the standalone binary EXE is only 17 Kb.


   
* procedural programming mode, is based on direct use of the FLAT API (Windows SDK) that is the core meat of the OS.

Thanks for removing the .vs folder because I had problems opening the Tutor solution as your .vs point to path of project files on your machine which are different from mine. I always have to delete .vs folder before opening the solution to avoid the opening problem. .vs is to store the intellisense information which can be regenerated.

Here is the Debug version, without the .vs hidden folder.

About the correct Debug settings, open the "Project" --> "Properties" to figure what to do.
The important parts are in these sections
> C/C++
> Linker
 Starting from now,, I shall try to add a Debug version in new tutors.

However keep in mind that the settings for Debug and Release are very different.

Have a look at these settings to produce standalone EXE without using the CRT.
http://www.objreader.com/index.php?topic=335.msg6044#msg6044

Currently in GDImage the WCHAR constants are defined like this

static WCHAR*   $NULL               = L"";
static WCHAR*   $SPACE              = L" ";
static WCHAR*   $CHARNULL           = L"\0";
static WCHAR*   $COMMA              = L",";
static WCHAR*   $ANTI               = L"\\";
static WCHAR*   $DOT                = L".";
static WCHAR*   $SAVE_EXT           = L"PNG,JPG,BMP,TIF,GIF,EMF,WMF";
static WCHAR*   $FILTER             = L"*.PNG (Portable Network Graphic)|*.PNG|*.JPG (JPEG File Interchange)|*.JPG;*.JPEG|*.BMP (Windows Bitmap)|*.BMP|*.TIF (Tagged Image File)|*.TIF;*.TIFF|";
static WCHAR*   $JPG_PNG            = L"JPG,PNG";
static WCHAR*   $ZLIM               = L"|";
static WCHAR*   $LF                 = L"\n";
static WCHAR*   $RegistryKey        = L"SOFTWARE\\GDImage";
static WCHAR*   $RegistryPath       = L"LoadDefaultPathName";

const int SCROLLBAR_NONE     = 0;
const int SCROLLBAR_VERT     = 1;
const int SCROLLBAR_HORZ     = 2;
const int SCROLLBAR_BOTH     = 3;

const int CHECK_FOR_MULTISAMPLE     = TRUE;
const int WGL_SAMPLE_BUFFERS_ARB    = 0x2041;
const int WGL_SAMPLES_ARB           = 0x2042;
const int WGL_DRAW_TO_WINDOW_ARB    = 0x2001;
const int WGL_SUPPORT_OPENGL_ARB    = 0x2010;
const int WGL_ACCELERATION_ARB      = 0x2003;
const int WGL_FULL_ACCELERATION_ARB = 0x2027;
const int WGL_COLOR_BITS_ARB        = 0x2014;
const int WGL_ALPHA_BITS_ARB        = 0x201B;
const int WGL_DEPTH_BITS_ARB        = 0x2022;
const int WGL_STENCIL_BITS_ARB      = 0x2023;
const int WGL_DOUBLE_BUFFER_ARB     = 0x2011;

Hi Patrice,

I cannot build in debug x64 x86 build and release x86 build of your Tutor 14. There are some errors and many errors due to the invalid WCHAR* conversion. If I try out to write some GDImage code, I am not going to start from scratch; I am going to take your existing Tutor 14 code and remove the code which I do not need to write a zooming photo viewer application. I must be able to debug using the debug build when something goes wrong. Right now, I am unable to build a debug build.

In 1990s, using Turbo C. I was able to write something like

char* text = "Good Holidays";
Starting from the early 2000s, I was not allowed to do this. A const keyword must be used.

const char* text = "Good Holidays";
For example, given the MyFunction below

void MyFunction()
{
    char* text = "Good Holidays";
    // code that modifies the content which text is pointing to.
}
If MyFunction modifies "Good Holidays" which is a static memory area, then the next time, MyFunction is called again, the text won't be "Good Holidays". This is why const must be used for string literals. I never verify if this is true because it is an industry practice that every C/C++ developer and I has to follow.

Assigning char* to const char* is allowed.

char* text = ???
const char* text2 = text; // allowed
but the opposite is not allowed by the compiler.

const char* text = ???
char* text2 = text; // error: not allowed.
Can you modify all the in parameters of WCHAR* to const WCHAR* in GDImage? This is to cut down the compile errors I have to fix when compiling in debug build. The side effort of this modification is you cannot modify const WCHAR* argument inside your function.

What do you think?