cmcmanis%pepper@Sun.COM (Chuck McManis) (06/09/88)
In article <34776@amdahl.uts.amdahl.com> (Kevin Clague) writes:
-> 3. Using the name string and the file lock (and Examine() and
-> ParentDir()) I create a string that contains the full path name
-> of my program. This tells me where the user has put my program
-> before executing it. Later I use this as the ToolType in any
-> project Icons that are written to disk.
Not the ToolType, should be in the DefaultTool pointer.
-> 5. When the user saves projects to disk, if the program was started
-> from the CLI, I don't create icons for it. If started from the
-> WBench I write out icons using the freshly created tooltype
-> string created in step 3.
You should also check to see if the icon already exists, and if so *not*
overwrite it. (The user may have customized it) Also see the comment
above about where the default tool goes.
-> I'm a CLI kinda guy. The WorkBench stuff is all new to me. Is this
->the proper approach? Am I working too hard at the ToolType stuff?
->Does the system handle this in some other kinda way? Am I missing
->anything? Inquiring minds WANT to know!
-> -kevin
Seems like you are right on track. Wish more people would consider it for
their programs.
--Chuck McManis
uucp: {anywhere}!sun!cmcmanis BIX: cmcmanis ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.spencer@eris.berkeley.edu (Randal m. Spencer [RmS]) (06/10/88)
Recently on *comp.sys.amiga.tech* kevin@amdahl.uts.amdahl.com (Kevin Clague) wrote: ...In article <55844@sun.uucp> cmcmanis@sun.UUCP (Chuck McManis) writes: ... >In article <34776@amdahl.uts.amdahl.com> (Kevin Clague) writes: ... ... stuff deleted.... ... ... >-> Later I use this as the ToolType in any ... >-> project Icons that are written to disk. ... > ... >Not the ToolType, should be in the DefaultTool pointer. ... ... Duh... Yes. Sorry I meant Default Tool type.... ...ToolTypes allows user/programmer defined parameters to be kept in ...icons. Question for all you Workbench programmers out there. I have a program that is distributed on a disk and when the user creates a project the default tool is Name:filename. I used to have a program that created an absolute path, but I found myself moving it around so much (and I had more floppies in those days) that a relative assign seems easier. If the user has the program on floppy, fine, otherwise he does an assign, like I have Dpaint: and ProWrite: on my hard disk (and Manx: and Lattice:, etc...) All the assigns take time to do, but I just run a background CLI at a low priority that sets up my hard disk when I boot. And if the assign hasn't been made (yet) I get a requester that says "Please insert ProWrite:" and I either find the disk, or click Retry when the background startup is done. I can see some merit to doing it so that when the program has been moved the user starts up the program and finds the file, or Shift-Clicks on the program and the file, but I am not sure which is better...Anyone? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Randy Spencer P.O. Box 4542 Berkeley CA 94704 (415)222-7595 spencer@mica.berkeley.edu I N F I N I T Y BBS: (415)222-9416 ..ucbvax!mica!spencer s o f t w a r e AAA-WH1M -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-