Demo #3 of my "home grown" GUI. (Radio buttons and check boxes)

[TBMan]

I'm progressing with my new GUI which is modeled after the PTCGraph/Borland Graph unit.  This demo shows the
group control that can own radio buttons or checkboxes.

The lag you see in the graphics is caused by the video recording software.

https://youtu.be/1qr39Ckkrf4

My library consists of several units:

win_graph - graph mode initialization, page flipping and primitives that either update the active page immediately or
with similar procedure names do not cause the page to be updated.

win_crt (mouse and keyboard polling)

lgw_object - OOP library. I also have LG_Object OOP library. The LGW_Object unit is based on it, with slight modifications for the new units I've listed here.

win_fonts - a list of windows fonts as unicodestring constants

win_colors - colorref constants

lgw_types - basic misc types, right now just a "wrect" type (x1,y1,x2,y2 of integer)

lgw_procs - often used misc stuff

[AlexTP]

so part of units have lgw_ prefix and others have the win_ prefix. why not having the single prefix lgw_? win+'_' prefix is similar to 'win' OS usual units (winTypes, winProcs), better lgw_. or for example "tbman_".

[TBMan]

so part of units have lgw_ prefix and others have the win_ prefix. why not having the single prefix lgw_? win+'_' prefix is similar to 'win' OS usual units (winTypes, winProcs), better lgw_. or for example "tbman_".

Level 1 units: Win_graph and win_crt call the Windows API directly. Win_Fonts are constants of Windows font names. Win_colors are COLORRefs constants used in calls to Windows API graphics.

Level 2 units: The lgw units use level 1 units. The level 2 units don't make Windows API calls directly. With just small modifications the lgw units could use ptcgraph.

So actually Win_fonts and Win_colors could have been level 1, win_graph and win_crt level 2 and the lgw units as level 3. Win_fonts and Win_colors could have just been include files in win_graph too.