It's not fancy but it draws lines over 1 pixel in thickness.

'draw_lineFT

' By James D. Jarvis August 21,2023

'draw a line with a defined thickness

Screen _NewImage(400, 500, 32)

Dim Shared tk&

tk& = _NewImage(3, 3, 32)

'*********************************************

'demo

'*********************************************

x1 = 100: y1 = 100

x2 = 300: y2 = 300

x3 = 100: y3 = 200

lineFT x1, y1, x2, y2, 10, _RGB32(200, 100, 0)

lineFT x2, y2, x3, y3, 10, _RGB32(200, 100, 0)

lineFT x1, y1, x3, y3, 10, _RGB32(200, 100, 0)



'*************** routines **********************

'lineFT - draw a thick line constructed from 2 mapped triangles

'DegTo - return angle (in degrees) between two points , used as an internal function in lineFT

'*********************************************

Sub lineFT (x1, y1, x2, y2, thk, klr As _Unsigned Long)

    'draw a line of thickness thk on color klr from x1,y1 to x2,y2

    'orientation of line is set in the middle of line thickness

    _Dest tk&

    Line (0, 0)-(2, 2), klr, BF 'set the color for the line

    _Dest 0

    cang = DegTo(x1, y1, x2, y2) 'get the angle from x1,y1 to x2,y2

    ta = cang + 90

    tb = ta + 180

    tax1 = x1 + (thk / 2) * Cos(0.01745329 * ta)

    tay1 = y1 + (thk / 2) * Sin(0.01745329 * ta)

    tax4 = x1 + (thk / 2) * Cos(0.01745329 * tb)

    tay4 = y1 + (thk / 2) * Sin(0.01745329 * tb)

    tax2 = x2 + (thk / 2) * Cos(0.01745329 * ta)

    tay2 = y2 + (thk / 2) * Sin(0.01745329 * ta)

    tax3 = x2 + (thk / 2) * Cos(0.01745329 * tb)

    tay3 = y2 + (thk / 2) * Sin(0.01745329 * tb)

    _MapTriangle (0, 0)-(0, 2)-(2, 0), tk& To(tax1, tay1)-(tax2, tay2)-(tax4, tay4)

    _MapTriangle (0, 0)-(0, 2)-(2, 0), tk& To(tax2, tay2)-(tax3, tay3)-(tax4, tay4)

End Sub

Function DegTo! (x1, y1, x2, y2)

    '========================

    ' returns an angle in degrees from point x1,y1 to point x2,y2

    aa! = _Atan2((y2 - y1), (x2 - x1)) / 0.01745329

    DegTo! = aa!

End Function

https://10print.org/10_PRINT_121114.pdf?...786I9Um03Q

Hi.

I've added some handy stuff to my library for dealing with arrays:
https://github.com/grymmjack/QB64_GJ_LIB/tree/main/ARR

What is in the library? Read the README.md, but:

TYPES SUPPORTED:

• _BYTE
  
• _UNSIGNED _BYTE
  
• INTEGER
  
• _UNSIGNED INTEGER
  
• _INTEGER64
  
• _UNSIGNED _INTEGER64
  
• LONG
  
• _UNSIGNED LONG
  
• SINGLE
  
• DOUBLE
  
• _FLOAT
  
• STRING
  

an update of an older sub to draw filled polygons using _maptriangle . This one is faster than the earlier version (polyT) and includes options for rotation, horizontal and vertical scaling, and a border.

'draw_polyFT

' by James D.  Jarvis  , August 20,2023

'draw filled  polygons

'

'HEADER

Dim Shared xmax, ymax

xmax = 800: ymax = 500

Screen _NewImage(xmax, ymax, 32)

Dim Shared pk& 'must be included in a program that uses polyFT

pk& = _NewImage(3, 3, 32) 'must be included in a program that uses polyFT



'======================================

' demo

'======================================

' This demo draws 64000 random polygons, and then clears the screen and draws a handful of polygons  rotating



Randomize Timer



t1 = Timer

For reps = 1 To 64000

    polyFT Int(Rnd * xmax), Int(Rnd * ymax), Int(3 + Rnd * 20), Int(3 + Rnd * 12), Int(Rnd * 60), Int(1 + Rnd * 3), Int(1 + Rnd * 3), _RGB32(Int(Rnd * 256), Int(Rnd * 256), Int(Rnd * 256)), _RGB32(Int(Rnd * 256), Int(Rnd * 256), Int(Rnd * 256))

Next reps

t2 = Timer

Print "That took "; t2 - t1; " seconds to draw 64000 polygons"

Sleep

rtn = 0

