flat assembler - FASM x64 Win32 GUI Controls — Custom Draw ListView Example

Index > Tutorials and Examples > FASM x64 Win32 GUI Controls — Custom Draw ListView Example

Goto page Previous 1, 2

Author

Thread

revolution
When all else fails, read the source

Joined: 24 Aug 2004
Posts: 21104
Location: In your JS exploiting you and your system

revolution 16 Aug 2026, 12:10

jochenvnltn wrote:

Can i help it that it's not in the INC files ?

It is an uphill battle to get people to change their .inc files.

See this old thread. Good work done there, but it never gained traction.

Better IMO, to do as suggested above to create a new set of files and bypass the .inc files that come with fasm.

16 Aug 2026, 12:10

jochenvnltn

Joined: 15 Jul 2011
Posts: 108

jochenvnltn 16 Aug 2026, 12:25

revolution wrote:

jochenvnltn wrote:
Can i help it that it's not in the INC files ?
It is an uphill battle to get people to change their .inc files.

See this old thread. Good work done there, but it never gained traction.

Better IMO, to do as suggested above to create a new set of files and bypass the .inc files that come with fasm.

I am not the creator of FASM ! I should not bypass anything because you are to lazy to update your own API files with the latest versions ! Also i remember that long ago someone here on the board wrote a program to walk the windows DLL's to create the INC files for you. As Windows gets older, more and more new API are added to it's DLL's... Is that so strange ?

16 Aug 2026, 12:25

bitRAKE

Joined: 21 Jul 2003
Posts: 4607
Location: vpcmpistri

bitRAKE 16 Aug 2026, 20:53

I've lost track of how many times I've iterated on different API file scenarios -- searching is in environment order. So, stacking paths seems very natural:

Code:

set "INCLUDE=C:\includes\vulkan;%INCLUDE%"

Automated scripts only make sense to me if external functions are recorded at assemble-time. Which is completely possible! Total automatic API includes - no micro-management in source. Modern Windows has API support layers. So, even the automatic needs layer selection or legacy assumption.

16 Aug 2026, 20:53

jochenvnltn

Joined: 15 Jul 2011
Posts: 108

jochenvnltn 17 Aug 2026, 19:23

revolution wrote:

Maybe some include missing?

Code:

$ fasm -m 99999 ListView_1.7_PROCESSLIST.asm
flat assembler  version 1.73.31  (99999 kilobytes memory)
ListView_1.7_PROCESSLIST.asm [58]:
        invoke SetProcessDpiAwarenessContext, DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE_V2
~/fasm/include/win64wx.inc [10] invoke [0]:
  \{ \common fastcall [proc],arg \}
~/fasm/include/win64wx.inc [129] fastcall [117]:
             match args,list \\{ fastcall proc,args \\}
~/fasm/include/win64wx.inc [129] match [0]:
             match args,list \\{ fastcall proc,args \\}
~/fasm/include/macro/proc64.inc [300] fastcall [292]:
    call proc
processed: call[SetProcessDpiAwarenessContext]
error: undefined symbol 'SetProcessDpiAwarenessContext'.

Description:	From your own board uploaded here more than a decade ago ! I can't find the original thread where i downloaded it from. This will also change the default FASM install, but without the need of you taking the effort of adding a few API yourself ;)	Download
Filename:	[PE Export Table Dump] etl.zip
Filesize:	2.43 KB
Downloaded:	32 Time(s)

17 Aug 2026, 19:23

Goto page Previous 1, 2

< Last Thread | Next Thread >

Forum Rules:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum