Closed GoogleCodeExporter closed 9 years ago
What?
Original comment by jh...@google.com
on 5 Oct 2010 at 12:11
First, sorry this should be an enhancement, not a defect. Second, the use case
scenario would be like this
User has one or more slave displays all are different sized displays from the
host, and potentially different resolutions as well.
User wants images to display in the master and slave at the same visual size
regardless of the physical size of the display.
One way I thought of doing this would be to simply implement a “zoom
offset” on the slave display so that for instance, if the slave display was
smaller than the master the slave would have a “zoom offset of 1” for
example to make the image appear larger in the slave to compensate for the
difference in physical display size.
Original comment by jaaaa...@gmail.com
on 5 Oct 2010 at 12:41
Oh, I see. You should be able to do what you want using the
'ViewSync/horizFov' setting, which sets the horizontal field of view in degrees.
Original comment by jh...@google.com
on 5 Oct 2010 at 10:19
jaaaames, were you able to do what you needed with the settings Jason pointed
out? Especially with newer versions of Google Earth, you should be able to use
a combination of ViewSync settings to get almost any view for a given galaxy
node.
Original comment by kiel.endpoint
on 15 Dec 2010 at 12:14
Without any further feedback, it's not clear if the user was able to utilize
the various ViewSync/* settings to achieve the desired effect. However, it
should certainly be possible, so closing this issue.
Original comment by kiel.endpoint
on 23 Jun 2011 at 6:32
close it. tweaking ViewSync/horizFov works for the scenario presented.
Original comment by alfski
on 27 Jun 2011 at 1:38
Original issue reported on code.google.com by
jaaaa...@gmail.com
on 3 Oct 2010 at 3:52