On Jun 11, 2015, at 12:29 AM, Jim Dishaw j...@dishaw.org wrote:
On Jun 10, 2015, at 11:30 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca
wrote:
snip
Just to confirm that I just now played a lot with resizing of
examples/c/x01c -dev xwin
for 5.10.0, 5.11.0, and git master tip
Hmmm
Then h some more
Followed by an ummm or two.
As you say Jim, clearly things are more complicated than I realised. I'm not
sure what the requirements really are here now. Now you have brought this up I
can imagine the issues associated with entering the message loop after an eop.
In
On Jun 13, 2015, at 12:03 PM, Jim Dishaw j...@dishaw.org wrote:
On Jun 11, 2015, at 12:29 AM, Jim Dishaw j...@dishaw.org
mailto:j...@dishaw.org wrote:
On Jun 10, 2015, at 11:30 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca
mailto:ir...@beluga.phys.uvic.ca wrote:
snip
Just to
Okay, well if you need any help or testing let me know.
Something that I haven't seen up to now (but maybe I never looked hard enough)
is a spec sheet for how to write a driver, I.e. What events should a buffer
deal with and in what way. Given the effort I've just been through with
rewriting
On Jun 13, 2015, at 1:13 PM, Phil Rosenberg p.d.rosenb...@gmail.com wrote:
Hmmm
Then h some more
Followed by an ummm or two.
As you say Jim, clearly things are more complicated than I realised. I'm not
sure what the requirements really are here now. Now you have brought this up
I
On Jun 13, 2015, at 3:25 PM, Phil Rosenberg p.d.rosenb...@gmail.com wrote:
Okay, well if you need any help or testing let me know.
Something that I haven't seen up to now (but maybe I never looked hard
enough) is a spec sheet for how to write a driver, I.e. What events should a
buffer
On 2015-06-13 17:15-0400 Jim Dishaw wrote:
On Jun 13, 2015, at 3:25 PM, Phil Rosenberg p.d.rosenb...@gmail.com wrote:
Okay, well if you need any help or testing let me know.
Something that I haven't seen up to now (but maybe I never looked hard
enough) is a spec sheet for how to write a