Do

    _Limit 60

    Cls

    Print "Press <ESC> to quit>"

    polyFT 100, 100, 40, 3, rtn, 1, 1, _RGB32(100, 200, 50), 0

    polyFT 200, 100, 40, 4, 45 + rtn, 1, 1, _RGB32(100, 200, 250), 0

    polyFT 300, 100, 40, 5, rtn, 1, 1, _RGB32(200, 100, 250), 0

    polyFT 400, 100, 40, 6, rtn, 1, 1, _RGB32(100, 250, 150), 0

    polyFT 500, 100, 40, 7, rtn, 1, 1, _RGB32(150, 200, 200), 0

    polyFT 600, 100, 40, 8, 22.5 + rtn, 1, 1, _RGB32(200, 200, 0), 0

    _PrintString (100 - (_PrintWidth("Triangle")) / 2, 160), "Triangle"

    _PrintString (200 - (_PrintWidth("Square")) / 2, 160), "Square"

    _PrintString (300 - (_PrintWidth("Pentagon")) / 2, 160), "Pentagon"

    _PrintString (400 - (_PrintWidth("Hexagon")) / 2, 160), "Hexagon"

    _PrintString (500 - (_PrintWidth("Heptagon")) / 2, 160), "Heptagon"

    _PrintString (600 - (_PrintWidth("Octagon")) / 2, 160), "Octagon"

    rtn = rtn + 1: If rtn > 360 Then rtn = 0

    _Display 'for smooth display

Loop Until InKey$ = Chr$(27)



'==========================================================================

'subroutines

'

'  polyFT    draw a filled polygon

'

' setklr    is a sub to build the color image used by triangles in  polyFT

'====================================== ==================================

Sub polyFT (cx As Long, cy As Long, rad As Long, sides As Integer, rang As Long, ww, vv, klr As _Unsigned Long, lineyes As _Unsigned Long)

    'draw an equilateral polygon using filled triangle for each segment

    'centered at cx,cy to radius rad of sides # of face rotated to angle rang scaled to ww and vv of color klr and lineyes if there is an outline, a value 0 would create no outline

    setklr klr

    Dim px(sides)

    Dim py(sides)

    pang = 360 / sides

    ang = 0

    For p = 1 To sides

        px(p) = cx + (rad * Cos(0.01745329 * (ang + rang))) * ww

        py(p) = cy + (rad * Sin(0.01745329 * (ang + rang))) * vv

        ang = ang + pang



    Next p

    For p = 1 To sides - 1

        _MapTriangle (0, 0)-(0, 2)-(2, 0), pk& To(cx, cy)-(px(p), py(p))-(px(p + 1), py(p + 1))

        If lineyes > 0 Then Line (px(p), py(p))-(px(p + 1), py(p + 1)), lineyes

    Next p

    _MapTriangle (0, 0)-(0, 2)-(2, 0), pk& To(cx, cy)-(px(sides), py(sides))-(px(1), py(1))

    If lineyes > 0 Then Line (px(sides), py(sides))-(px(1), py(1)), lineyes







End Sub

Sub setklr (klr As Long)

    'internal routine to setup an image to copy a colored triangle from in the color klr

    'called by polyT

    _Dest pk&

    Line (0, 0)-(2, 2), klr, BF

    _Dest 0

End Sub

And what the hell is compiler dead space, you may ask.

People who write compilers have a habit of being lazy, very lazy.  The coding part (your executable) will be the same from computer to computer.  This is true as long as the compilers are the same version.  So code from one computer coding will have the same SHA hash value as the next.  What will change is data and string areas.  The same areas which contain uninitialized memory for storage.  A dumb compiler will just assign the space.  Which shows up as a random segment of the compiling computers memory.  Looking at the EXE code in RAW mode may show some interesting information.  A smart compiler will zero out all data and string areas before sending it to the linker/exe module.

So is QB64pe using a smart or dumb compiler/linker ?  The reason I am asking is "If I send someone source code and a SHA of the resulting EXE."  I can determine if compilers are the same version on my computer and his/her computer.  Thus resolving compiler issues before they become a problem.  AKA: They said they were up to date, only to find they are 3 versions behind.

Thanks.
Nobody here may have an answer.  This a very inside question about the GCC compiler QB64pe is using.

a little routine and associated demo for drawing a filled hex.

'Fhex

'by James D. Jarvis August 19,2023

'draw a filled hex

'demo code

Screen _NewImage(500, 500, 32)

rr = 200

For d = 1 To 10

    fcirc 250, 250, rr, _RGB32(200, 200, 0)

    fhex 250, 250, rr, _RGB32(200, 100, 100)

    rr = rr * .86

Next d

For a = 60 To 360 Step 60

    ang_line 250, 250, 200, a, _RGB32(250, 0, 0)

