D4.0 bug in DocumentShell>>promptToSaveChanges:

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

D4.0 bug in DocumentShell>>promptToSaveChanges:

G. Krupa
Description of cause at end of message.

The fix is to have the MessageBox's #onYes: block read as
    [ aBooleanValue value: self fileSave ]
instead of
    [ self fileSave ]

I know my description is a little confusing, but trust me--the patched
version works as expected.

I don't suppose this is worth a free or discounted upgrade to 5 Pro (from 4
Pro)?
*puppy dog eyes*

Cheers,

Gabriel


Desc:

The document must not have a filename (i.e., it's a new document) and be
modified when the call is made.

If the user chooses yes to save the changes, #fileSaveAs is sent from
#fileSave.  If the user then cancels from the "Save As" dialog, the value
passed in will be returned (which is true in the case of
#promptToSaveChanges).  Thus, #promptToSaveChanges will return true, even
though the user cancelled the save.


Reply | Threaded
Open this post in threaded view
|

Re: D4.0 bug in DocumentShell>>promptToSaveChanges:

Blair McGlashan
"G. Krupa" <[hidden email]> wrote in message
news:ad6ld9$ape$[hidden email]...
> Description of cause at end of message.
>
> The fix is to have the MessageBox's #onYes: block read as
>     [ aBooleanValue value: self fileSave ]
> instead of
>     [ self fileSave ]
>
> I know my description is a little confusing, but trust me--the patched
> version works as expected.

Thanks Gabriel. Recorded as #957 for fixing in the next patch level.

Regards

Blair