Home
Products
Overview
Compare Products
Actual Window Manager
Actual Multiple Monitors
Actual Title Buttons
Actual Virtual Desktops
Actual File Folders
Actual Transparent Window
Actual Window Minimizer
Actual Window Guard
Actual Window Menu
Actual Window Rollup
Download
Actual Window Manager
Actual Multiple Monitors
Actual Title Buttons
Actual Virtual Desktops
Actual File Folders
Actual Transparent Window
Actual Window Minimizer
Actual Window Guard
Actual Window Menu
Actual Window Rollup
Order
Single User License
Corporate Sales
Upgrade Center
News
Latest news
Newsletter
Support
FAQ
How to Upgrade
Restore License Key
Online Demos
Online User Manual
Forums
Announcements
General
Feature Requests
Technical Support
Tips and Tricks
Beta Testing
Feedback Form
Beta Testing Section
Resources
Articles
Reviews
Success Stories
Multi-Monitor Wallpapers
Company
About Us
Contact Us
Privacy
Our Clients
Press Center
Press Releases
In The News
Reviewer's Guide
Logos and Screenshots
Publishing-friendly Graphics
Forums list
New topics
Topics list
Search
Help
Login
Register
Topic: «
AWM 6.5 b1 Restrict Placement still doesn't work right
» on forum:
Beta Testing
Views: 4438
Mike Brazil
Advanced user
Posts:
136
Joined:
07/19/2010
Posted:
03/07/2011 23:23:41
According to the What's New for Actual Window Manager 6.5 beta 1, you made changes to correct the Restrict Placement problem I had reported in my post of 28.02.2011 in the Tech Support forum. Apparently, there is still some work that needs to be done regarding Restrict Placement.
The Restrict Placement values apparently are offsets that refer to the edges of the entire desktop area comprising both monitors. This isn't stated in the Restrict Placement area where these values are displayed or in the help. I think this needs to be prominently and clearly explained in both places. My initial assumption was that, since I'd selected Move at startup to monitor | Exactly specified | Monitor 2, the Restrict Placement coordinate values would refer to the borders of that monitor, not the borders of the entire desktop.
While the target tool now does obtain a functional set of coordinates for the app, some of the coordinate values displayed in AWM still seem to be incorrect or at least misleading.
In the example I provided in my earlier post, I stated that the app window is 1294 x 1036 and is aligned top-left on monitor 2 (1280 x 1024 resolution) and is offset -14 L and -4 T. The values shown in Restrict Placement for this app are -1294 L, -4 T, 1920 R, and 168 B. Shouldn't the value for Left be -14 rather than -1294?
Also, since the app window is displayed only on monitor 2, it seems confusing that the value for Bottom is 168 rather than 0. I understand that, since it's referencing the borders of the entire desktop area, that's where the 168 is derived from, but on the monitor the app window is occupying, those last 168 pixels don't exist.
Maybe the best answer to this situation overall would be to add a checkbox so the user could choose whether to reference the offsets to a specific monitor or to the entire desktop area.
Mike
--
Mike
Top
Vasiliy Ivachev
Administrator
-retired-
Posts:
2073
Joined:
11/09/2010
Posted:
03/09/2011 01:35:17
Hello Mike,
Thanks for the post.
Quote
Maybe the best answer to this situation overall would be to add a checkbox so the user could choose whether to reference the offsets to a specific monitor or to the entire desktop area.
We'll try to add this possibility.
Best regards.
Top
User(s) reading this topic
Number of guests:
1
, registered members:
0
, in total hidden:
0
Forums list
New topics
Topics list
Search
Help
Login
Register