[AccessD] Display on 21:9 screen

[RockySmolin at bchacc.com]

-------- Original Message --------
Subject: RE: [AccessD] Display on 21:9 screen
From: <RockySmolin at bchacc.com>
Date: Fri, July 24, 2015 8:44 am
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>

The resizing is under my program's control.  I'm not sure what the
ultrawide's proerties are - whether they can split their display, etc. 


So I'll have to solve this using my own code I think.  I'm actually
unsure at this point what the problem is with displaying the form.




r


  -------- Original Message --------
 Subject: Re: [AccessD] Display on 21:9 screen
 From: Dan Waters <df.waters at outlook.com>
 Date: Fri, July 24, 2015 8:29 am
 To: "'Access Developers discussion and problem solving'"
 <accessd at databaseadvisors.com>
 
 Hi Rocky,
 
 From what I've been reading, the purpose of a 21:9 monitor is to
replace a
 dual monitor setup. So your client should only be concerned about
resizing
 to the height of the monitor, not the width.
 
 And, it does look like an ultrawide monitor is an investment!
 
 Good Luck!
 Dan
 
 -----Original Message-----
 From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf
Of
 RockySmolin at bchacc.com
 Sent: Friday, July 24, 2015 10:20 AM
 To: Access Developers discussion and problem solving
 Subject: [AccessD] Display on 21:9 screen
 
 Dear List:
 
 I have a client who has changed from 16:9 displays to 21:9 displays -
 ultrawide. In my product I use the venerable screen resizing module
from
 the Access Developer's Handbook. It has always worked well with some
custom
 tweaks I have made over the years, and works well in 16:9. 
 But it does not resize correctly in 21:9.
 
 The client can make the forms display correctly by setting the display
back
 to 16:9 but is complaining that the inability makes his investment in
ultra
 wides 'useless'. 
 
 So maybe the technology has finally outstripped the ability of the
Littwin,
 Getz, et al's resizing code to keep up.
 
 I'm on the road and just got this report so I can't replicate the
condition
 until I get back to the office. 
 
 Bu in the meantime is there an alternative - preferably packaged in a
module
 - that effectively replaces the ADH code?
 
 MTIA
 
 Rocky
 
 --
 AccessD mailing list
 AccessD at databaseadvisors.com
 http://databaseadvisors.com/mailman/listinfo/accessd
 Website: http://www.databaseadvisors.com
 
 -- 
 AccessD mailing list
 AccessD at databaseadvisors.com
 http://databaseadvisors.com/mailman/listinfo/accessd
 Website: http://www.databaseadvisors.com