🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.sys.acorn.tech
3 messages
3 total messages Started by pdenize Fri, 13 Nov 1992 02:18
Windows and Pains :-) OK, Panes ...
#409
Author: pdenize
Date: Fri, 13 Nov 1992 02:18
19 lines
1206 bytes
I have written a program and it has a window in a window.  The two are intended
to be joined together so I made the one on top a pane.

But when the user clicks on the top of the back window I get an open event and
then have to open the other in front again.  Thus when the user holds the title
bar the pane flashes (albeit very fast)

Can someone tell me how it should be done ?

Paul Denize.

--------------------------------------------------------------------------
Paul Denize                                Internet: PDenize@Waikato.ac.nz
Department of Computer Science
University of Waikato                         phone: ++64 7 8562-889
Hamilton                                                          Ext 8743
NEW ZEALAND                                   fax  : ++64 7 8560-135
--------------------------------------------------------------------------
Re: Windows and Pains :-) OK, Panes ...
#427
Author: Chris Dollin
Date: Fri, 13 Nov 1992 14:02
14 lines
1288 bytes
THis stuff about panes reminds me.

What is the *advantage* of defining a window to be a pane? I mean, when you
move the parent window, you have to move the pane *yourself* -- the WIMP
doesn't do it for you. What does making it a pane give you over making it an
ordinary window and tracking opens of its logical parent?

I read the WIMP section of the PRM several times, looking for an answer, some
time ago, but found one not. Can anyone enlighten me?
--

Regards,    | "Layered protocols give the software implementor a chance to
Kers.       | ruin his performance in each layer." - Don Gillies
Re: Windows and Pains :-) OK, Panes ...
#524
Author: D.Pead
Date: Mon, 16 Nov 1992 17:35
16 lines
1038 bytes
My technique for opening panes is, on getting the redraw request:

1. <behind>= "handle of window to open behind" field from open request

2. Calculate position of Pane 1 (don't corrupt data for main window)
3. Open Pane 1 behind <behind>
4. <behind> = Pane 1 handle

5. Repeat steps 2-4 for subsequent panes

6. Open main window behind <behind>

Oh yes - ignore "Open Window Requests" for panes.
This seems to work without any flickering, although "solid drags"
of a window+pane combination are never quite as smooth as a single
window.
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads