Custom Query

RichEditConstants.au3 already has the following constants for use with the common Find Replace dialog. Annoying since I then have to find the ones I need elsewhere, and then comment out the already existing ones (which miss out a few key constants).

Current:

Global Const $FR_DOWN = 0x1
Global Const $FR_MATCHALEFHAMZA = 0x80000000
Global Const $FR_MATCHCASE = 0x4
Global Const $FR_MATCHDIAC = 0x20000000
Global Const $FR_MATCHKASHIDA = 0x40000000
Global Const $FR_WHOLEWORD = 0x2

proposed constants (full list):

Global Const $FR_DOWN = 0x00000001
Global Const $FR_MATCHWHOLEWORD = 0x00000002
Global Const $FR_WHOLEWORD = $FR_MATCHWHOLEWORD
Global Const $FR_MATCHCASE = 0x00000004
Global Const $FR_FINDNEXT = 0x00000008
Global Const $FR_REPLACE = 0x00000010
Global Const $FR_REPLACEALL = 0x00000020
Global Const $FR_DIALOGTERM = 0x00000040
Global Const $FR_SHOWHELP = 0x00000080
Global Const $FR_ENABLEHOOK = 0x00000100
Global Const $FR_ENABLETEMPLATE = 0x00000200
Global Const $FR_DISABLEUPDOWN = 0x00000400
Global Const $FR_DISABLEMATCHCASE = 0x00000800
Global Const $FR_DISABLEWHOLEWORD = 0x00001000
Global Const $FR_ENABLETEMPLATEHANDLE = 0x00002000
Global Const $FR_HIDEUPDOWN = 0x00004000
Global Const $FR_HIDEMATCHCASE = 0x00008000
Global Const $FR_HIDEWHOLEWORD = 0x00010000

Global Const $FR_MATCHALEFHAMZA = 0x80000000
Global Const $FR_MATCHDIAC = 0x20000000
Global Const $FR_MATCHKASHIDA = 0x40000000

In addition, the following constants could be added, though are not as important:

Global Const $FR_DIALOGMESSAGE = "commdlg_FindReplace"
Global Const $tagFINDREPLACE = "dword lStructSize; hwnd hwndOwner; hwnd hInstance; dword Flags; ptr lpstrFindWhat; ptr lpstrReplaceWith; ushort wFindWhatLen; ushort wReplaceWithLen; " & _
			"ptr lCustData; ptr lpfnHook; ptr lpTemplateName;"

Mat

These new functiona will return memory Address/Size Of given AutoIt's Variable so we can use some pointers/typecast tricks. For example create structure "over" that memory and then get data in another type

$MemPointer = AddressOfVar($a)
$MemSize = SizeOfVar($a)
$struct = DllStructCreate("byte[" & $MemSize & "]", $MemPointer)
$data = DllStructGetData($struct, 1)

I'm sure there will be another uses of this functionality together with AutoIt's DllCall() and structures and memory API functions.

I read that you are not ready to add OOP concept in autoit and I agree with this but it is painful to define structured data array. I am using a lot a structured array and the only way to get them is to define an enum with all the fields offset in the array and to define an array. This needs definition of a lot of constants which needs to be exported everywhere. It would be better to define a struct and access directly members.

declaration: Defstruct mystruct_t [ _

field1, _ field2, _ field3 ]

instaciation: Struct mystruct_t mystruct = [initfield1, initfield2 , initfield3]

access: mystruct.field1 = data

I agree it is very C like but so easy to use.