This is VideoApp-for-ND-cant-start-on-2-headed-cube. in view mode; [Up]
Date: Sun 04-Jul-1991 09:06:17 From: izumi@mindseye.berkeley.edu (Izumi Ohzawa) Subject: VideoApp for ND can't start on 2-headed cube. When 2-headed NeXTcube (mono chrome + NeXTdimension) is setup to use the Monochrome screen as the ZERO screen (screen on which loginwindow and Dock show up), /NextDevelopers/Demos/VideoApp refuses to start up. It says that the machine can't run video apps. This error occurs because the video window of the app is placed on the Monochrome screen, the current 0 screen. Is there any way to instruct specific apps such that it's video window is placed on NeXTdimension screen in the above 2-headed configuration, preferably in a way which does not depend on configuration and positioning of screens ? Perhaps, the error checking code is not appropriate? Will there be a problem if we allow these apps to start up in monochrome screen, and then if the user drags the video window into the NeXTdimension screen? In the source code provided, in file MyApps.m, method it checks... if(![NXLiveVideoView doesWindowSupportVideo:bufWindow standard:&type size:&vidSize]) { NXRunAlertPanel("No Video Present", "This machine is not capable of running video applications. \ Since this program is exclusively for Video, It will now exit", "OK",NULL,NULL); [self terminate:self]; } // Method doesWindowSupportVideo:standard:size returns NO if // bufWindow is entirely within non-ND window. Instead, what the code should really be doing is to check if ND exist at all, and if it does put up the video window into the ND screen. Does anyone have good solutions to this? Izumi Ohzawa [ $@Bg_78^=;(J ]
Date: Sun 04-Jul-1991 13:24:02 From: lacsap@media.mit.edu (Pascal Chesnais) Subject: Re: VideoApp for ND can't start on 2-headed cube. Dudes, if you have a NextDimension and are running 2.1 you do not want to run a two headed configuration with the monochrome as the primary head. Play around with both configurations and you will see what I mean. VideoApp being brain dead about it is a feature forcing me to change to the ND as the primary head and finding the machine much zippier! If you can afford to, lose the monochrome head... keep it as a spare... pasc In article <1991Jul4.090617.1832@agate.berkeley.edu> izumi@mindseye.berkeley.edu (Izumi Ohzawa) writes: > When 2-headed NeXTcube (mono chrome + NeXTdimension) is > setup to use the Monochrome screen as the ZERO screen > (screen on which loginwindow and Dock show up), > /NextDevelopers/Demos/VideoApp refuses to start up. > > Izumi Ohzawa [ $@Bg_78^=;(J ]
Date: Sun 04-Jul-1991 18:56:22 From: izumi@mindseye.berkeley.edu (Izumi Ohzawa) Subject: Re: VideoApp for ND can't start on 2-headed cube. In article <1991Jul4.132402.395@news.media.mit.edu> lacsap@media.mit.edu (Pascal Chesnais) writes: > >Dudes, if you have a NextDimension and are running 2.1 >you do not want to run a two headed configuration with >the monochrome as the primary head. Play around with >both configurations and you will see what I mean. VideoApp >being brain dead about it is a feature forcing me to change >to the ND as the primary head and finding the machine >much zippier! If you can afford to, lose the monochrome >head... keep it as a spare... You are right, and thank you all for telling me about it. I was too quick to change to the bad 2-headed config, and was too stubborn to change it back. My thought on the lack of performance was "Oh my gosh, I just don't have enough RAM.", but that wasn't it. The performance drops by more than 10 times in this configuration. The swapfile grew to about 70MB in a matter of a few hours. Is there still some performance degradation if I keep the monochrome head? Other than loss of real deskspace, why is it better to lose the monochrome head? It's nice to have the extra workspace, and I like to do non-color text work, like reading on-line DOC, terminal sessions on the monochrome screen. The color screen is not bad, but monochrome is much easier on the eyes for fine text. Izumi Ohzawa [ $@Bg_78^=;(J ]
Date: Sun 04-Jul-1991 23:51:57 From: gmk@ucsc.edu (Gottfried Mayer-Kress) Subject: Re: VideoApp for ND can't start on 2-headed cube. In article <1991Jul4.090617.1832@agate.berkeley.edu> izumi@mindseye.berkeley.edu (Izumi Ohzawa) writes: > When 2-headed NeXTcube (mono chrome + NeXTdimension) is > setup to use the Monochrome screen as the ZERO screen > (screen on which loginwindow and Dock show up), > /NextDevelopers/Demos/VideoApp refuses to start up. > > It says that the machine can't run video apps. > This error occurs because the video window of the app > is placed on the Monochrome screen, the current 0 screen. > This means you CAN run VideoApp on 2-headed cube, you just have to switch the startup configuration such that the zero screen is the color screen. Please try to avoid incorrect or misleading headers for your messages.
Date: Sun 05-Jul-1991 01:45:58 From: izumi@mindseye.berkeley.edu (Izumi Ohzawa) Subject: Re: VideoApp for ND can't start on 2-headed cube. In article <17752@darkstar.ucsc.edu> gmk@ucsc.edu (Gottfried Mayer-Kress) writes: >In article <1991Jul4.090617.1832@agate.berkeley.edu> >izumi@mindseye.berkeley.edu (Izumi Ohzawa) writes: >> When 2-headed NeXTcube (mono chrome + NeXTdimension) is >> setup to use the Monochrome screen as the ZERO screen >> (screen on which loginwindow and Dock show up), >> /NextDevelopers/Demos/VideoApp refuses to start up. >> >This means you CAN run VideoApp on 2-headed cube, you just have to switch >the startup configuration such that the zero screen is the >color screen. > >Please try to avoid incorrect or misleading headers for your messages. I stand by my title, and don't think that was incorrect or misleading that much. In any case, I had reasons for wanting to use monochrome screen as the primary display, but now I will use ND as the primary display given the performance penalty. Given all this though, I would like very much some way of specifying, on application by application basis, the screen on which menus and windows are first placed. For example, I always want Terminal and Edit windows and menus to appear on Monochrome display if it is present, while video apps should always appear on an ND screen. Izumi Ohzawa [ $@Bg_78^=;(J ]
Date: Sun 05-Jul-1991 13:45:21 From: korp@atlantis.ees.anl.gov (Peter Korp) Subject: Re: VideoApp for ND can't start on 2-headed cube. There are two ways to make VideoApp start if using the Mono screen as the default. You can start IB and use the window inspector on the main window and check the option "Wants to be Color", save the IB file recompile and run. Alternatively you could simply yank the code that does the check for the video screen, recompile and run. As an aside, I run my ND with the Color screen as the primary display but still get swap files in the 70MB range in just a few hours. Is it just time to invest in more ND memory? Peter
Date: Sun 08-Jul-1991 18:41:45 From: aozer@next.com (Ali Ozer) Subject: Re: VideoApp for ND can't start on 2-headed cube. In article <1991Jul4.090617.1832@agate.berkeley.edu> Izumi Ohzawa writes: >When 2-headed NeXTcube (mono chrome + NeXTdimension) is >setup to use the Monochrome screen as the ZERO screen >(screen on which loginwindow and Dock show up), >/NextDevelopers/Demos/VideoApp refuses to start up. > ... >Instead, what the code should really be doing is to >check if ND exist at all, and if it does put up the video >window into the ND screen. > >Does anyone have good solutions to this? NXLiveVideoView has a factory method + (const NXScreen *)videoScreen; which returns a screen capable of video. Thus a window could be created with the method - initContent:(const NXRect *)contentRect style:(int)aStyle backing:(int)bufferingType buttonMask:(int)mask defer:(BOOL)flag screen:(const NXScreen *)screen; by specifing [NXLiveVideoView videoScreen] as the screen argument. If a window is being created through IB, then one reasonable substitute is to check the "Wants Color" switch in the window inspector; this will cause the window to open up on a color screen, which, in the case of the 2-headed ND, will be the video screen as well... Or you can create the window in a default location, and, in an outlet setting method, move the window to the [NXLiveVideoView videoScreen]. Ali, Ali_Ozer@NeXT.com
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.