Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
31
The concept / Re: Tutor-17 (C++ VS2022 GDImage64.dll tutorial)
« Last post by Patrice Terrier on September 03, 2023, 08:06:20 am »
Here it is now, I did a few changes in the new WinLIFT VS2022 experimental version.  ;)
32
The concept / Re: Tutor-17 (C++ VS2022 GDImage64.dll tutorial)
« Last post by Shao Voon Wong on September 03, 2023, 06:55:33 am »
I do not see any upload in the first post of this thread.
33
The concept / Re: Tutor-17 (C++ VS2022 GDImage64.dll tutorial)
« Last post by Patrice Terrier on September 02, 2023, 11:04:25 am »
The first post of this thread has been updated with a new WinLIFT64.dll using fully qualified paths that should work in debug mode.
34
The concept / Re: Tutor-17 (C++ VS2022 GDImage64.dll tutorial)
« Last post by Patrice Terrier on September 02, 2023, 09:00:28 am »
I think to remember that GDIPLUS needs a fully qualified path, and since the .sks file has been moved to the resource folder, it is not found in debug mode, because the active folder is different.

I shall use zTrace to answer this question, and post a new WinLIFT version that will solve this debug issue.
35
The concept / Re: Tutor-17 (C++ VS2022 GDImage64.dll tutorial)
« Last post by Patrice Terrier on September 02, 2023, 08:54:35 am »
Good question ...

Probably because the current folder used in debug mode is not the same than in release mode.

I could check in WinLIFT the complete folder path, and see what is different in debug mode than in release mode.

BTW, in this tutor I am detecting the different cube faces using a single color, see in the Drawcube(Hitdetection) procedure glColor4ub(0,0,ID,255).
36
The concept / Re: Tutor-17 (C++ VS2022 GDImage64.dll tutorial)
« Last post by Shao Voon Wong on September 02, 2023, 08:42:37 am »
Hi Patrice,

Cool animation. Why is there no program window and the background is totally transparent when I run the program from Visual Studio? Is there a trick to it?

When I double-click to run the program from the release folder on File Explorer, I get to see the program window as shown on this forum thread.
37
The concept / Tutor-17 (C++ VS2022 GDImage64 tutorial)
« Last post by Patrice Terrier on September 01, 2023, 07:24:42 pm »
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.
38
The concept / Re: Tutor_14 (C++ VS2022 GDImage64 tutorial)
« Last post by Patrice Terrier on August 27, 2023, 09:25:06 am »
Quote
Can you change the IN parameters of WCHAR* type to const WCHAR* type? Windows API uses LPCWSTR which is the same as const WCHAR*

I did try to use const WCHAR*, but that is causing too much havoc into the GDImage64.dll.
Especially when a IN parameter is changed inside of the code for internal uses.

In my code IN means, this parameter is not returned to the calling code, however it could be altered for internal purpose.
In other world, IN doesn't mean it is a const parameter.

The "IN" and "OUT" macros are doing nothing, they are just used for informational purpose.
39
The concept / Re: Tutor_14 (C++ VS2022 GDImage64 tutorial)
« Last post by Shao Voon Wong on August 27, 2023, 08:33:37 am »
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.
40
The concept / Re: Tutor_14 (C++ VS2022 GDImage64 tutorial)
« Last post by Shao Voon Wong on August 27, 2023, 08:25:49 am »
Thanks Patrice,

Can you change the IN parameters of WCHAR* type to const WCHAR* type? Windows API uses LPCWSTR which is the same as const WCHAR*

For example, change from

Code: [Select]
C_IMPORT WCHAR*    ZI_SetSaveExtension (IN WCHAR* sExtension, IN long RW);
to

Code: [Select]
C_IMPORT WCHAR*    ZI_SetSaveExtension (IN const WCHAR* sExtension, IN long RW);
You also have to change in the original source code of GDImage and build a new version of GDImage64.dll.

Thanks.
Pages: 1 2 3 [4] 5 6 ... 10