[BUG] Walkback Trying to Debug STBFileIn Problem

This is my first attempt at debugging an STBFileIn problem so if I'm barking
up the wrong tree don't hesitate to say so. I was trying to debug a problem
filing in an STB file so in Object>>binaryReadFrom:context: I changed the
code to:

 ^(STBDebugger on: aStream) context: anObject; next.

Is this the correct usage of STBDebugger?


When I then tried to file in the offending STB file I got the following
walkback:

20:41:24, 12 January 2001: 'STBPrefix does not understand #allMask:'
STBPrefix(Object)>>doesNotUnderstand:
STBDebugger(STBInFiler)>>readClassData:
STBDebugger>>basicNext
STBDebugger(STBInFiler)>>next
STBDebugger>>next
Object class>>binaryReadFrom:context:
Object class>>binaryReadFrom:
PaymentManagerShell(DocumentShell)>>streamIn:
PaymentManagerShell(DocumentShell)>>fileLoad
PaymentManagerShell(DocumentShell)>>fileOpen
Symbol>>forwardTo:
[] in Command>>value
BlockClosure>>ensure:
Command>>value
PaymentManagerShell(Shell)>>performCommand:
CommandQuery>>perform
DelegatingCommandPolicy(CommandPolicy)>>route:
[] in ShellView(View)>>onCommand:
BlockClosure>>ensure:
Cursor>>showWhile:
ShellView(View)>>onCommand:
ShellView(View)>>wmCommand:wParam:lParam:
ShellView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
InputState>>pumpMessage:
InputState>>loopWhile:
InputState>>mainLoop
[] in InputState>>forkMain
ExceptionHandler(ExceptionHandlerAbstract)>>markAndTry
[] in ExceptionHandler(ExceptionHandlerAbstract)>>try:
BlockClosure>>ensure:
ExceptionHandler(ExceptionHandlerAbstract)>>try:
BlockClosure>>on:do:
[] in BlockClosure>>newProcess

I think my original problem with being unable to file in the STB was due to
my app having a listview/list model on which I had clicked a column heading
before saving, there's an article on the WIKI about List Presenters and
Sorting so I need to take remedial action.



--
Ian Oldham

I am addicted but I can't get the T-shirt to prove it - they've sold out

Ian,

>  ^(STBDebugger on: aStream) context: anObject; next.
>
> Is this the correct usage of STBDebugger?

Looks OK, although I'm not sure if you actually need to specify the context?

> When I then tried to file in the offending STB file I got the following
> walkback:

'tis broke. Bill did mention it in a post on 15/12 but there was no reply
from OA - not to say that it hasn't been fixed in the forthcoming update of
course.

As a temporary fix you could try adding the following which allows the
STBDebugger to work well enough to display the contents of the object but
may have side effects (he said, covering himself just in case <g>)

STBDebugger>>readClassData: prefix
    ^super readClassData: prefix dword

Ian

Ian and Ian,

> I think my original problem with being unable to file in the STB was due
to
> my app having a listview/list model on which I had clicked a column
heading
> before saving, there's an article on the WIKI about List Presenters and
> Sorting so I need to take remedial action.

That could easily be the problem.  Of course, if you've changed instance
variable layouts (or if 4.0 changed them for you), you might need to write a
conversion method.

The calls stack you posted does _not look like a problem creating the view,
but, I have noticed that some/all of my older views (those last edited in
2.1) don't want to load into 4.0 due to STB versioning problems - the remedy
is to fire up 3.06 and export to a vu file, and then import into 4.0.



> As a temporary fix you could try adding the following which allows the
> STBDebugger to work well enough to display the contents of the object but
> may have side effects (he said, covering himself just in case <g>)
>
> STBDebugger>>readClassData: prefix
>     ^super readClassData: prefix dword

Nice work!!!!  I failed to see this and ended up creating a cloned STB
debugger :(

Have a good one,

Bill

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