From: "Jim C. Brown" <jma5@umd.edu>
To: jhoger@pobox.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] scrollable window
Date: Sun, 10 Jul 2005 23:41:56 -0400 [thread overview]
Message-ID: <20050711034156.GA32197@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <1121029613.9033.53.camel@aragorn>
On Sun, Jul 10, 2005 at 02:06:53PM -0700, John R. Hogerhuis wrote:
> VmWare seems to let you do it any way you want. Full screen, scroll it
> manually or auto scroll, etc. So clearly it can be done. Maybe the code
> in something like VNC client would give some ideas.
>
Scrolling manually works, just a few kinks to iron out.
Fullscreen support is currently broken, but it is fixable. Just haven't gotten
around to it yet.
Autoscrolling is harder. VMware uses guest drivers, and using a custom guest
mosue driver would certainly help. This is doable if the guest OS does not do
mouse acceleration (because then the host and guest pointers dont get out of
sync - if the host pointer is at the edge of the window, the guest must be as
well). This option is a bit of work though...
> Scaling an image *down* to fit in window of a given size seems totally
> pointless other than to give a thumbnails of multiple vm's for
> navigation between VMs. For that matter I can't imagine trying to work
> with a machine w/in a machine at 800x600 for the host. Better to go to a
> higher resolution and then you could consider scaling a vm display *up*
> to some given size. Just increase your font size on the host. There's no
> such thing as too high a resolution, just fonts that are too small
> and/or broken applications or windowing systems that don't let you
> adjust the font size.
>
Scaling an image up on the other hand, may be quite useful. I am not sure how
to do either (up or down) but if scaling up is possible, it seems only natural
to add the ability to scale down (even if its not recommended due to hard to
see fonts and etc).
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-07-11 4:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-10 5:58 [Qemu-devel] scrollable window Jim C. Brown
2005-07-10 6:50 ` Ashish Naik
2005-07-10 11:07 ` Ashish Naik
2005-07-10 13:40 ` Jim C. Brown
2005-07-10 15:27 ` user user
2005-07-10 16:16 ` Jim C. Brown
2005-07-10 16:37 ` jeebs
2005-07-10 17:32 ` Herbert Poetzl
2005-07-10 17:57 ` Jim C. Brown
2005-07-10 18:37 ` Herbert Poetzl
2005-07-10 18:53 ` Jim C. Brown
2005-07-10 20:51 ` Herbert Poetzl
2005-07-10 21:06 ` John R. Hogerhuis
2005-07-11 3:41 ` Jim C. Brown [this message]
2005-07-10 19:07 ` Jernej Simonèiè
2005-07-10 18:19 ` jeebs
2005-07-10 17:43 ` Jim C. Brown
2005-07-10 18:21 ` jeebs
2005-07-10 20:24 ` Jim C. Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050711034156.GA32197@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=jhoger@pobox.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).