| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
Is there any way to have a *single* DECW$CLOCK process running on a node direct it's output to several workstations? I assume not, but for an application such as clock whose only input is window sizing and clip priority it's a reasonable customer expectation... thanks, -dale
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1170.1 | looks like none are multi-threaded today | NCBDVX::HOHMD | Dale Hohm, on site @PDS 515-270-3945 | Tue Jul 25 1989 13:10 | 9 |
with dir/title I've answered my own question...
reading notes 282.* and others it appears that none of the out of the
box applications have been written multi-threaded (yet)
one for the wish list
-dale
| |||||
| 1170.2 | Controversy about clock? | SDSVAX::SWEENEY | Honey, I iconified the kids | Tue Jul 25 1989 14:02 | 8 |
First of all, clock has input, MB2 produces a popup.
Secondly, why is it a reasonable customer expectation that the clock
client application connect to multiple display servers simultaneously?
For an out of the box (OOTB) application and not a layered product, I'd
say that is an unreasonable expectation.
| |||||