I'll second the vote for a smaller footprint display, if it's possible.
In my case, I have the Pi hooked into my car's in-dash unit (back-up
camera port), which has a VGA display resolution. Mostly it seems to
affect the configuration pages, where stuff ends up below or off to the
side of the screen, but there aren't any scroll bars to access it. I
think simply triggering the scroll bars for those screens would make it
usable.
Lacking the scroll bars, what I do now is to access the Pi with VNC, and
that display is configured for 1024/768 resolution.
Greg KO6TH
rhclinton wrote:
toggle quoted message
Show quoted text
Hmm, maybe I'm missing the point too - of WA7SKG's complaint. I have
been using APRS or nearly
20 years, fixed station and mobile. Most of the time mobile I have
been satisfied with the
non-graphic display of a Kenwood D700/710. When I needed a full
graphic display of APRS-FI,
UI-View or YAAC it wasn't a big deal to use my iPad or connect a
laptop. No doubt a format
suitable for a 7" display connected to an RPi would be useful but APRS
has been useful without
it for a long time. If Andrew can come up with a suitable layout for
use with YAAC that would
be great but it is more important to get it right than to just get
it released.
Bob G0BUX/W0BUX
On 2019-12-28 17:07, Andrew P. wrote:
Let me clarify.
YAAC's screens were designed for a conventional laptop PC, with
minimally 1024x768 pixels to work with. They weren't designed for
low-resolution screens, because it's too hard to draw a usable map
with limited pixels. So the screen layout assumed that there would be
enough width to display all the messaging controls at the bottom of
the map window.
The menu choice Message->Station provides the same functionality in a
popup dialog window, but has the fields in different lines, so it may
not require as much screen width.
I have been contemplating an alternate screen for low-res mobile
operations (such as the 7" touchscreen for Raspberry Pi), but haven't
come up with a layout I like yet that will fit in such a tiny space
and still be operable with fat fingers on a touchscreen.
Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of
Christopher Rose <kb8uih88@...>
Sent: Saturday, December 28, 2019 11:13 AM
To: '[email protected]'
Subject: Re: [yaac-users] Message box
Michael, Andrew said menu choices will get you where you want to go
on your smaller screen. Then you say too bad? Did I misunderstand this
exchange?
Chris
-----------------------------------------
From: "Michael WA7SKG"
To: "Andrew P.", "[email protected]"
Cc:
Sent: Saturday December 28 2019 6:05:11AM
Subject: Re: [yaac-users] Message box
That is too bad. Perhaps I am misinformed or have misunderstood, but I
thought the whole purpose of APRS was to cater to the mobile user to
provide a quick and easy method of reporting position, status, and brief
messages. Mobile operation, by its nature, necessitates smaller screens
and demands minimal operator actions to accomplish a task. The system
should be driven to meet that situation, rather than make it more
difficult for the primary purpose.
Maybe I am missing the point of APRS. Perhaps further investigation is
in order.
Michael WA7SKG
Andrew P. wrote on 12/27/19 6:24 PM:
It's because your window is too small. The rightmost controls in the
footer are being drawn off-screen because they don't fit in the allowed
window space.
There are menu choices to get you the same functionality in a smaller
window.
Sent from my Verizon 4G LTE smartphone
-------- Original message --------
From: Michael WA7SKG <wa7skg@...>
Date: 12/27/19 20:16 (GMT-05:00)
To: [email protected]
Subject: [yaac-users] Message box
Another question. On my base configuration, at the bottom of the
screen,
there are three boxes, TO, VIA, and Message, followed by a SEND button.
I can put in a callsign, a path, and some text, hit send and it goes to
that station. However, on my just configured mobile, only the TO and
VIA
boxes are visible. The TEXT box and the SEND button are missing.
Is this a configuration issue? Or because I am using a much smaller
screen (22" on base, 7" on mobile)?
Thanks,
Michael WA7SKG
