View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000551VTK(No Category)public2004-01-28 13:112011-01-13 17:00
ReporterMathieu Malaterre 
Assigned ToMathieu Malaterre 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0000551: vtkWin32RenderWindowInteractor handling of WM_CLOSE
DescriptionI was wondering: at line 686 of revision 1.86 of file
vtkWin32RenderWindowInteractor.cxx , wouldn't it be better to have


>> else me->TerminateApp();


than the current


>> me->TerminateApp();


Because with the current line, you cannot really override the application's
termination even if you set an ClassExitMethod.
TagsNo tags attached.
Project
Type
Attached Files

 Relationships

  Notes
(0000594)
Mathieu Malaterre (developer)
2004-02-02 09:34

I do want it to terminate as a default behaviour, but I want to be able to
override this behavior in a number of situations. Typically, if I catch the
WM_CLOSE by specifying a ClassExitMethod or by observing the ExitEvent, the aim
is to avoid terminating the app. For instance I can offer a "Are you sure you
want to quit ? Yes/No" dialog, and if the answer is "No", I need the application
not the terminate. Are the vtkRenderWindow might only be a part of the whole
application and I only want WM_CLOSE to close that window and not stop the
application entirely.

In both cases, I need the "else" added. And if other people do need the current
behavior, then can still call TerminateApp() explicitely from within their
ClassExitMethod.


 Issue History
Date Modified Username Field Change
2010-11-29 17:59 Mathieu Malaterre Source_changeset_attached => VTK master 647a7994
2011-01-13 17:00 Source_changeset_attached => VTK master a2bd8391
2011-01-13 17:00 Source_changeset_attached => VTK master 020ef709
2011-06-16 13:11 Zack Galbreath Category => (No Category)


Copyright © 2000 - 2018 MantisBT Team