Next a



hx = 60: hy = 60: hl = 12

fhex hx, hy, hl, _RGB32(100, 100, 100)

For ha = 30 To 390 Step 60

    hx = 60 + (hl * 1.9) * Cos(0.01745329 * ha)

    hy = 60 + (hl * 1.9) * Sin(0.01745329 * ha)

    fhex hx, hy, hl, _RGB32(ha / 2, ha / 2, ha / 20)

Next ha



Sub fhex (cx As Long, cy As Long, r, klr As _Unsigned Long)

    'draw a hex to radius r filled with color klr centeted on cx,cy

    rcheck = ((r * .867) * (r * .867))

    For dY = -r To r

        If dY * dY < rcheck Then

            dx = r - Abs(dY / _Pi * 1.81)

            Line (cx - dx, dY + cy)-(cx + dx, dY + cy), klr, BF

        End If

    Next dY

End Sub





'ang_line and fcirc included for demo not needed for fhex itself

Sub ang_line (sx, sy, lnth, ang, klr As _Unsigned Long)

    'draw a line lnth units long from sx,sy at anlge ang measures in degrees, 0 deg is out along X axis

    nx = sx + lnth * Cos(0.01745329 * ang)

    ny = sy + lnth * Sin(0.01745329 * ang)

    Line (sx, sy)-(nx, ny), klr



End Sub

Sub fcirc (CX As Long, CY As Long, R, klr As _Unsigned Long)

    'draw a filled circle with the quickest filled circle routine in qb64, not my development

    Dim subRadius As Long, RadiusError As Long

    Dim X As Long, Y As Long

    subRadius = Abs(R)

    RadiusError = -subRadius

    X = subRadius

    Y = 0

    If subRadius = 0 Then PSet (CX, CY): Exit Sub

    Line (CX - X, CY)-(CX + X, CY), klr, BF

    While X > Y

        RadiusError = RadiusError + Y * 2 + 1

        If RadiusError >= 0 Then

            If X <> Y + 1 Then

                Line (CX - Y, CY - X)-(CX + Y, CY - X), klr, BF

                Line (CX - Y, CY + X)-(CX + Y, CY + X), klr, BF

            End If

            X = X - 1

            RadiusError = RadiusError - X * 2

        End If

        Y = Y + 1

        Line (CX - X, CY - Y)-(CX + X, CY - Y), klr, BF

        Line (CX - X, CY + Y)-(CX + X, CY + Y), klr, BF

    Wend

End Sub

This was supposed to go in the Museum a long time ago. However, I never got to re-implementing the assembler routines that this uses... until now.
I've included the assembly sources as comments in General.bas. Below those comments you can find the QB64 function ports.

From MS PDS 7.1 Getting Started docs:

Quote:User Interface Toolbox

With the new user interface code samples, you can design your own user interface using
BASIC procedures. The code samples in this toolbox give you complete control of character-
based window interfaces. For example, you could write a BASIC program with multiple
windows, menu bars, dialog boxes, and mouse interaction. For more information about the User
Interface toolbox, see Part 3 of the BASIC Language Reference.

Attached Files

  PDSUITB64.zip (Size: 45.29 KB / Downloads: 50)

Since I've started diving into API calls I figured a dedicated thread for API related questions would be better.

Here is my first question.

In the Wiki here: https://qb64phoenix.com/qb64wiki/index.p...ndow_Focus

It's shown how to determine the foreground window (the one in focus).

The Microsoft docs for GetForegroundWindow are located here: https://learn.microsoft.com/en-us/window...oundwindow

I noticed in the Wiki example that GetForegroundWindow is declared as an _OFFSET (%&). How was this determined? Looking at the Microsoft docs there is no indication of the type of variable returned. With other window handle (hWnd) related functions I've noticed a variable type of LONG is used. Why was _OFFSET needed here instead of LONG?

This has me confused. Any clarification would be greatly appreciated.

First, I'm a complete noob to API calls so this just may be my ignorance on the subject.

@SpriggsySpriggs suggested I use GetClientRect to get the client area coordinates of a Window. So I set up some code below to investigate.

However, no matter what size the screen is set to the return values of the RECT are always 0,0 - 640,400.

This makes me think that perhaps _WINDOWHANDLE is pointing to an underlying console window instead of the currently visible window?

Am I correct in my thinking, or am I using _WINDOWHANDLE incorrectly?

I am tweaking dbox pset version with less bubble release each frame for consistent fountain pattern (same tweak as in Proggies) PLUS a wider viewing frame that spreads Bell Curve a little better:

https://qbjs.org/index.html?code=J09wdGl...A1FTdWIKCg==