Package prerequistes after deleting view class

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Package prerequistes after deleting view class

Bill Schwab
Hi Blair,

This happened in 4.0, but, it's probably worth mentioning here as it will
likely have bad interactions w/ the new package browser.

I created a subclass of ScrollingDecorator, and then made a
CompositePresenter view resource for it.  The idea worked, but, shortly
thereafter, I realized how to use #preferredExtent to get ScrollingDecorator
to do the same thing.  I made the required changes, tested it, and deleted
the subclass.  However, I forgot about the resource.  Later, looking for
prerequisites for the owning package generated a walkback (below).

Have a good one,

Bill



2:26:11 AM, Thursday, January 31, 2002: Unhandled exception - a
MessageNotUnderstood('UndefinedObject does not understand #stbVersion')

UndefinedObject(Object)>>doesNotUnderstand:
STBViewProxy>>stbFixup:at:
STBInFiler>>basicNext
ResourceSTBByteArrayAccessor>>hiddenObjects
ResourceSTBByteArrayAccessor(ResourceAccessor)>>hiddenClassReferences
ViewResource(Resource)>>hiddenClassReferences
[] in Package>>tracePrerequisitesOfResources:
Set>>do:
Package>>tracePrerequisitesOfResources:
Package>>tracePrerequisites:
Package>>tracePrerequisites
Package>>calculatePrerequisites
Package>>buildPrerequisiteNames
Package>>getPrerequisites
[] in PackagePrerequisitesShell>>childrenFor:
BlockClosure>>ifCurtailed:
BlockClosure>>ensure:
Cursor>>showWhile:
PackagePrerequisitesShell>>childrenFor:
MessageSend>>valueWithArguments:




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


Reply | Threaded
Open this post in threaded view
|

Re: Package prerequistes after deleting view class

Blair McGlashan
"Bill Schwab" <[hidden email]> wrote in message
news:[hidden email]...
> Hi Blair,
>
> This happened in 4.0, but, it's probably worth mentioning here as it will
> likely have bad interactions w/ the new package browser.
>
> I created a subclass of ScrollingDecorator, and then made a
> CompositePresenter view resource for it.  The idea worked, but, shortly
> thereafter, I realized how to use #preferredExtent to get
ScrollingDecorator
> to do the same thing.  I made the required changes, tested it, and deleted
> the subclass.  However, I forgot about the resource.  Later, looking for
> prerequisites for the owning package generated a walkback (below).
>....

Thanks Bill, #529.

Regards

Blair