Show inherited methods bug

The handle is invalid error appears when I enable Show  Inherited
Methods AND click on an inherited method.

Costas

On Sat, 04 May 2002 20:48:15 GMT, [hidden email] (Costas) wrote:

>The handle is invalid error appears when I enable Show  Inherited
>Methods AND click on an inherited method.

In addition, this message does not appear if you click on the pink
methods. It seems to occur with the Dolphin package methods.

Regards

Costas

Costas,

> >The handle is invalid error appears when I enable Show  Inherited
> >Methods AND click on an inherited method.
>
> In addition, this message does not appear if you click on the pink
> methods. It seems to occur with the Dolphin package methods.

I don't see this here. Can you give us an exact sequence to reproduce it and
let us know what OS you are using. First thing to try, though, is a "Panic".
I wonder if you have any xombie windows lurking in the image.

Best Regards,

Andy Bower
Dolphin Support
http://www.object-arts.com
---
Are you trying too hard?
http://www.object-arts.com/Relax.htm
---

On Tue, 7 May 2002 07:29:39 +0100, "Andy Bower"
<[hidden email]> wrote:

Andy,

What does a Panic do and where would this xombie have come from?

Thanks

Costas

Costa,

> What does a Panic do and where would this xombie have come from?

>From SmalltalkSystemShell>>panic:

panic
    "Forcibly close all views to clean up if necessary"

    (MessageBox new taskModal; confirm:
        'Are you sure you wish to forcibly close all open windows?
        If so, all windows will be destroyed and a new System Folder will be
opened.
        You should do this only if you believe you may have hidden or
partially
        composed windows in your image that are preventing some objects from
        otherwise being garbage collected.')
            ifTrue: [[View destroyAll] on: Error do: [:x | x notify]]

You can see that it forcibly closes all views and ignores errors. Zombie
views can arise if an error occurs during the opening and closing of a
window or, perhaps, if you set a breakpoint in window initialization and
then don't do a resume from within the debugger.. The end result is you may
have instances of View kicking around in your image that have invalid
handles. They may events registered for them and, if the event is triggered,
will often cause a walkback because of the invalid handles in the view
objects.

Best Regards,

Andy Bower
Dolphin Support
http://www.object-arts.com
---
Are you trying too hard?
http://www.object-arts.com/Relax.htm
---

Andy,

I tried the Panic button and it does not help.  I am running a Windows
2000 Professional with 392 MB Ram. Windows and Dolphin run on my G:
drive instead of C:. Later I will try to reinstall Dolphin and see if
it goes away.

The steps are as follows:

Start Dolphin
Start Class Browser from anywhere
Click Method/Show Inherited
Select Class Tab pane
Click on any grayed out method (Dolphin pkg) in class methods pane.

You get the following message:   *** The operation completed
succesfully(16r0...) **** and a long    walkback.
Click Terminate.

Click again in any grayed out method again and you get the following
message "*** The handle is invalid ( 16r6)

Below is the initial walkback for
    *** The operation completed succesfully(16r0...) ****

 GDILibrary(ExternalLibrary)>>systemError
IndexedColor>>asRGBUsingPalette:
IndexedColor>>asRGB
IndexedColor(Color)>>fadedBy:
[] in UndefinedObject>>{unbound}doIt
NMLVCUSTOMDRAW(NMCUSTOMDRAW)>>evaluateDrawBlock:
ListView>>customDrawSubItem:
ListView(IconicListAbstract)>>nmCustomDraw:
ListView(ControlView)>>nmNotify:
[] in ListView>>nmNotify:
Array(SequenceableCollection)>>at:ifAbsent:
ListView>>nmNotify:
ReferenceView(View)>>wmNotify:wParam:lParam:
ReferenceView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
ListView(ControlView)>>defaultWindowProcessing:wParam:lParam:
ListView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
ListView(View)>>sendMessage:wParam:lpParam:
ListView>>basicItemFromPoint:
ListView>>itemFromPoint:
ListView>>selectionFromPoint:
ListView>>onButtonPressed:
ListView>>onLeftButtonPressed:
ListPresenter(Presenter)>>onLeftButtonPressed:
ListView(View)>>wmLButtonDown:wParam:lParam:
ListView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
ShellView(View)>>isDialogMessage:
ShellView>>preTranslateMouseInput:
ShellView(View)>>preTranslateMessage:
InputState>>preTranslateMessage:
InputState>>pumpMessage:
InputState>>loopWhile:
InputState>>mainLoop
[] in InputState>>forkMain
ExceptionHandler(ExceptionHandlerAbstract)>>markAndTry
[] in ExceptionHandler(ExceptionHandlerAbstract)>>try:
BlockClosure>>ifCurtailed:
BlockClosure>>ensure:
ExceptionHandler(ExceptionHandlerAbstract)>>try:

Costas,

What is your Windows display colour setting (8bit, 16bit 24bit etc) and
desktop size?

Best Regards,

Andy Bower
Dolphin Support
http://www.object-arts.com
---
Are you trying too hard?
http://www.object-arts.com/Relax.htm
---

Andy,

This looks related to the walkbacks posted in the "D5:SystemBrowser/Delete
class" thread. Can you reproduce the walkback I posted in that thread?

Steve

Andy Bower <[hidden email]> wrote in message
news:ab9hgr$flf08$[hidden email]...
> >
> >  GDILibrary(ExternalLibrary)>>systemError
> > IndexedColor>>asRGBUsingPalette:
> > IndexedColor>>asRGB
> > IndexedColor(Color)>>fadedBy:
> > [] in UndefinedObject>>{unbound}doIt
>
> What is your Windows display colour setting (8bit, 16bit 24bit etc) and
> desktop size?

I get the same problem, and in another thread

http://groups.google.com/groups?q=Dolphin+fadedBy:&hl=en&selm=3CD48D2C.4827F
BFC%40shoshana.com&rnum=1 ) Bill Dargel seems to have the same problem (I
did not see a response to his post, so you may have missed it).

