Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!purdue!haven!umd5!oppenhei From: oppenhei@umd5.umd.edu (Richard Oppenheimer) Newsgroups: comp.windows.ms Subject: Re: MS-WINDOWS IN 1024x768 RESOLUTION Message-ID: <6318@umd5.umd.edu> Date: 23 Mar 90 00:42:38 GMT References: <327@spot.wbst128.xerox.com> <29563@amdcad.AMD.COM> <1531@watserv1.waterloo.edu> Reply-To: oppenhei@umd5.umd.edu (Richard Oppenheimer) Organization: University of Maryland, College Park Lines: 34 In article <1531@watserv1.waterloo.edu> tom@mims-iris.waterloo.edu (Tom Haapanen) writes: >Phil Ngai writes: >> Using an Orchid Prodesigner in 1024x768 mode with Micrografx >> Designer, I found the performance also unacceptable. Let's >> all hope that Windows 3.0 is much better. > >...but at least on a Paradise VGA Plus, 800x600 mode is not noticeably >slower than VGA. And the resolution's not bad; maybe you could compromise >until Microsoft makes the announcement we're all holding our breath for... I am not sure whether this speed issue is Windows or Designer. I find that many of Micrographx's programs do not have an optimal refresh algorithm. Any change you make requires the entire document to be redrawn. In 1024x768 more of the document is displayed and therefore you are not only waiting for the document to be redrawn, but also the entire workspace (the area used by the app). I think that Micrographx needs to improve in both areas. It is kind of like the old 1-2-3 calculation method. Make a change which only affects one dependent cell and calculate all 10,000 cells. I am sure the issue here is more complicated, but the idea is the same. Signature under construction ______ / | Richard Oppenheimer | \/ Computer Science Center | Ri University of Maryland __|__ __ College Park, Maryland ,USA | | |______|| \ oppenhei@umd5.umd.edu (office) | | OO OO--0-| richard@wam.umd.edu (home) ****************************************************************** My employer cares not what I think and knows not what I say. The opinons expressed herein are my own and are not endorsed by the Computer Science Center. ******************************************************************