slow paints despite fast hardware

[Phlip]

Christopher Faylor wrote:

> On the contrary, this is a good illustration for anyone who tends to
> become offended by attempts to clarify and redirect false assumptions.

The fallout makes converging on an answer much harder too.

Let's start again, with a parable. For example, if I discovered the
CrystalSpace shader were slow, their FAQs and forums would tell me to
switch from the emulation shader to the hardware shader. They would
tell me to inspect such-and-so log file to find evidence, to obtain
such-and-so driver, and to change such-and-so configuration file.

CrystalSpace ships with the software emulator enabled because you
obviously might not have the same hardware as their build server has.
So this default is safe, not fast.

If they said, "Did you even read the FAQ?", I would read it, report
that I did, and report how well I could apply its suggestions. If they
said, "hey newb, is your computer turned on?"... what would you
answer?

My Cygwin's X server generates the slowest GUIs on my workstation. The
rest handle simple repaints in user-time. I have observed this
problem, off and on, over several different platforms and
configurations, for over a year by now, and it has limited my ability
to make Cygwin productive. The problem's tenacity makes me think it is
commonly reported and easy to fix. My inability to read the various
xinitrc-related batch files, and to Google for their documentation and
online FAQs, has told me simply that there is something that I don't
know how to even ask about.

So I ask my question as a metaphor. Because I have experience with GUI
systems that ship in a safe configuration, instead of the fast
configuration, I ask if this is the case for Cygwin's X server.

Things go downhill from there, but I'm not sure if any better metaphor
were possible...

The question remains: Where do I start the investigate, and what RC
files and setting lines might control the situation?

-- 
  Phlip
  http://c2.com/cgi/wiki?ZeekLand  <-- NOT a blog!!

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/