I get the error in the System Browser and the Class Browser on inherited
methods.  It is semi-random, but frequent.  If I select methods with the
mouse or arrow keys quickly the error will usually come up.  It will not
happen every time I select an inherited method though.

The computer this happens on is running Windows ME 4.90.3000 on a Toshiba
Pentium III 650 Laptop with 384 MB RAM.  The display is a Savage/IX w/MV the
resolution is 1024x768 and it is running in True Color (32 bit) mode.

Another, perhaps unrelated thing, is that Dolphin on this computer does not
use the Splash screen graphic for the about box.  It uses the boring dialog.

BTW:  I really like the Dolphin enhancements in 5.0, it really looks like a
killer IDE.  I also like the system enhancement hook example class, I will
be porting my goodies over using that as an example.  Great job!

Here is my walkback:
----------------------------------------------------------------------------
------------------------
5:46:37 PM, Tuesday, May 07, 2002: Unhandled exception - a Win32Error('The
parameter is incorrect. (16r57: The parameter is incorrect.)')
GDILibrary(ExternalLibrary)>>systemError
IndexedColor>>asRGBUsingPalette:
IndexedColor>>asRGB
IndexedColor(Color)>>fadedBy:
[] in UndefinedObject>>{unbound}doIt
NMLVCUSTOMDRAW(NMCUSTOMDRAW)>>evaluateDrawBlock:
ListView>>customDrawSubItem:
ListView(IconicListAbstract)>>nmCustomDraw:
ListView(ControlView)>>nmNotify:
[] in ListView>>nmNotify:
Array(SequenceableCollection)>>at:ifAbsent:
ListView>>nmNotify:
ReferenceView(View)>>wmNotify:wParam:lParam:
ReferenceView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
ListView(ControlView)>>defaultWindowProcessing:wParam:lParam:
ListView(View)>>dispatchMessage:wParam:lParam:
----------------------------------------------------------------------------
------------------------

Chris

Andy,

The Desktop  is:
1024x768 ,32 bit true color, NVidia GEForce 2MX,
 Flat Screen Panel Monitor

On Tue, 7 May 2002 22:36:22 +0100, "Andy Bower"
<[hidden email]> wrote:

Andy,

I dragged a method from one browser to another, and it didn't compile (as
was expected).  The error icon was mangled a bit; I can email you a
screenshot if it will help.

Have a good one,

Bill

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

Christopher,

> I get the same problem, and in another thread
>
>
http://groups.google.com/groups?q=Dolphin+fadedBy:&hl=en&selm=3CD48D2C.4827F
> BFC%40shoshana.com&rnum=1 ) Bill Dargel seems to have the same problem (I
> did not see a response to his post, so you may have missed it).

No, I had seen Bill's post but, so far, we are unable to reproduce it.

> I get the error in the System Browser and the Class Browser on inherited
> methods.  It is semi-random, but frequent.  If I select methods with the
> mouse or arrow keys quickly the error will usually come up.  It will not
> happen every time I select an inherited method though.
>
> The computer this happens on is running Windows ME 4.90.3000 on a Toshiba
> Pentium III 650 Laptop with 384 MB RAM.  The display is a Savage/IX w/MV
the
> resolution is 1024x768 and it is running in True Color (32 bit) mode.
>
> Another, perhaps unrelated thing, is that Dolphin on this computer does
not
> use the Splash screen graphic for the about box.  It uses the boring
dialog.

Hmm.. that sounds odd, given your machine configuration. Can you debug
through:

DolphinSplash canDisplay

and let me know which of the tests is failing on your system. Does anyone
else experiencing these inherited method w/bs have a similar problem with
the splash screen?

Best Regards,

Andy Bower
Dolphin Support
http://www.object-arts.com
---
Are you trying too hard?
http://www.object-arts.com/Relax.htm
---

Andy Bower <[hidden email]> wrote in message
news:ab9rfu$gce6h$[hidden email]...
>
> Hmm.. that sounds odd, given your machine configuration. Can you debug
> through:
>
> DolphinSplash canDisplay
>

The OSVERSIONINFO current isWinV5 test returns false.  The isWinV5 test code
looks for #winME, but (on my machine at least) the osName value is #winMe
hence it fails.

Chris

Chris,

> > Hmm.. that sounds odd, given your machine configuration. Can you debug
> > through:
> >
> > DolphinSplash canDisplay
>
> The OSVERSIONINFO current isWinV5 test returns false.  The isWinV5 test
code
> looks for #winME, but (on my machine at least) the osName value is #winMe
> hence it fails.

Thanks. Recorded as issue #924.

Best Regards,

Andy Bower
Dolphin Support
http://www.object-arts.com
---
Are you trying too hard?
http://www.object-arts.com/Relax.htm
---

Steve

You wrote in message news:ab9hvl$gcn70$[hidden email]...
>
> This looks related to the walkbacks posted in the "D5:SystemBrowser/Delete
> class" thread. Can you reproduce the walkback I posted in that thread?
>...

That is a different issue caused (it would appear) by re-entrance into the
custom draw block I think it is probably independent of machine setup.

Regards

Blair