#Warn with Gdip variable clash Topic is solved

[ahketype]

Hi, I've been using Gdip.ahk library and writing my code by hacking examples from @tic. These call the library with many of the same variable names as are used by the functions in Gdip itself.

Should I be worried when I put #Warn in my code that I get lots of error warnings about variables I'm using that are also in Gdip? These include things like pToken, hBitmap, pBitmap and G, from calls to the library, and also a bunch of common variable names like x, y, size and so on.

I began to rename them, and then got reports that these variables weren't assigned (unless I just screwed up the editing; I don't think so)!

I wonder if this is a general misuse of variables on my part - should I be declaring variables more specifically as global or local or something?

Or should I just take #Warn out again and forget it, since it's all be working just fine!

Cheers

[mikeyww]

Yes, you can declare them, explained here: #Warn. Alternatively, remove the #Warn directive.

[gregster]

You can still use #Warn, but just disable certain warnings (see #Warn docs).

Warnings are just potential errors - obviously the creators of the Gdip library didn't care to use #warn, or initializing variables. But these are probably no errors, just uninitialized variables.
But of course, you can also initialize all variables, if you prefer.

[ahketype]

Ahem, sorry, I don't know why I didn't look it up! Thanks.