Hi,
Alright, I'm glad the initial problem is solved
Now for the other errors:
The first error probably occured due to:
* Using KeyGuard Studio in compression mode and the OCX in non-compression mode or visa versa
* Or the POL-file was corrupted (located in the frames folder, this is the file that holds the data for a specific frame)
So, please check the help file for compression and non-compression mode. Compression is default enabled when fresh installed, to change KGS to non-compression you have to perform change a key in the registry located here: HKEY_CURRENT_USER\Software\ShadowHunter\KeyGuard change the value of "UseCompression" from 99 to 16. If this entry does not exist you can create it manuall (type REG_SZ)
To change the OCX from compression to non-compression you have to alter the "Component("KeyGuard").Object.General_DisableCompression = False" to "True" which can be found when you select to edit a plugin, under the tab "Startup", the top textbox.
If the file is corrupt simply delete the POL-file in the "Frames" directory of you project folder and draw it again.
Note: it is best to restart and reload your project during each test or change. Sometimes the OCX is not unloaded completely due to the edit mode of AM, if so certain values stay in the memory.
For the second problem:
The Panoramic plugin and KeyGuard can exists next to eachother BUT with a lot of limitations.
- KeyGuard can only be used for keystrokes, not (yet) for polygons, hint cursors or text rendering...
- A pixel shift happens but this is already solved in the next release of KeyGuard (stay tuned)
- The cursor won't change anymore, also fixed in the next release
And finally the limitation that is causing your problem. This happens when you have move from non panoramic frame but with KeyGuard and go to a panoramic frame using a transition (depending on the speed of your computer COULD also happen with no transitions but I never saw that)
The reason for this is perhaps to complex to explain in detail but involves hWnd and hDC changes by the panoramic plugin whilst KeyGuard already has info on the previous handles (hWnd = windows handle, hDC = device context handle), I was not yet able to solve this behaviour... but I'm working on it.
This error does not appear when you start the game by using a frame that uses the panaromic plugin and has a KeyGuard function. The other way arround: moving from pana to only a KeyGuard frame poses no problems.
Disabling the transition might of course also fix the problem...
I hope this information can help you.
With best regards,
ShAdOwHuNtEr