Reply to thread

Message

<blockquote data-quote="jamieo" data-source="post: 301187" data-attributes="member: 53052">Hi, regarding the cross thread stuff, window messaging doesn't care about any of that - it how windows works, whether those windows are in the same thread, app or OS.&nbsp; For instance, I could make a small app that activates the windows in your app so I'm sure your app should be able to do the same with it's own windows.&nbsp; This can be done with any programming language with basic access to the WinAPI, even by something like the AutoHotkey script language..Net should have it's own wrapper around SetWindowPos but at the very least you can use <a href="http://www.pinvoke.net/default.aspx/user32/SetWindowPos.html" target="_blank">PInvoke</a> to invoke the WinAPI directly - I believe one of the properties of a .Net window is it's window handle for use with the WinAPI, if not then you would have to get this by searching for the window title or similar.&nbsp; All this is independent of thread etc. so it shouldn't matter.&nbsp; However, it's not a big issue - I just know that it is possible to implement as the core WinAPI functionality provides for it.Btw, for proper cross threaded gui stuff you should look into delegates and control.invoke etc.&nbsp; However, while it would solve this problem there is a steep leaning curve and, as I said before, it's overkill when simple window messaging is all that's required.Anyway, any chance of an updated exe?&nbsp; It's annoying to have to keep deleting those extra covers!Jamie</blockquote>

[QUOTE="jamieo, post: 301187, member: 53052"] Hi, regarding the cross thread stuff, window messaging doesn't care about any of that - it how windows works, whether those windows are in the same thread, app or OS. For instance, I could make a small app that activates the windows in your app so I'm sure your app should be able to do the same with it's own windows. This can be done with any programming language with basic access to the WinAPI, even by something like the AutoHotkey script language. .Net should have it's own wrapper around SetWindowPos but at the very least you can use [URL="http://www.pinvoke.net/default.aspx/user32/SetWindowPos.html"]PInvoke[/URL] to invoke the WinAPI directly - I believe one of the properties of a .Net window is it's window handle for use with the WinAPI, if not then you would have to get this by searching for the window title or similar. All this is independent of thread etc. so it shouldn't matter. However, it's not a big issue - I just know that it is possible to implement as the core WinAPI functionality provides for it. Btw, for proper cross threaded gui stuff you should look into delegates and control.invoke etc. However, while it would solve this problem there is a steep leaning curve and, as I said before, it's overkill when simple window messaging is all that's required. Anyway, any chance of an updated exe? It's annoying to have to keep deleting those extra covers! Jamie [/QUOTE]

Verification