[Prev][Next][Index][Thread]
Re: GetIconSuite unimplemented?
>>>>> "Clay" == Clay Helberg <helberg@maddog.fammed.wisc.edu> writes:
In article <4ek4ua$ndo@news.doit.wisc.edu> helberg@maddog.fammed.wisc.edu (Clay Helberg) writes:
Clay> I'm trying to run a statistics package called JMP-IN (a
Clay> student version of JMP), and when I try to run it, I get a
Clay> fatal error: C_GetIconSuite unimplemented. Please let me
Clay> know what my options are:
Clay> a) If I've screwed something up in configuring
Clay> Executor, please tell me what it is so I can fix it
Clay> b) If it's a problem with Executor itself, is there a
Clay> workaround? If so, what is it?
Clay> c) If there's no current workaround, will this be
Clay> fixed in version 2.x?
There is no current workaround, but starting with 1.99q3, Executor
will try to continue running after GetIconSuite is called. However,
we still haven't implemented GetIconSuite, so the program may quite
possibly die after the call to GetIconSuite fails.
Currently we do not plan to support the icon routines in Executor 2.
Most programs use "Gestalt" to determine whether or not the routines
are present and don't call the routines when they're not there.
Once Executor 2 is shipping, adding support for those routines becomes
a very high priority task, since they're on the cusp of being
important enough to support in Executor 2 already.
Clay> d) If not, should I just give up trying to run this
Clay> app under Executor?
I'd guess that we'll have support for those routines by April, but
that's a guess. Writing the routines isn't really that hard, but
getting Executor 2 out the door is, and that's what's taking up all
our engineers right now.
Clay> Thanks in advance for any assistance.
Clay> --Clay
Clay> -- Clay Helberg | Internet:helberg@maddog.fammed.wisc.edu
Clay> Research Design & Statistics Unit | Bitnet: clavius@wiscmacc
Clay> Schools of Medicine & Nursing |
Clay> http://maddog.fammed.wisc.edu/~helberg University of
Clay> Wisconsin-Madison | Speaking only on my own behalf....
--Cliff
ctm@ardi.com
Follow-Ups:
References: