#2247 closed Bug (Fixed)
Documentation needs change for @Desktop macros
Reported by: | RichardPillay@… | Owned by: | trancexx |
---|---|---|---|
Milestone: | 3.3.9.5 | Component: | Documentation |
Version: | 3.3.8.1 | Severity: | None |
Keywords: | Cc: |
Description
The macro reference for @DesktopWidth and @DesktopHeight creates confusion by describing these macros as being the size of the desktop screen. Both these macros return the size of Primary Monitor not the Desktop. This created a situation where I was spending ages looking for bugs that did not exist when using Melba23's ExtMsgBox because he's obviously taken the documentation at face value.
The desktop is the entire area that Windows allows you to use across all monitors, while each monitor has it's own individual area. These macro names should be changed, but obviously that's going to break a lot of existing code. Under the circumstances, I beleive the text in the documentation should be changed to point out the issue.
Best Regards,
Richard.
Attachments (0)
Change History (4)
comment:1 Changed 12 years ago by trancexx
- Milestone set to 3.3.9.5
- Owner set to trancexx
- Resolution set to Fixed
- Status changed from new to closed
comment:2 Changed 12 years ago by AdmiralAlkex
The bit depth (@DesktopDepth) and refresh rate (@DesktopRefresh) are also per screen. I tested it, and they returned the primary screen for me. Could you please verify their workings and document that too?
comment:3 Changed 12 years ago by anonymous
Yes, I can confirm that. It's the same thing, the info is for primary monitor.
Somebody with better English do it.
...Anonymous my ass.
comment:4 Changed 12 years ago by AdmiralAlkex
Err I tried. It became a bit long the way you wrote it so shortened and added the note to the other two.
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
Fixed by revision [7171] in version: 3.3.9.5