Path: utzoo!attcan!uunet!wuarchive!rex!uflorida!gatech!mcnc!decwrl!sgi!betsy@vesuvius.esd.sgi.com
From: betsy@vesuvius.esd.sgi.com (Betsy Zeller)
Newsgroups: comp.sys.sgi
Subject: Re: stdin under Workspace
Message-ID: <73276@sgi.sgi.com>
Date: 25 Oct 90 21:06:01 GMT
References: <2260@bnlux0.bnl.gov>
Sender: guest@sgi.sgi.com
Reply-To: betsy@vesuvius.UUCP (Betsy Zeller)
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 33

In article <2260@bnlux0.bnl.gov> bstewart@bnlux0.bnl.gov (Bruce Stewart) writes:
>I have just joined the world of 4D series, and have a problem with
>my graphics application software. I use the texport as dialog area; all
>works well when I run the application by typing the command to
>Irix in a shell. But when I start the application from Workspace,
>all attempts at scanf on stdin return EOF, without giving me a
>chance to type anything in the textport. I have already noticed
>that the console icon must be opened prior to starting the
>application from Workspace. What else am I missing?
>
>Any clues would be appreciated.
>
>bstewart@bnlux0.bnl.gov

To make your application run from workspace so that it will use scanf
effectively, you need to tag it. Try doing this

	tag 0x400 your_application_name

Your application will now appear on workspace as a little picture of 
a terminal window. When you double click it, a text window will open,
showing you any text or prompts, and into which you can enter your input.
When you are done, close that window.

Tagging is the mechanism workspace uses to identify what icon to display,
and what behaviour to supply for a given file. The ascii files from which
workspace gets its information are in /usr/lib/filetype/default, install,
local, and system.

Any application which puts up its own window to run in will run just
fine from workspace without being tagged.

Betsy Zeller