How to add a version number from the source code and.. ?

[Roger Cabo]

Hi everyone,

I saved my source files always like ProjectXYZ___ 66a.g32
The last or 3 or 4 digits after the _ identify my personal version number. In this case 66a.

Is there a way to grab this version number and pass it into the "Produktversion" number or "DateiVersion" number
at the dialogue "GFABasic32 Exe erzeugen" >  Version ?

Or is there another way?!.  So after compile.. I'd like to read out an information inside of an exe file and let display eg. "66a = was the compiled source code into Exe"

I do not want to press any button/menus  and to add any number manually in the editor, because sometimes I forget...

and then I ask me.. WTF what code version I used for the compiled exe?!

Any ideas how so solve this automatically when simply running the Code by F5?

Eg:
Open the source file,
Read the filename
Extract version number
Pass it into the gb32 code anyhow
After compile I got the info inside of the running exe.

There is one restriction..
Don't save the info into any file, try to ship the file with the package, and read from that file..

[scalion]

Hi Roger,
I think you need to use a personalised compile menu.
The gfa_compile instruction in a gll extension can help you.
Just insert automatically lines how you want using g32 source name with the gfa_insert statement before launch compilation.

[Roger Cabo]

Aug 11, 2023 13:18:37 GMT 1 scalion said:

Hi Roger,
I think you need to use a personalised compile menu.
The gfa_compile instruction in a gll extension can help you.
Just insert automatically lines how you want using g32 source name with the gfa_insert statement before launch compilation.

Thank you very much!

Another question:

It's possible to remove a file from the inline resource ... after I used Gfa_CopyFile Source$, Dest$?
Didn't find any GFA_InlFileDelete(":" or index) or similar.

A workaround would be:
Open the source file as binary an read through all the entries at the end
and try to find the correct name starting with ":code1" followed by a value.

:code1 32
TVnYg8VDKACIgkGIooSYsAiYqkCIsACKhBiKgIWKNoA=
:test_exe 4171, 46592
UsAUDtWMMsAAAewC1vgBAAhETGmMhEkFxgPBzjw/WqRIxQUZD+zLhETQD1SEjYSEx8YKvi/i40vH
...

[scalion]

Your workaround is the best. There's no other way apparently.

[(X)]

From Help on Gfa_InlFileName...

Gfa_CopyFile Command and Gfa_InlFileName Function

To delete an entry in the ":Files" tab specify the empty string for src$ and its resource name is dest$.

Gfa_CopyFile "", ":icodeb"


Full exerpt:

Gfa_CopyFile Command and Gfa_InlFileName Function
Syntax
Gfa_CopyFile src$, dest$

$ = Gfa_InlFileName(n%)

Description
Copies a (normal) file src$ to a new ':Files' inline resource with its name specified in dest$. The destination name must start with the semi colon : to prevent errors.

Gfa_CopyFile "e:\cparse\icodeb.ico", ":icodeb"


To delete an entry in the ":Files" tab specify the empty string for src$ and its resource name is dest$.

Gfa_CopyFile "", ":icodeb"


To copy the data from the inline resource section to a normal file use CopyFile.

CopyFile ":icodeb", "e:\cparse\icodeb.ico"


Note Most GFA-BASIC 32 functions that perform file I/O are capable of loading resources from the inline section directly. These commands and functions parse the filename for a starting colon, and assume an inline resource when found. For instance

PlaySound ":dingwav"


or

Open ":menutext" for Input As # 1


Gfa_InlFileName(n%) returns the :File name with specified index n%. When n% (1, 2, …, n) is larger than the number resources the function returns the empty string.

Remarks
GFA-BASIC 32 supports so called inline files or, otherwise put, it allows for including raw data into the project file. These raw data entities are placed in a packed, mime-encoded data format at the end of the project file.

The inline resources are maintained in the ":Files" tab in the sidebar. When you right click in the client area of the ':Files' tab, a context menu will popup to allow for data insertion by loading a file or by pasting from the clipboard. In addition, when one of the loaded GFA Editor Extensions includes the Gfa_OnDropInl event sub, the ':Files' tab will become a drag and drop window and one or more file may be dropped. Inline files can not be used in GLL and Library projects.

The inline files are accessed through the GFA-BASIC 32 Open For Input As # statement. Once opened the resources can be read as any other file, GFA-BASIC 32 will decode and unpack on the fly.

When a resource must be used in other functions (API functions for instance), the resource must be copied to disk before it can be used. To copy the file you should use CopyFile or FileCopy. Usually, the file is copied to a temporary directory and killed after it is used.

Other functions that can load inline resources are LoadPicture and LoadCursor. Inline resources that are used without GFA-BASIC 32 commands must first be copied out of the inline section to a temporary file on disk before they can be accessed. After using the external file it is then deleted (most often). See LoadBmp.

See Also
Gfa_OnDropInl, CopyFile

{Created by Sjouke Hamstra; Last updated: 07/07/2022 by James Gaite; Other Contributors: Jean-Marie Melanson}

[Roger Cabo]

Yes! Thank you... I totally over read this.

To delete an entry in the ":Files" tab specify the empty string for src$ and its resource name is dest$.
Gfa_CopyFile "", ":icodeb"


Would it possible to create a menu (Compile menu) in gll in the same way like the other ocx menus with ocxocx commands?

[(X)]

Aug 12, 2023 19:59:19 GMT 1 Roger Cabo said:

Would it possible to create a menu (Compile menu) in gll in the same way like the other ocx menus with ocxocx commands?

Well, you can create your own menu items that will appear in the Editor's "Extra" menu.  And, we can prompt the user for input...

Gfa_Menu Commands and Functions

The GFA-BASIC 32 editor extension commands: procedures/functions, can be

