T.R | Title | User | Personal Name | Date | Lines |
---|
1981.1 | some comments | CALL::SWEENEY | International House of Workstations | Fri Dec 29 1989 21:10 | 44 |
| Ken (PROJECTS), please don't title your notes "BUG" or "X Window
features denied by DECwindows", it's terribly uniformative and in the
latter case argumentative and irritating.
Do you really expect one of us to say "We're dumb. We've devoted the
better part of two years (for my part) to DECWINDOWS and now we
discover what we have created is a subset?" Give the hundreds of
dedicated Digital employees associated with DECwindows some credit,
won't you?
You are wrong and you need to spend a lot more time reading the
documentation, looking at examples, and modifying them before you can
begin to understand how much there is that you don't know.
A graphics context is a data structure of the _server_ and the created
using the _display_. Multiple windows can/do/should share graphics
contexts. You should already know that.
A widget is a data structure of the _client_. When created the window
field is not valid. It becomes valid after XtRealize is called and a
valid window value is filled in. If you need to use window a before
anything is realized but after the display is open, then use the root.
You should already know what the root window is and how to obtain
information on it. Also, I beginning to believe that you don't have a good
grasp of what the difference is between a window and a widget.
I suggest that you add
"if (window == NULL) {
printf ("I'm calling X with a null window\n");
exit(0);
}"
before each of your calls to an X routine which requires a window.
The term "private color cell strategy" doesn't mean anything to me. In
X (and in DECwindows!!) colors, color cells, and color planes can be
allocated and new color maps created. Colors and color maps are
associated with a display and screen. All are available to any window
of a matching visual type.
You should know that many, many other notes exist in this conference
discussing colors in detail.
Patrick Sweeney
|
1981.2 | Please observe noting etiquette. | TROPPO::RICKARD | Doug Rickard - network junkie. | Sat Dec 30 1989 16:29 | 21 |
| Dear Projects,
To not give your name, AND use an impersonal username like PROJECTS is
considered to be the height of noting rudeness.
I have sent you personal mail regarding this but you still persist.
One could form the opinion from your rather aggravating note titles
and the fact that you do not wish to identify yourself, that in fact
you don't really want answers but are just doing some stirring.
There is a noting etiquette - there are even documents available on it.
You will become known for your noting style.
Doug Rickard, noter.
-------------------
Networks and Communications Consultant
Brisbane
Australia
|
1981.3 | | AITG::DERAMO | Daniel V. {AITG,ZFC}:: D'Eramo | Sat Dec 30 1989 21:19 | 7 |
| I sent similar mail, and at least one note afterwards was
signed "Ken".
It's a start. You can always send mail to SYSTEM on
that node if you are still curious.
Dan
|
1981.4 | Reveal yourself! | GOLLY::MILLER | I need 'Deeper Understanding' | Sun Dec 31 1989 10:42 | 5 |
| Don't give us "Ken's" a bad reputation! ;)
Regards,
== ken miller ==
|
1981.5 | Just trying to help a new noter... | TROPPO::RICKARD | Doug Rickard - network junkie. | Sun Dec 31 1989 17:27 | 16 |
| Re: .3
> It's a start. You can always send mail to SYSTEM on
> that node if you are still curious.
Hi Dan,
No, I'm not curious. Just trying to help a new noter learn the
culture. I guess we all made our own gaffes somewhere along the way -
(some of us have even learnt how to edit an existing note to change
something we didn't really mean to say :-))
I guess its something we don't realize at first - just how one gets
recognised by their noting style, even their nicknames, e.g. 'mulp'....
Doug.
|
1981.6 | X WINDOW and DECWINDOWS logic question | FREZEN::PROJECTS | | Mon Jan 01 1990 11:30 | 10 |
|
re. 1
Please excuse the sloppyness and unintended perceptions, and thanx
for the somewhat reply to my question that got deleted by accident.
Much appreciated
Ken 1-508-264-2360
|