View Issue Details

IDProjectCategoryView StatusLast Update
00032563 - Current Dev ListBugpublic2019-08-13 22:14
ReporterK7ZCZAssigned ToK7ZCZ 
PrioritynormalSeverityminorReproducibilityhave not tried
Status feedbackResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0003256: What is the minimum screen size (in pixels) that HRD supports?
DescriptionSeems like some users expect to run HRD on very small monitors. However, we know that HRD doesn't scale well -- it doesn't include code to manage layout or content to smaller screen sizes.

We don't actively test or design with any specific display size in mind.

It would help to identify a minimum screen size (in pixels) which we support. By clearly communicating this to customers, we'll set their expectations; we'll also establish our own guideline for development and testing. Maybe we don't need to implement any scalying or layout code -- or maybe we do need to approach that issue.
TagsNo tags attached.
TestingNot Started


related to 0003040 closedPD9FER 5 - Closed w/o Action Logbook ALE window can not be resized vertically 
related to 0002657 resolvedPD9FER 1 - Backlog Request: option to turn off Tool Tips 



2019-03-21 15:38

administrator   ~0007716

In the triage call on 2019-03-21, we identified this issue and you agreed to evaluate the issue.


2019-03-21 15:40

administrator   ~0007717

The related issues show a couple of cases where the HRD UI becomes cumbersome on smaller screens.


2019-08-13 22:13

administrator   ~0008401

I was testing our apps with a variety of pixel dimensions today. What I found is this...

The one thing I could find that I didn't like that was affected by the pixel dimensions was that when the width is less than about 1234 pixels, the "ribbon bar" above the logbook database view goes from one row to two rows (I have no other means to describe this, but it's the bar that has Add, Contest, Delete, View, Cut, Copy, Paste... LOTW Upload, LOTW Download). When this happens, then vertical screen real estate is consumed and (I think) it makes using the program a bit more awkward. (Too bad users can't add/remove buttons from that bar.)

Are we trying to define (a) minimum requirements or (b) a recommended minimum?

If (a), then we're saying that the software will be configured so that it will not run on machines with less than the "minimum requirements?"
If (b), then there's more flexibility if we're telling customers that this is what we "recommend."

That said... it appears to me that 1280x800 would be the appropriate screen size. I'm just not sure we need to force that and prevent the software from running if it doesn't meet that minimum.

Issue History

Date Modified Username Field Change
2019-03-21 15:36 K7ZCZ New Issue
2019-03-21 15:37 K7ZCZ Relationship added related to 0002657
2019-03-21 15:37 K7ZCZ Assigned To => WA9PIE
2019-03-21 15:37 K7ZCZ Status new => assigned
2019-03-21 15:38 K7ZCZ Note Added: 0007716
2019-03-21 15:39 K7ZCZ Relationship added related to 0003040
2019-03-21 15:40 K7ZCZ Note Added: 0007717
2019-08-13 22:13 WA9PIE Note Added: 0008401
2019-08-13 22:14 WA9PIE Assigned To WA9PIE => K7ZCZ
2019-08-13 22:14 WA9PIE Status assigned => feedback