Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!execu!sequoia!uudell!natinst!davoli
From: davoli@natinst.com (Russell Davoli)
Newsgroups: comp.sys.mac.programmer
Subject: Re: OOP--What do you think?
Message-ID: <22287@natinst.natinst.com>
Date: 23 Apr 91 14:38:10 GMT
References: <1991Apr10.210516.25812@rice.edu> <51593@apple.Apple.COM> <1991Apr22.191744.16196@cica.indiana.edu>
Organization: National Instruments, Austin, TX
Lines: 23

In article <1991Apr22.191744.16196@cica.indiana.edu>, gtall@ogre.cica.indiana.edu (Gerry Allwein) writes:
> I've been following the OO-debate and being a heavy MacApp user, I do have a
> question with respect to what is supported and what isn't. Floating windows
> are on top of my list for Fun Things To Have What Apple Won't Support. Even
> HyperCard has floating windows built into it now because they work well within
> the Interface guidelines and are particularly useful. Will MacApp 3.0
> support floating windows? And if not, what does it take to get the MacApp
> engineers to recognize a feature of Mac programs as something standard enough
> to be supported? I don't buy the criticism that since MacApp doesn't support
> a lot of things, it isn't useful. You simply have to work a little harder to
> get some things. But this is one I don't feel I should have to work hard to
> get.
> 

I don't think anyone should assume that the MacApp team doesn't think
floating windows are useful just because such windows aren't implemented
in the current version of MacApp (I last used v. 2.0).  If memory serves,
I believe there was an unused "fFloating" field in the TWindow class, which
leads me to suspect that MacApp will someday offer floating windows, too.
It's been a while since I've looked at the MacApp stuff (I spend most of my
time writing drivers) so I welcome corrections.

--Russell