QE Script for creating a bare window

[hutch--]

Dave mentioned the idea of templating in another thread so I quickly put together a script for QE that creates a bare window with a matching XML manifest file and a version control block in the RC file. This script is easy enough to modify if you understand the windows code it contains and this allows anyone to set up their own preferred base window code.

[dedndave]

that's cool as hell   :8)
it doesn't look too difficult to pick up the script stuff

[hutch--]

Dave,

On the "Script" menu in QE are two DLLs,

1. Convert Text To Script
2. Convert Binary To Script

I use these two DLLs to construct the test piece, the text DLL is what you use form normal ASCII text code and the binary DLL is what you use for a binary file like a bitmap or Icon.

The dialogs should be simple enough to use and about the only unusual thing is some of the dialogs return text in general purpose variables designated y the format "$0 $1 etc ..." If you set a named variable at the start,

STRING MyText$

You can assign a gp variable to it with script like,

MyText$ = $1

The script tends to be basic style as a dialect and it has a flexi-parser where you separate arguments by a space or ",".

You can write direct API code with it and it comes close to handling normal structures as long as they have DWORD sized members.

[baltoro]

Damn,...that IS a good idea. :bg
All this time, I've been doing it the hard way (asking dumb questions in the Campus forum, trying to get someone to write the code for me).

On a lighter note,...you could easily create a file that would generate a standard prenuptial agreement. This would be very popular with non-assembly programmers from California, and could undoubtedly generate considerable income. Think of it,...you could add an entire luxury wing to your house,...complete with world-class entertainment system, several pools and deluxe spa, servant's quarters, 24-hour gourmet kitchen (and professional staff), and, emergency medical facilities. :eek

[hutch--]

Well, notwithstanding such serious considerations, here is another QE script that will build a simple 2 button dialog. The dialog can be edited with Ketil Olsen's resedit and seems to work fine but the main action is you can easily modify the template to change the code design.

[ToutEnMasm]

it doesn't look too difficult to pick up the script stuff

I agree

open the masm32\menus.ini
and add this line
[&Code]
          Create New &Window,{e}\script\makewin.qse

[dedndave]

i will try that, Yves   :U

in the mean time, that brings up an interesting question for Hutch...

this is a list of files in the masm32 folder (fresh install)
which files belong to QE ?????
can they be moved, or are they "hard-wired" ???
i'd like to put QE in it's own folder, if that's possible

Code Select Expand

07/31/2007  04:19 PM               729 makelibs.bat
07/30/2008  11:06 PM                40 qeint.bin
07/29/2008  11:08 PM                36 qetxt.bin
09/27/2007  11:35 PM            21,118 topgun.chm
07/30/2008  07:04 PM            25,088 qsc.dll
08/09/2008  08:07 PM            28,160 se.dll
07/20/2008  06:57 AM            19,456 menuedit.dll
06/26/2008  05:51 AM            19,244 topgun.exe
11/12/2006  04:28 AM             7,168 maketbl.exe
02/27/2006  09:26 PM             8,192 fda2.exe
09/18/2006  04:15 AM            15,900 tproc.exe
09/18/2006  04:18 AM            17,500 mnutoasm.exe
09/28/2007  07:39 AM             3,072 tview.exe
07/27/2008  06:10 PM            12,316 procmap.exe
06/13/2007  08:01 PM             2,560 shellex.exe
08/01/2008  11:46 PM            29,308 prostart.exe
10/19/2005  04:10 AM             6,656 fda.exe
09/18/2006  04:16 AM            15,400 subclass.exe
09/18/2006  04:20 AM            20,520 ccon.exe
08/02/2008  06:54 PM            27,336 qeditor.exe
06/13/2007  07:03 PM             6,144 makecimp.exe
08/01/2008  09:14 PM            19,488 jtmake.exe
06/13/2007  07:43 PM            15,324 qetb.exe
06/13/2007  10:03 PM            13,312 bintodb.exe
09/14/2005  06:40 PM               118 pths.ini
08/01/2008  09:26 PM               118 prostart.ini
06/10/2007  07:23 PM               137 qeditor.ini
08/11/2008  06:28 AM             3,829 menus.ini
07/30/2008  11:54 PM             3,751 dlgtmplt.qsc
09/14/2005  05:30 PM             8,516 testbed.qsc
09/14/2005  07:48 PM             1,186 bldmakit.qsc
01/04/2004  12:28 AM             4,139 blankdlg.qsc
09/14/2005  07:57 PM               711 tmp.qsc
07/30/2008  11:54 PM             4,322 dlgproc.qsc
09/14/2005  08:27 PM             1,359 libbat.qsc
04/04/2004  12:44 AM               589 makerc.qsc
09/14/2005  07:49 PM             1,188 makecon.qsc
09/14/2005  05:45 PM            10,424 bigtstbd.qsc
08/01/2008  11:53 PM               820 prostart.set
08/02/2008  07:12 PM             2,295 intro.txt
09/06/2004  08:21 PM             3,712 tproc.txt

of course, many of them are rather obvious, but i'd like to get it right

[hutch--]

Dave,

You can set QE up in a directory by itself, just add the three DLLs so it can use the scripts and the programmable menus. It is better to set the menus up from scratch and if you build directories above the directory with QE, you can use relative paths {e} in the menu ini file so it can be moved as a block. The DLLs if present must be in the same directory as QE so it can always find them, it tests if they are there or not and adds functionality to the menus if present.

You will find the menu editor easier to use than manually editing the menus.ini file and be aware that once the menus parser reaches the [Help] setting it does not add any further headings. You can keep adding headings before it until you run out of screen space.

[dedndave]

so - all those DLL's belong to QE, alone ?
it appears that the BIN files belong to QE

it would be great to know what the INI and QSC files are
i would like to clean that folder up a bit

[ToutEnMasm]

You will find the menu editor easier to use than manually editing the menus.ini file and be aware that once the menus parser reaches the [Help] setting it does not add any further headings

I am searching the "menu editor" but only see a menuedit.dll but not a menu witth "menu editor"  ?

[dedndave]

i'll bet it's in the menus   :U

[hutch--]

The menu editor is provided in the dll and is called from th EDIT menu in QE.

[ToutEnMasm]

Thanks,
MENU "EDIT" -->"Settings" -->"Edit menus"