Error while exiting D6

I have an image with 3 "idea spaces".  When I try to exit D6 (and save
the image while exiting) I get this error:

1:25:18, mardi 20 décembre 2005: 'Invalid arg 2: Cannot coerce a
DeafObject to handle'
UserLibrary(ExternalLibrary)>>invalidCall
UserLibrary>>mapWindowPoints:hWndTo:lpPoints:cPoints:
ShellView class(View class)>>mapRectangle:from:to:
ShellView(View)>>rectangle
Grabber>>alignWithView
Grabber>>draw
[] in View Composer>>drawAdornment
IdentitySet(Set)>>do:
ViewComposer>>drawAdornment
ViewComposer>>onIdleEntered
[] in Idea Space>>onIdleEntered
OrderedCollection>>do:
IdeaSpaceShell>>onIdleEntered
ShellView(View)>>enterIdle
InputState>>uiIdle:
[] in InputState>>uiIdle
[] in InputState>>topLevelHandlesDo:
BlockCallback>>valueWithArgumentsAt:
ExternalCallback class>>callback:withArgumentsAt:
[] in ProcessorScheduler>>callback:withArgumentsAt:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:withArgumentsAt:cookie:
InputState>>topLevelHandlesDo:
InputState>>uiIdle
InputState>>aboutToIdle
InputState>>waitForInput:
InputState>>loopWhile:
InputState>>mainLoop
[] in InputState>>forkMain
ExceptionHandler(ExceptionHandlerAbstract)>>markAndTry
[] in ExceptionHandler(ExceptionHandlerAbstract)>>try:
BlockClosure>>ifCurtailed:
BlockClosure>>ensure:
ExceptionHandler(ExceptionHandlerAbstract)>>try:
BlockClosure>>on:do:
[] in BlockClosure>>newProcess

I must close the idea spaces to be allowed to exit.

Thanks,

Joseph

Joseph,

> I have an image with 3 "idea spaces".  When I try to exit D6 (and save
> the image while exiting) I get this error:

As a side note, to this day, I cannot bring myself to do that.  I save,
and then exit w/o saving - a hold over from my STV days.


> 1:25:18, mardi 20 décembre 2005: 'Invalid arg 2: Cannot coerce a
> DeafObject to handle'
> UserLibrary(ExternalLibrary)>>invalidCall
> UserLibrary>>mapWindowPoints:hWndTo:lpPoints:cPoints:
> ShellView class(View class)>>mapRectangle:from:to:
> ShellView(View)>>rectangle
> Grabber>>alignWithView
> Grabber>>draw
> [] in View Composer>>drawAdornment

> I must close the idea spaces to be allowed to exit.

I don't like to save images w/ view composers open, but have done so.
What are you editing?  Any dialogs?  What happens if you close the vcs
in the idea spaces?  If there are any dialogs being edited, is it enough
to close only those vcs?  Just a hunch.

Have a good one,

Bill


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

"Bill Schwab" <[hidden email]> wrote in message
news:nhOpf.7846$[hidden email]...
> As a side note, to this day, I cannot bring myself to do that.  I save,
> and then exit w/o saving - a hold over from my STV days.

I have similar reflex :)

I think it might be allready mentioned Scintilla housekeeping problem on
exit.

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

Rush, Bill,

> "Bill Schwab" <[hidden email]> wrote in message
> news:nhOpf.7846$[hidden email]...
> > As a side note, to this day, I cannot bring myself to do that.  I
> > save, and then exit w/o saving - a hold over from my STV days.
>
> I have similar reflex :)
>

As you know, from my "bonkers" post of 1999:

http://groups.google.com/group/comp.lang.smalltalk/browse_frm/thread/546
f0f95fce2d0f/3a25d06aaadba307?lnk=st&q=dolphin+smalltalk+bonkers&rnum=1#
3a25d06aaadba307

I personally don't agree with this way of working. Both Blair and I
always save the image and use it as a temporary repository for work in
progress. Of course, each one to his own, you should choose to work in
the way that suits you best. What I would like to say, however, is that
there should be no problems using Dolphin with a work routine that
involves regularly saving images. If people do find problems then we
would like to know about them so that they can be addressed.

> > I don't like to save images w/ view composers open, but have done
> > so.  What are you editing?  Any dialogs?  What happens if you close
> > the vcs in the idea spaces?  If there are any dialogs being edited,
> > is it enough to close only those vcs?  Just a hunch.
>
> I think it might be allready mentioned Scintilla housekeeping problem
> on exit.

I don't think this is the Scintilla exit problem. For a start, that is
a very rare occurrence and also this particular stacktrace indicates an
issue with the View Composer.

Best regards,

--
Andy Bower
Dolphin Support
www.object-arts.com

Joseph,

This looks like it might be a problem with a zombie View Composer (i.e.
one that has not been opened successfully and remains hidden).
Alternatively, I think it may be an indication that the view being
edited by the view composer has been prematurely closed.

If you try closing the Idea Space cards that have view composers in
them, does the problem go away? If you do a "panic" and then recreate
the Idea Spaces as before, does the problem still exist. Basically, in
order to track this down, if it is a genuine problem, we are going to
need a reproducible case to work from.

Best Regards,

--
Andy Bower
Dolphin Support
www.object-arts.com

"Andy Bower" <[hidden email]> wrote in message
news:[hidden email]...
> Rush, Bill,
> As you know, from my "bonkers" post of 1999:
>
> http://groups.google.com/group/comp.lang.smalltalk/browse_frm/thread/546
> f0f95fce2d0f/3a25d06aaadba307?lnk=st&q=dolphin+smalltalk+bonkers&rnum=1#
> 3a25d06aaadba307
>
> I personally don't agree with this way of working. Both Blair and I

