Do you have autohotkey installed?
if so you can try this script.
It's just a rough draught so you can test & see if this is what you have in mind.
This script has a timeout of 60 secs & you can press Win+3 to reset the timer.
The setting are the variables at the top of the file - they are obviously named.
Right now the script just runs once & if it locks you out you will have to run the script again - but as I said it's just a first run.
And hopefully sum other guys here will jump in 2 polish it up.

#Persistent
#SingleInstance force
#UseHook On
#Include %A_ScriptDir%
SetWorkingDir, %A_ScriptDir%

HotkeyCombo = #3
CountdownTimer = 60
WarningMessageTimer = 30
WarningMessage = WiFi connection signal quality is poor, connection will be lost in %WarningMessageTimer% seconds
DebugMode := False



StartUp:
{

   nCountdownTimer := 1000 * CountdownTimer
   nWarningTimer := 1000 * WarningMessageTimer
   nInternalTimer := nCountdownTimer
   nInternalTimerResolution := 100
   bIconOff := False
   
   
   if(WarningMessageTimer>CountdownTimer)
   {
      msgbox "CountdownTimer" must be greater than or equal to "WarningMessageTimer"
      return
   }
   
   Hotkey, %HotkeyCombo%, HotkeyPressed
   
   SetTimer, InternalTimer, %nInternalTimerResolution%

return
}


HotkeyPressed:
{
   SetTimer, InternalTimer, Off
   nInternalTimer := nCountdownTimer
   SetTimer, InternalTimer, %nInternalTimerResolution%

   TrayTip, Autolock, Timer reset thank you, 5

return
}


InternalTimer:
{

   nInternalTimer := nInternalTimer - nInternalTimerResolution
   if(nInternalTimer<=0)
   {
      Gosub, LockOut
      return
   }
   if(nInternalTimer<=nWarningTimer)
   {
      Gosub, ShowWarning
      return
   }
   
   bIconOff := !bIconOff
   if(bIconOff)
   {
      Menu, Tray, Icon, Shell32.dll, 174
   }
   else
   {
      Menu, Tray, Icon, Shell32.dll, 173
   }
   
return
}


ShowWarning:
{
   TrayTip, Autolock, %WarningMessage%, 30
return
}

LockOut:
{
   SetTimer, InternalTimer, Off
   if(DebugMode)
   {
      msgbox, LOCKOUT
   }
   else
   {
      DllCall("LockWorkStation")
   }
   
return
}

tinjaw I don't know how yr situation applies 2 the original question, but going on the original issue of linking to a CAD program that frequently breaks binary compatibility & forcing a recompile...
Why not use late binding instead?
In that situation what I would try is 2 create the project as normal, linking to type libraries & such so that you get the full benefit of intellisense.
When everything is working, change yr strongly typed references to the 3rd party library with Variants or Objects.
Also replace all uses of the NEW operator with CreateObject & remove the project references to those controls or dlls.
You only need to do this for 3rd party objects that might break binary compatibilty.
Also keep in mind the Add Components dialog which has a checkbox to "REMOVE INFO ABOUT UNUSED ACTIVEX CONTROLS" - you may need to check/uncheck that (I forget which ;))
If you take this scripting-like approach, binary compatibility should not be an issue.
However you're still gonna have some apps which change the structure of their exposed objects but that would always be a recompile...

I was looking for exactly the same thing a few years ago 2 have an unobtrusive webcam video while I work.
I found the best solution 4 my needs was the VLC Media Player. You can detach the video window interface from the main window thru the options.
But the decider for me was that the install includes an viewer ActiveX control so you can create yr own custom viewer to suit yr exact needs.
If I remember correctly, with the right settings, the VLC player even supports transparency which most other players don't.
If you try it & want some help with the connection strings let me know cos I have the VB code around somewhere.