| |
Most recent update was on January 8, 1996. If you'd like to
submit something to the FAQ or update something in the FAQ, feel
free to contact Don Yacktman or use our
handy FAQ submission form.
I can't get the MiscShell palette to load. What is wrong?
As noted in the MiscShell class documentation, you must first load
the MiscString palette into IB. If the MiscString palette isn't
loaded, then you'll see errors in the console (from rld, the dynamic
linker) telling you it can't find some of the required symbols. To
autoload the MiscShell palette in IB, be sure that the MiscString
palette is loaded before the MiscShell palette. One way to do this
is to edit the "Palettes = " line in ~/.NeXT/defaults.nibd.
I can't get the InterfaceBuilder in the beta release
of EOF to load my palettes. Why? Is there a fix for this?
There is a bug in the beta version of the Enterprise Objects version
of Interface Builder. This bug will prevent most third party
palettes, including those in the MiscKit, to not load at all. The
workaround is to go into the palette.table file and comment out
the "ExportImages" line. This well known bug is fixed in
the later
versions of IB shipped with EOF 1.0, EOF 1.1, and NS Dev 3.3.
InterfaceBuilder under 3.0 crashes upon launch with
the message "Uncaught exception: NXReadOnlyString does not
respond to -replaceWith:" after using some MiscKit palettes.
Having too many palettes available seems to tickle a bug in 3.0
(either in NEXTSTEP or in Interface Builder). If the combined path
length of all your palettes is longer than 1024 characters, then
restarting IB will give you the error: "Uncaught exception:
NXReadOnlyString does not respond to -replaceWith:". For the
time being, deleting the file ~/.NeXT/defaults.nibd before restarting
IB will allow you to get IB up and running again. Before quitting
IB, you should unload the MiscKit palettes. Note that moveing
the palettes to a path with a shorter name will also help reduce
the problem. Try making a link like this:
ln -s /LocalDeveloper/Palettes /p
That should provide a short enough path to still allow loading
of many palettes. Later NEXTSTEP releases seem to
have fixed this bug. Some people have, however, reported this
problem with NEXTSTEP releases 3.1 and 3.2 as well.
|
