It detects my 1280x1024 as 1280x960 from time to time(precise and fast). Also, if I move the mouse rapidly while calculating, I got results like 462x363 or 89x63 (precise). The mouse disappears while determining, and if I don't move the mouse, I don't get any result at all. Also, from time to time, I got:
00:04:22.94 Trigger Error in 'lib0E15B1AE_gt_GetMousePos_Func': Divide by zero
00:04:32.50 Trigger Error in 'lib0E15B1AE_gt_GetMousePos_Func': Divide by zero
All of this in Windowed (Fullscreen). In Fullscreen, it seems to always detect correctly, Windowed with varying window sizes seems to be problematic as well, similar problems to Windowed (Fullscreen).
Last edited Jul 20, 2012 by Kueken531
Taldeen Regular ShmoeHey there,
since the resolution libary by desiderius1 requierd the User to click, and had some little errors when moving the mouse during the measurement, i decided to write a new one. The new libary has a diffrent approch to measure the resolution and has more options doing this:
Advantages
Disadvantages
Known Issues
Documentation(Basic)
Installation
Change the lirbary ID to 0E15B1AE (Right click on the library -> Library -> Change Library ID -> Use Shared ID -> Hexadecimal -> 0E15B1AE)
Action: UI - Resolution - Setup
It's initailizes everything you need. If you want to risk a lagg when detecting the resolution you should run this action in adavance. It usally takes 2-3 seconds. I recommend running this at Map initialization. This will generate the needed dialogs for the system and initalize the resolution database.
Action: Resolution - Refresh
This is the heart of the system. Running this action it will set the global variables.
Parameter: Player(0-15)
Playernumber of the Player you want to detect the resolution of.
Parameter: Mode(on/off)
Turning on the precison mode will ensure the quallity of the result. If the mouse is moved rapidly it will take some additional seconds to detect the resolution. When turned off the result will be nearly instant, but on moving the mouse it will be inaccurate the same way like desiderius1 library.
Parameter: Tolerance(0-infty)
Setting this parameter to a value greater than zero the system will use the resolutiontable(Source:Wikipedia) and trys to match the measured resolution to a common resolution. Since the error of the measurement is about 1% i recommend a value of 2.5%, this will ensure quallity of the result.
Parameter: Debugmode(on/off)
This will display the measured variables when done.
Variable(Record): UI - Resolution
This contains all information measured. The array is the playernumber(0-15). All values are set to zero in the beginning. If youre not sure if the variable has been set then use the "Condition: Resolution - Decent check". I will return false if the variales aren't set.
Documentation(Advanced)
Action: UI - Resolution - Disable Permanent Tracking
Parameter: Permanent Tracking(Enable/Disable)
Enableing this option might speed up the detections Prozess. I do not recommend leaveing this option turned on since it fires a trigger on mouse movement and generates this way a lot of traffic. Single player shouldn't be a probem.
Condition: Resolution - Decent check
This condition will check if the player has changed his resolution. It's a lot faster than refreshing the resolution variables. It will return false if the resolution has changed, true if it's still the same. I will NOT correct the resolution variables!
Settings(Advanced): Record: Settings
By-product: Show/Hide Dialogs Below Mouse
This will hide all dialogs below your mouse and show them again on command.
Parameter: Player(0-15)
Playernumber of the Player you want to hide the dialogs for.
Parameter: Display(show/hide)
Show or hide the Dialogs
I hope this Documentation helps a litte ;).
Since i have no Idea if these changes are enough for a new post in the library section and i would like to have some feedback i postet this here for now. Hope this helps some mapmakers ;)
Taldeen