Question on Includes

[Ace08]

hi there i have a nice little script that runs fine but i want to add something to it but after adding an include am getting an error ERROR: $WM_COMMAND previously declared as a 'Const', im not declaring this constant so i checked my includes and found out that both WindowsConstants.au3 and GUIInputSetOnlyNumbers.au3(made by MrCreatoR) are declaring this variables could this the cause of the error, any thought/comments on this?

[hannes08]

Hi Ace08,

both UDFs declace the $WM_COMMAND as constant:

Global Const $WM_COMMAND = 0x0111

look at your script whether you are trying to assign a value to that constant.

[Ace08]

yes it is $WM_COMMAND are defined inside both WindowsConstants.au3 and GUIInputSetOnlyNumbers.au3, so you were saying that its ok that 2 include udfs contain Global Const $WM_COMMAND = 0x0111 and that the problem is with my script...hmmmm... will try to look into this Thanks for the reply, i just needed to know if its ok to have 2 udfs declare the same constant. Thanks again

[hannes08]

Hi Ace08,

please try and change the order of you includes, so that the windowsconstants.au3 will be included before the other include.

[Ace08]

Thanks Hannes123

But i have set windowsconstants.au3 first before GUIInputSetOnlyNumbers.au3 but still have the same result, even tried to interchange their position. i made a copy of GUIInputSetOnlyNumbers.au3 udf and modified itself, removed the const $WM_COMMAND and made another include this time on the modified udf. this one worked for me but i dont think this is a good idea specialy with the one who created the udf

[hannes08]

Can you post your code,

so we can have a look at it together.

[Xenobiologist]

FMPOV, the order of includes doesn't matter. On runtime/compile the whole code consits all lines of all au3 files.

You cannot declare a const value twice.

Just delete the declaration in the GUIInputSetOnlyNumbers UDF and include the standard UDF.

When compiling use the obfuscator with e.g. striponly to get rid of unneeded lines of code.

Edited March 15, 2011 by Xenobiologist

[Ace08]

Ok Thanks Hannes123 for the help

#include <WindowsConstants.au3>
#include <ComboConstants.au3>
#include <EditConstants.au3>
#include <GUIInputSetOnlyNumbers.au3>

GUICreate("Sample Only", 130, 140, Default, Default, $WS_CAPTION)
GUICtrlCreateLabel ("Code1",10,10)
$Lcode = GUICtrlCreateInput("", 80, 5, 40, 20)
GUICtrlSetLimit($Lcode,3)
GUICtrlCreateLabel ("Code2",10, 30)
$Scode = GUICtrlCreateInput("", 80, 25, 40, 20,$ES_UPPERCASE)
GUICtrlSetLimit($Scode,2)
GUICtrlCreateLabel ("Year",10, 50)
$SYear = GUICtrlCreateInput(@YEAR, 80, 45, 40, 20)
_GuiInputSetOnlyNumbers($SYear)
GUICtrlSetLimit($SYear,4)
GUICtrlCreateLabel ("Month",10, 70)
$SMonth = GUICtrlCreateCombo("", 45, 65, 75, 20,$CBS_DROPDOWNLIST)
$Month = 'March'
GUICtrlSetData($SMonth, "1 Year|January|February|March|April|May|June|July|August|September|October|November|December", $Month)
GUISetState()
$msg = 0
While $msg <> $GUI_EVENT_CLOSE
    $msg = GUIGetMsg()
WEnd

here i made a sample modified from my script, well its not only $WM_COMMAND but also $WM_MOVE, $WM_LBUTTONDOWN, $WM_RBUTTONDOWN all 4 const are declared at windowsconstants.au3 and GUIInputSetOnlyNumbers.au3

Edited March 15, 2011 by Ace08

[Ace08]

Thanks Xenobiologist

i did try that one and its working realy nice. its just that i think its not right to modify udfs in respect with the maker so i was trying to see if there are other solutions.

Thanks guys for the help

[Xenobiologist]

That's life. Things are changing and not always the UDFs are changed too.

I think, it is no problem to delete those varibles.

Good luck!

[Ace08]

Yeah maybe you're right Thanks again Xenobiologist

to MrCreatoR sorry for modifying your code

also thanks Hannes123 for the help