Forum unknown
· Help/Announcements
#Multiple Ports/Icon
17 messages in this thread
Answer to your first question—I don't know, but I would take a
guess at yes. There are add-on boards with serial ports included. I would
guess that adding a serial port that can't be addressed would be a waste of
money. q.e.d. it can be addressed separately.
To your 2nd question, Yes, an icon can execute a command file. For
example, on Textcraft (and other's) you can click on a text file and it will
load the WP and then that particular "letter" into the program. The
information on which program is run from the icon is in the WBObject and
DiskObject structures within the icon itself. Basically, what you need is a
Project ICON and the application program that created that icon will also be
loaded. Now if you wanted to click on an icon and have it load a batch
command file (execute file), that may be a little trickier, but I am sure it
can be done.
don't worry, there's provisions for multiple serial ports or whatever.
essentially they are handled like multiple drives – there's a structure with
a "unit number" in it that points to the serial handler code and device name
and such. i don't have all the details, cuz i don't have manuals – i go sit
in corners at user group meetings and read ray brand's RKMs. –Scotty
don't worry, there's provisions for multiple serial ports or whatever.
essentially they are handled like multiple drives – there's a structure with
a "unit number" in it that points to the serial handler code and device name
and such. i don't have all the details, cuz i don't have manuals – i go sit
in corners at user group meetings and read ray brand's RKMs. –Scotty
First, create your Project icon, then save it. Next: Click ONCE on the Icon
then go to the Workbench menu and select Info. Once the Info screen comes up,
in the Default Tool space type C/EXECUTE. SAVE your work then double-click on
the icon and see if it works!
Right, I know it can be done, I just haven't done it myself and was passing
the information on. I think your idea should work though but I honestly
don't know at this point, I'll try it and see. Don
Right, I know it can be done, I just haven't done it myself and was passing
the information on. I think your idea should work though but I honestly
don't know at this point, I'll try it and see. Don
Unfortuately, Execute just isn't set up to accept its argument from the
WorkBench. Doing what you suggested brings you nothing more than a visit
from the Guru (under 1.1, anyway — another suggestion for 1.2/1.3?) Anyone
want to write a WBExecute program? – Bela
Bela;
Oops. (Said with foot in mouth). Sorree….That might be an interesting
project, at that!
John
There's another weakness in AmigaDOS, specifically in WorkBench. One of the
things that you can set via Info should be a bit that says "pass arguments to
this as if it were being invoked from the CLI" (or for a project icon, the
same bit would mean "pass >this< argument to the program as if it were being
run under CLI"). Then you could construct an icon for any CLI program and
WorkBench would handle the difference. Anyone reading this who has direct
contact with the DOS people, pass it on… – Bela PS: hmmm… could a WB
program be written such that you would first click on a project icon, then
double click on this program, and it would do the work? I'm thinking you'd
take the project icon and set its default tool to the CLI command, but then
you'd pass that icon on as an argument to the "run as a CLI command" program.
That program would look up the "default tool" and run it, passing on the
argument as if CLI were invoking the program. Possible? Of course double
clicking on the project icon itself would still do the Guru, but it's a
step…
Hmm…No, 'tis possible to do it the way you say…Have seen a prog floating
around that will print a file in just that manner; i.e. you first click on
the file icon, then double click on the program's icon…That's how Workbench
can pass a parameter, if I'm not mistaken (I might be…) But it really would
be easier to write a WBExecute to work from a standard Project
icon….hmmm…Using some batch-file source from the MyCLI source in DL7
should be ablt to write a Workbench interface in C…..dagnabit, now won't
get any sleep tonight! OP <<Grin>
hehe! I'll look for your program! – Bela
PS: if you're gonna use SU to send your messages, could you type them 80
columns long? Better, don't use SU…
hehe! I'll look for your program! – Bela
PS: if you're gonna use SU to send your messages, could you type them 80
columns long? Better, don't use SU…
Hmm…No, 'tis possible to do it the way you say…Have seen a prog floating
around that will print a file in just that manner; i.e. you first click on
the file icon, then double click on the program's icon…That's how Workbench
can pass a parameter, if I'm not mistaken (I might be…) But it really would
be easier to write a WBExecute to work from a standard Project
icon….hmmm…Using some batch-file source from the MyCLI source in DL7
should be ablt to write a Workbench interface in C…..dagnabit, now won't
get any sleep tonight! OP <<Grin>
There's another weakness in AmigaDOS, specifically in WorkBench. One of the
things that you can set via Info should be a bit that says "pass arguments to
this as if it were being invoked from the CLI" (or for a project icon, the
same bit would mean "pass >this< argument to the program as if it were being
run under CLI"). Then you could construct an icon for any CLI program and
WorkBench would handle the difference. Anyone reading this who has direct
contact with the DOS people, pass it on… – Bela PS: hmmm… could a WB
program be written such that you would first click on a project icon, then
double click on this program, and it would do the work? I'm thinking you'd
take the project icon and set its default tool to the CLI command, but then
you'd pass that icon on as an argument to the "run as a CLI command" program.
That program would look up the "default tool" and run it, passing on the
argument as if CLI were invoking the program. Possible? Of course double
clicking on the project icon itself would still do the Guru, but it's a
step…
Bela;
Oops. (Said with foot in mouth). Sorree….That might be an interesting
project, at that!
John
Unfortuately, Execute just isn't set up to accept its argument from the
WorkBench. Doing what you suggested brings you nothing more than a visit
from the Guru (under 1.1, anyway — another suggestion for 1.2/1.3?) Anyone
want to write a WBExecute program? – Bela
First, create your Project icon, then save it. Next: Click ONCE on the Icon
then go to the Workbench menu and select Info. Once the Info screen comes up,
in the Default Tool space type C/EXECUTE. SAVE your work then double-click on
the icon and see if it works!