Oh, I think there is missunderstanding, we nowdays save the image,  we just
do it in separate step from exiting. I think in reality there would be no
hard reason to support such behaviour, more form of supperstiton.

But I must say I could use any advice /patterns on using STS. It looks very
nice and tempting, but I still do not have confiodence that I understand and
know consequences of various choices one makes when using it.

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

I am at work now, and I don't have D6 installed on my computer: I might
not use the right names for the "things" (sorry).

The problem might be with a View Composer.

Each Idea space contains a pakage browser, a class browser, a view
composer, a workspace.

In one Idea space I have a small project "imported" from D5.  I use this
as an example.

In another Idea space, I wrote a very small program (named "ax+b") with
one view.  In this view I have 7 "labels", 6 number presenters and 2
push buttons.

It was not my intention to keep those idea spaces in my image, but when
I deployed my small program to exe, Dolphin saved my image... So I
continue to work like that (finding that it's not a bad idea to keep all
my environment ready).

The only strange thing I noticed is that each time I load my image, in
the view composer, the number presenters of "ax+b" are hidden (all of
them) until I click on the name of one of them in the objects names list
(I don't remember how this list is called, it's in the upper right
corner of the view composer, above the properties list).

I can give more details later when I go back home :-)

Thanks,

Joseph

Andy Bower wrote:
Andy, I never said there was.  Hopefully our friendship can take a
well-meant "lighten up".  You _completely_ missed my point.  Rush
appears to have picked up precisely the same pattern from precisely the
same non-Dolphin source.  However, since I work that way, I cannot
honestly tell someone that save/exit w/ VCs open is a robust way to work.

I hate to think how old my current image is.  The last thing I am going
to tell anyone is that Dolphin can't reliably save an image.  My image
is stable living proof that it can, at least when properly protected
from risky behavior.  The archives contain what I mean by that, and how
I set an image up for testing, debug, and exist w/o saving to avoid
damaging the image.  Works great.



As I said in my post.  The VC block line in the stack trace is a big clue.

Have a good one,

Bill

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

"Bill Schwab" <[hidden email]> wrote in message
news:nhOpf.7846$[hidden email]...
...
> As a side note, to this day, I cannot bring myself to do that.  I save,
> and then exit w/o saving - a hold over from my STV days.
...

I can empathize with that based on my experiences with VSE (the follow up to
STV).  However in VSE I think I probably lost more code in PARTS due to bugs
that would make my code inaccessible than anything else.  We ended up
switching to Window Builder from PARTS just in time for the PP-D suicide.
Ugh!

In Dolphin I do actually do a "snapshot and exit".  However I have my image
configured to make a backup when ever I load it.  Between my image backups
and Ian's wonderful Chunk Browser I do not worry about corrupt images
anymore as I know I can easily recover.  Dolphin images have been pretty
sturdy.  I have only experienced a handful of damaged images over the years
I have been using it on an almost daily basis.

Chris

Chris,

Just in case there is any misunderstanding still lurking about, I am NOT
saying there is a problem with save/exit.  I AM saying that I do not use
it, and hence cannot sing its praises; simple as that.  When I saw
(likely) VC related walkbacks during a save/exit, it made sense to pass
along a couple of observations and their context.

My image speaks to Dolphin's stability and of its ability save images.

Have a good one,

Bill

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

Bill Schwab a écrit :

> I don't like to save images w/ view composers open, but have done so.
> What are you editing?  Any dialogs?  What happens if you close the vcs

I saved my image with a Views composer opened and editing a view with
StaticText's and TextEdit's .

I created a new freh image, installed the last live update, loaded my
package, opened a view composer, edited my Default view, exited with
saving.  And now when I load the image, the view composer don't show the
TextEdit's, they are gone!  If I close the view composer and open
another one, I see the view with everything in it!

I couldn't recreate the error!

Perhaps I need to use one, two, three idea spaces ?
I don't have the force to do such combinatorial tests.

I will remember that it's a bad idea to save an image with something
opened (being about to think that it's a bad idea to save an image  :'( )

Thanks,

Joseph

Joseph,

That's not quite the message I had hoped to give you.  Search for my
posts containing words like save, dangerous, without.  I get the image
ready to do something that will fail and save it w/o actually suffering
the error, then evaluate the risky code, learn what I can in the
debugger, and exit w/o saving.  I do this with external interfacing,
changes to the opening of a presenter (errors during commands do not
seem to be so potent, most of the time anyway), etc.  Things that do not
touch the outside world or the GUI do not bother me; I pound away
furiously and save the image at any time.

I save images with browsers and workspaces (not to mention quick code,
and the acme filter store) open all the time.  The VC is more
complicated, and using it sometimes invokes some of my code (via custom
views) that is on my suspect list.

My image is ancient, so there is nothing wrong with saving an image.
But as I have long said, I have been hurt far more by saving something
bad than by failing to save something good - especially with the change
log as a backup.

What I had hoped you would be able to do is close just the VCs in your
idea spaces to see if that would make your problem go away.  You would
want to backup the offending image first to be able to try multiple
things to see what fixes it.

Andy's point about a zombie is well taken.

I will mention that I am tired and rushed at the moment, and am not
happy with this post.  Please feel free to ask questions to fill in the
blanks, and I will try to remember to take another crack at it later.

Have a good one,

Bill

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