Error saving package

Hi,

When I try to save a package, I get an error message complaining that
'the package will NOT load if saved in this for, so the package file
has no t been saved'

Anybody knows what might be causing this?

Thanks

Fernando,

> When I try to save a package, I get an error message complaining that
> 'the package will NOT load if saved in this for, so the package file
> has no t been saved'
>
> Anybody knows what might be causing this?

This is an important milestone in your Dolphin use.  It might _seem_
terrible at the moment, but not to worry.  The problem is that you have
a package that depends on one of its prequisites, forming a cycle.

Searching the archives and wiki for cyclic prerequisites will turn up
some helpful tips.  The place to start is in the package browser's
prerequisites tab; turn on the show status icons options, and look for
the red icons.  Repackage things that look out of place until the
problem goes away.

FWIW, I have found that tests are common offenders, and moving an
individual #test* method as a loose method in more specialized package
can often fix an otherwise horrible looking cycle.

Most importantly, rememeber that you can save and backup images to
protect your work until you find the packaging problem.  After a while,
they become (almost<g>) easy to fix.

Have a good one,

Bill


--
Wilhelm K. Schwab, Ph.D.
[hidden email]

Fernando,

> When I try to save a package, I get an error message complaining that
> 'the package will NOT load if saved in this for, so the package file
> has no t been saved'

It's likely to be one of two related causes.

1) (which Bill has already mentioned) You have cyclic pre-requisites.  I.e.
your package depends on another package which in turn depends on the first
package.  To track this down, go to the Package Browser's 'Prerequisites' tab,
and turn on (from the context menu) 'Show status icons' which (poorly named)
option will cause Dolphin to display a red cross next to any package that has
cyclic pre-requisites.  From that it should be easy enough to track down the
problem.

2) You package depends on some class (or whatever) that is not itself in a
package.  The PB's prerequisites tab will show such package as depending on the
pseudo-package '<Unpackaged>'.  And, again, it should be simple to track down
the problem from there.

BTW, when the error message pops up, the prompt finishes:
    'Would you like to browse the package prerequisites in order to track down
the problem?'
It's often a good idea to answer Yes to such questions ;-)

    -- chris

On Fri, 22 Apr 2005 09:17:04 +0100, "Chris Uppal"
<[hidden email]> wrote:


>2) You package depends on some class (or whatever) that is not itself in a
>package.  The PB's prerequisites tab will show such package as depending on the
>pseudo-package '<Unpackaged>'.  And, again, it should be simple to track down
>the problem from there.

That's the problem, it uses 2 globals that aren't packaged. How can I
package a global variable?

"Fernando Rodriguez" <[hidden email]> wrote in message
news:[hidden email]...
> That's the problem, it uses 2 globals that aren't packaged. How can I
> package a global variable?

In package browser, select the desired target package, in menu select File|
Ad uncommited> | Global

I guess there is also some drag'n'drop with same effect.

rush
--
http://www.templatetamer.com/
http://www.folderscavenger.com/

Fernando,

> That's the problem, it uses 2 globals that aren't packaged. How can I
> package a global variable?

Yes.  Use the PB, select the package, go to the globals tab and choose
add uncommitted from the ctx menu.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]