• executed through the use of a set of predefined keystrokes/shortcut/hotkeys or
• by selecting a custom menu item from the Extra submenu added by the coder.

But, can we create a "dialog box with edit fields and checkboxes etc"?  Hmmm...  I am not sure.  I will look into this.

[(X)]

Well, it's a start...

This procedure, when put into a GLL and called, opens a form as one would expect from the Form command.

It is unclear how we might respond to inputs as there seems to be a inability to respond to events from inside a GLL.

This is quite new to me and I am not yet sure what the limitations are.

I am getting my information from the help document under: Dialog Command.

Proc P_Dialog_Test
 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
 ' Create a Dialog 'form'...
 ' Notes:
 '     1) The Dialog command is useful for converting GFA-BASIC 16 programs and in
 '        GLL extensions.
 '     2) In a normal program use Form instead.
 '     3) OCX types are not allowed in a GLL.
 '
 Local dlgf&, s%, v%
 Const STYLE1 = WS_TABSTOP
 Const STYLE2 = BS_DEFPUSHBUTTON | WS_TABSTOP
 Const STYLE3 = BS_GROUPBOX | WS_TABSTOP
 Const STYLE4 = BS_AUTORADIOBUTTON | WS_TABSTOP
 Const STYLE5 = BS_AUTOCHECKBOX | WS_TABSTOP
 Const STYLE6 = ES_UPPERCASE | WS_BORDER | WS_TABSTOP
 Const STYLE7 = LBS_NOTIFY | LBS_SORT | LBS_STANDARD | WS_BORDER | WS_VSCROLL
 Const STYLE8 = CBS_DROPDOWN | CBS_SORT | CBS_HASSTRINGS | WS_VSCROLL
 Const WS_OVERLAPPEDWINDOW = 0xCF0000
 
 DlgBase Pixel
 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
 ' DIALOG SYNTAX:
 ' Dialog hd%,x%,y%,w%,h%,tit$ [,flag% [,height%,font$] ]
 '
 Dialog # 1, 10, 10, 400, 400, "Dlg Test", WS_OVERLAPPEDWINDOW
   EditText "Test", 100, 10, 10, 100, 30, STYLE6
 EndDialog
 ShowDialog # 1
 
 ~SetFocus(DlgItem(1, 100))
 
EndProc

[(X)]

Further reading: gfabasic32.blogspot.com/2012/02/how-gll-dialog-is-created.html

05 February 2012
How a GLL Dialog # is created

The Dialog command used in a GLL editor extension is quite different than the Dialog in a normal GB32 application. How is that possible?

When one or more GLLs is loaded in memory, the IDE assigns the compiled GLL an array with pointers to the GB32 library functions in the runtime DLL (or Ocx). This is the same array with pointers each application gets when it is loaded. This way a call to a library function like Left$(), Dialog, or OpenW, etc, will reference the appropriate function in the runtime. When the GLL is loaded some of these pointers are replaced by addresses of functions inside the IDE executable. This way when the GLL invokes a dialog related function it will call the function inside the IDE, rather than in the runtime. All the dialog box related functions and commands are replaced. Examples are the Control command and the names of standard and common controls. You'll find an overview of the valid GB32 dialog box related statements and functions in the help file.

The GB32 dialog box related statements and functions are GfaBasic for Windows 16-bit-compatible. However, the window styles specified in the Dialog # command may come as a surprise. When you omit the style GB32 uses a default window style. GB32 processes as follows:


' Create a dialog box
Local Long dwStyle = 0
Dialog # 1, 200, 200, 536, 400, "" , dwStyle
EndDialog

'
' How GB32 sets the Dialog window styles.
'
If (dwStyle %& DS_MODALFRAME) Then
Ex_Style = WS_EX_DLGMODALFRAME | WS_EX_CLIENTEDGE

Else If dwStyle == 0 ' Default Style?
dwStyle = WS_POPUP | WS_DLGFRAME | WS_BORDER
If Len(szTitle) == 0 ' No Title?
dwStyle = WS_POPUP | DS_MODALFRAME
Ex_Style = WS_EX_DLGMODALFRAME
EndIf
EndIf
'
dwStyle |= DS_SYSMODAL ' Top Most
The system creates the window (dialog box) with the WS_EX_TOPMOST style using CreateWindowEx().
The dialog has no owner or parent. 
It is modeless because it exist parallel to the Gfa_hWnd IDE window.
The WS_EX_TOPMOST style does not prevent the user from accessing other windows on the desktop.

This gives you the tools puzzle the appearance of GLL dialog box and might explain its unexpected visual style.

Posted by Sjouke Hamstra at 5.2.12
Labels: Commands, Editor Extensions

[Roger Cabo]

Thank you..

I tried several things but I do not get the IsWindow(hwnd) back from the

Dim Hwnd% = DlgItem(1, 100)
~SetFocus(Hwnd%)
MsgBox IsWindow(Hwnd%)

Also:

Do
   Sleep()
Loop Until MouseK = 1

As long as you can't build a loop, you can not react to anything, unfortunately..

[Roger Cabo]

Type POINTAPI
   x As Long
   y As Long
End Type

Declare Function GetCursorPos Lib "user32" (lpPoint As POINTAPI) As Long
Declare Function ScreenToClient Lib "user32" (ByVal hwnd As Long, lpPoint As POINTAPI) As Long

Function HoleMausPositionFuerFenster(ByVal hwnd As Long) As POINTAPI
   Dim pt As POINTAPI
   GetCursorPos pt
   ScreenToClient hwnd, pt
   HoleMausPositionFuerFenster = pt
End Function

Perhaps it possible to get the control by hWnd and be able to access it anyhow.
All DoEvents, Peek.. etc cause a Fatal Error.