Of course, all is easier if you have a Unicode dynamic string. ' ======================================================================================== ' * Returns the path of the program which is currently executing. ' ==============================================================================...

Hi Patrice, So many time coding with C++ that you seem to have forgot Basic. SUB skExePath (BYREF wszPathName AS WSTRING, BYVAL nSize AS LONG) DIM dwRes AS DWORD = GetModuleFileNameW(NULL, wszPathName, nSize) IF GetLastError = ERROR_INSUFFICIENT_BUFFER THEN EXIT SUB DIM p AS LONG = INSTRREV(wszPathN...

FreeBasic supports Unicode. What yu can't expect is that it will use the same declarations that C++. Which declaration are you using to use skCreateToolTip with FreeBasic? Show it and I will tell you how to declare it to allow passing literals and/or WSTRING.

There is an even more powerful reason why I have switched to dialogs and it is DPI awareness. Microsoft has added a bunch of new DPI functions and has updated the dialog manager to make it easier to program for high resolution monitors. The dialog manager in Windows handles how dialog boxes respond ...

You don't have to switch if you don't want/need it. You can also use Tiko with Afx instead of Afx2. I have written CDialog to replicate the PowerBasic DDT dialog engine, and DDT.inc is a thin wrapper to allow to use CDialog in a procedural way with a DDT-like syntax. Could help DDTer's to transition...

Hi Paul,

I'm using WIndows 10 and Tiko, as you know, but not with the suite but with what I have been downloading from your GitHub repository. Works perfectly in my system.

> Now, I have to figure how to post an attachment on this forum?

You can't. You have to store it in another place and provide a link to it.

Yes, I did mean fastcall. Sorry for the typo.

I'm not seeing __fastcall being used in the declares.

Hi Patrice,

Didn't you tell me that your DLL uses fastproc as the calling convention? I'm not seeing __fastproc being used in the FreeBasic declarations.

> [How] I can check if this example is working correct

Check if bSuccess is TRUE or FALSE.

Instead of first reading and then writing, write first and then read.

> but where is the main difference between dwstring and cwstr? CWSTR uses a buffer of bytes and DWSTRING a buffer of words. I wrote it to be independent of the Afx framework, to see if the developers of the compiler will incorporate something similar. Dynamic unicode strings are needed to work with ...

Please, do not mix DWSTRING with the Afx framerowrk. When using WinFBE and AFX, use CWSTR.

I have added code to check and fix broken surrogates. ' ######################################################################################## ' Platform: Microsoft Windows ' Filename: DWSTRING.inc ' Purpose: Implements a data type for dynamic null terminated unicode strings. ' Compiler: Free Basi...

No, it does not work (unless you declare the parameter as HANDLE, or ANY PTR, to force the compiler to do automatic conversion). The value must be unsigned, Instead of HANDLE, you can use ULong (in 32-bit) or ULongInt (in 64-bit). They are using negative numbers and casting them to a ULong or ULongI...

@Löwenherz These constants can be found in a VB forum and are foolish, but thanks for bothering. The correct declarations, using the MSDN syntax, are the following. #define DPI_AWARENESS_CONTEXT HANDLE #define DPI_AWARENESS_CONTEXT_UNAWARE (CAST(DPI_AWARENESS_CONTEXT,-1)) #define DPI_AWARENESS_CONTE...