Inconsistent (weird) behaviour of GUICtrlCreatePic on Windows 7

[KalleB]

I have a program consisting of 5 .au3-files, one is the main functions, one the GUI functions, and the other are various functions I mostly separate to avoid scrolling when editing (and instead changing tabs).

In the GUI file I have

GUICtrlCreatePic("P1050652.JPG", -1, -1, 1200, 450)

GUICtrlSetState(-1, $GUI_DISABLE)

(and the file P1050652.JPG exists and is without errors).

If I double click the main .au3-file everything is fine and I get to see the background picture.

If I create a shortcut, and double click this, all is fine.

If I pin AutoIt to the taskbar, and then pin the main file to this icon, then the GUI is grey (no picture) when it runs.

Why don't I see the picture when the file is called via a pinned shortcut?

If I compile the program I see the picture.

If I pin the compiled version to the taskbar I see the picture.

Since using the pin to pinned icon version of starting the program is the easiest, I'd prefer for this to work as well. Other than that I'm mostly curious to why the behaviour varies.

[BrewManNH]

Use the full path to the picture file in there instead of a relative path the way you have it now.

[KalleB]

Thank you, that did it. But why does the pin-to-pinned version require full path, when none else does?

[BrewManNH]

It's taking the directory from where the file is, the script directory that is. When it's pinned, it's probably using one of the default directories as the working directory, which isn't your script directory.