BBC BASIC forum

I tried so many variations of different things that I may have just overlooked 'GetForegroundWindow'. Thanks.

I would be surprised if BB4W got confused with hwnd% and @hwnd%. Particularly as @... is a system variable. But I will investigate what you have brought up.

Thanks.

Matt

Thanks DDRM. Yes, that's helpful. I hadn't considered where the variables were being stored, just that I assumed they would be released. That's one of the problems of taking a piece of code and shoving it into a program without carefully looking through. The GUID is mainly used for an random code wi...

Hi. I've been using a GUID (Global Unique Identifier) routine, which came from Wiki. REM Creates Global Unique Identifier name DEF FNguid LOCAL guid{}, guidw%, guida% SYS "LoadLibrary", "OLE32.DLL" TO ole32% SYS "GetProcAddress", ole32%, "CoCreateGuid" TO CoCreateGuid% SYS "GetProcAddress", ole32%, ...

This is a very useful piece of information, and the added code works great.

Svein, thanks.

Matt

Cheers. I'll investigate this. One of my thoughts was to add wait statements to various points and it seemed to have little effect. However, I'll try again.

Matt

Thanks Svein.

Implementing this change into my program does sort this problem out. However, it seems to introduce another one, which I will have to investigate further. Thanks again for your advice.

Matt

Thanks Zaphod. My understanding of the help for MOUSE and ON MOUSE is that ON MOUSE is an alternative rather than a necessary part of MOUSE. It's possible that using the ON MOUSE command might sort my problem out, but it would mean a heck of a lot of changes to my code. I'd be interesting to know, t...

OK. That's interesting.

I've only got the one computer to try it on, so I'd be interested if anyone else has tried it, and what results they have. I retried it after a reboot and came up with the same result as before.

Matt

Hi. This one's got me stumped. The following bit of code is an adaptation from a part of my program. Ignore the fact that DP% is always set to -1, as this is a normal posibility of the removed code. When the window is clicked on the loop runs to the error message. When the window 'X' close button is...

This change works fine. (Although I had to go back and reset the mouse double click Y value, as this was changed to zero with the 30 - i.e. &1E.) However, I'm getting a slightly confusing effect when I try to run my program. The edited bit is here: DIM rc{l%,t%,r%,b%} SYS "GetSystemMetrics", 0 TO W%...