wxvtk-users — wxVTK users

[wxVTK] Sander Niemeijer's patch was Re: wxAuiNotebook with wxVTK

[Mathieu M. <mat...@gm...>]

Hi Sander,

  Your patch made it into CVS HEAD. Please accept my apologies for the
long wait.

$ cvs ci -m"ENH: Merge almost all Sander Niemeijer patch from last
August in wxVTK CVS:HEAD."
Checking in src/wxVTKRenderWindowInteractor.cxx;
/cvsroot/wxvtk/wxVTK/src/wxVTKRenderWindowInteractor.cxx,v  <--
wxVTKRenderWindowInteractor.cxx
new revision: 1.35; previous revision: 1.34
done
Checking in src/wxVTKRenderWindowInteractor.h;
/cvsroot/wxvtk/wxVTK/src/wxVTKRenderWindowInteractor.h,v  <--
wxVTKRenderWindowInteractor.h
new revision: 1.19; previous revision: 1.18
done



On Wed, Apr 9, 2008 at 10:32 AM, Sander Niemeijer <nie...@st...> wrote:
>  - wxWidgets 2.6 + GTK 1.2 -> use wxGLCanvas
>  - wxWidgets 2.6 + GTK 2.0 -> don't use wxGLCanvas
>  - wxWidgets 2.8 + GTK 1.2 -> will never work
>  - wxWidgets 2.8 + GTK 2.0 -> don't use wxGLCanvas

That's at least one part of your patch I did not commited. As far as I
understand you were setting USE_WXGLCANVAS on all wxGTK 2.8.0 without
no distinction, right ?

If so does anyone knows how to detect at compilation wether we are
using gtk 1.x or gtk 2.x ? Otherwise I'll dig something

Thanks again,
-- 
Mathieu

Re: [wxVTK] [vtkusers] Anyone using wxVTK wxVTKRenderWindowInteractor wxWidgets VTK class?

[Mathieu M. <mat...@gm...>]

On Wed, Aug 22, 2007 at 3:33 PM, Sander Niemeijer <nie...@st...> wrote:
> Hi Mathieu,
>
>
>  On 22-aug-2007, at 15:15, Mathieu Malaterre wrote:
>
>  >   Can I ask just one quick question, about the OnKeyUp/OnChar thingy.
>  > Did you notice that capital letter were being passed ?
>
>  In our implementation we don't have capitalization issues (for the
>  OnChar).
>  However, mind that we are currently only testing this against
>  wxPython 2.8 and VTK 5.
>  So capitalization issues may be present with older wxWidgets/VTK
>  versions.
>
>
>  >   Patch will be merged tonight.
>
>  Be careful here. Since we haven't tested against older wxWidgets/VTK
>  versions you may break backward compatibility by including this patch.

Oh waw ! I did said I would your patch the very same night... Did you
know that night last a couple of months in France ;-P

Sorry about that...
-- 
Mathieu

[wxVTK] Problem with wxVTK and _UNICODE wxwidgets.

[<joh...@ao...>]

Dear All,

I am doing a project with wxwidgets, wxVTK and VTK under VISTA and VC9 environment.
I have several question as follows:

1. Does wxVTK support _UNICODE built wxwidgets?
2. How can I tell the compiler to use the "non-unicode" build? In my project under the VISTA and VC9 environment, it seems that the "_UNICODE" has been defined so it forces me to use unicode version of wxwidgets otherwise it won't compiled. 

Using "unicode built" ver. of wxwidgets, everything works fine without using wxVTK, but if I use wxVTK, the compiler generates error linking messages as follows. 

1>------ Build started: Project: wxTRY1, Configuration: Debug Win32 ------
1>Compiling...
1>TRYWXMyFrameTRY1.cpp
1>Compiling...
1>TRYWxFrameMain.cpp
1>Linking...
1>?? Creating library C:\TRY1\wxTRY1.lib and object C:\TRY1\Debug\wxTRY1.exp
1>TRYWXMyFrameTRY1.obj : error LNK2019: unresolved external symbol "public: __thiscall wxVTKRenderWindowInteractor::wxVTKRenderWindowInteractor(class wxWindow *,int,class wxPoint const &,class wxSize const &,long,class wxString const &)" (??0wxVTKRenderWindowInteractor@@QAE@PAVwxWindow@@HABVwxPoint@@ABVwxSize@@JABVwxString@@@Z) referenced in function "public: __thiscall TRYWXMyFrameTRY1::TRYWXMyFrameTRY1(class wxWindow *)" (??0TRYWXMyFrameTRY1@@QAE@PAVwxWindow@@@Z)
1>C:\TRY1\Debug\wxTRY1.exe : fatal error LNK1120: 1 unresolved externals
1>Build log was saved at "file://c:\TRY1\Debug\BuildLog.htm"
1>wxTRY1 - 2 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========


I have tried to build the whole wxVTK project and samples with "non-uncode" ver. of wxwidgets, everything's fine, but if I use "unicode" version, the compiler generates similar linking error like in my project.

How should I solve this problem?
PS. I am sure that there's no "_UNICODE" in my IDE's pre-processor setting.

Environment: vc9, vista 32, wxwidgets 2.8.7, wxVTK 1.2, vtk 5.1x and all compiled under vc9

Thanks very much.

John

________________________________________________________________________
AOL's new homepage has launched. Take a tour at http://info.aol.co.uk/homepage/ now.

Re: [wxVTK] wxAuiNotebook with wxVTK

[Sander N. <nie...@st...>]

Hi Mathieu,

The problem is a matter of ownership. There are situations where you  
have to give ownership over who is responsible for deleting the wxVTK  
object to some other component (depending on the design of the  
framework you are using). In the situation I had it was because I use  
a Python wrapping for wxVTK. Because of the garbage collection that  
Python uses I can't call Delete() myself but have to rely on the fact  
that Python (through a SWIG wrapping) will call delete on the wxVTK  
object.

My guess is that for the wxAuiNotebook the same reasoning holds. You  
can't call Delete() yourself, because the wxAuiNotebook has ownership  
of the destruction, so there is no single point where you can 'assist'  
in destroying the wxVTK object. In other words, you _should not_ call  
'delete' or 'Delete()' yourself!

So what does it mean if another component calls 'delete' on the wxVTK  
object?
1) It breaks the operation of all objects that still have a reference  
to the wxVTK object
2) It breaks the final decrement that a call of wxVTK::Delete() would  
do if there would be no further references (which raises a "Trying to  
delete object with non-zero reference count." error if the  
vtkObjectBase destructor gets called for the wxVTK object)

So how do we remedy this?
For the first problem we need to make sure that we have no more  
references to our object. For my purposes calling the  
SetRenderWindow(NULL) and SetInteractorStyle(NULL) from the wxVTK  
object destructor was sufficient. But depending on how you use the  
wxVTK object in your code you may have to remove additional references  
as well.
For the second problem I use the 'if (GetReferenceCount() == 1)  
SetReferenceCount(0);' trick in the destructor.


P.S. I saw that several of the items of the patch that I send in  
August last year are not in HEAD (yet). If you want to discuss them  
please drop me an email. Most importantly for me would be to drop the  
'#if (!wxCHECK_VERSION(2, 8, 0))' part. It may also be good to mention  
that wxWidgets 2.8 no longer supports GTK 1.2 (there are a lot of  
things broken). You will have to use GTK 2.x if you want to use  
wxWidgets 2.8.0. For our application we changed at some point from  
wxWidgets 2.6/GTK 1.2 to wxWidgets 2.8/GTK 2.x (we never got wxWidgets  
2.6 properly working with GTK 2.x). Your mention in  
wxVTKRenderWindowInteractor.h of the flickering was I think exactly  
that issue. But this would then mean that:
- wxWidgets 2.6 + GTK 1.2 -> use wxGLCanvas
- wxWidgets 2.6 + GTK 2.0 -> don't use wxGLCanvas
- wxWidgets 2.8 + GTK 1.2 -> will never work
- wxWidgets 2.8 + GTK 2.0 -> don't use wxGLCanvas

Best regards,
Sander

On 8 apr 2008, at 16:27, Mathieu Malaterre wrote:
> Hi there !
>
>  Long time no activity on wxVTK, glad to see it is still active :)
>
>  Kerry, I made some minor tweaks to the wxVTK class so that the
> annoying debug leaks message does not appear anymore. You can now
> build VTK with DEBUG_LEAKS=ON safely.
>
> On Mon, Apr 7, 2008 at 11:33 PM, Sander Niemeijer  
> <nie...@st...> wrote:
>> wxWidgets and VTK use different ways to delete objects. In this case
>> you want to delete it yourself the VTK way which is using '...-
>>> Delete()' and on the other hand a wx object is doing it the
>> wxWidgets way and thinks it can call 'delete ...'. This generates a
>> conflict. The delete will not decrese the VTK refcount and will  
>> result
>> in your VTK error, but you can't really prevent the call to delete
>> either (so doing your own Delete() will also give you trouble).
>>
>> I had this problem as well and got it solved differently: I was
>> already using a derived class of wxVTKRenderWindowInteractor and for
>> that class I added the following part to the destructor (at the end):
>>
>> ----
>>     SetRenderWindow(NULL);
>>     SetInteractorStyle(NULL);
>
>
> That's always safe AFAIK. I can add those two lines to the  
> destructor of wxVTK.
>
>>     // Normally one has to remove a wxVTKRenderWindowInteractor
>> object using 'window->Delete()',
>>     // but we also would like 'delete window' to work (which is
>> needed for e.g. Python wrapping)
>
>
> Yeah, that's where you got me lost. ->Delete() from VTK world always
> 'delete this', so whatever wxWindows wants should be included in the
> destructor (~wxVTK), but ->Delete is just a convention to call
> ~wxVTK() before doing some other VTK cleanups.
>
>>     // This should be safe as long the reference count is 1 (i.e. no
>> other objects have a reference to this object)
>>     // The problem is that we can't use Delete() or Unregister(NULL)
>> here, because that would recursively invoke the
>>     // destructor. Therefore, we just explicitly decrease the
>> reference count by 1 if it was 1 (this way you will still
>>     // get a warning from VTK if the reference count afterwards was
>> not 0).
>>     if (GetReferenceCount() == 1)
>>     {
>>         SetReferenceCount(0);
>>     }
>> ---
>>
>> This is the safest solution to this issue that I know of.
>> Note that it also doesn't break a delete using the VTK-style Delete()
>> mechanism (since it won't do anything special if the reference count
>> is already 0, and the VTK Delete function will never call the
>> destructor if the refcount was still higher than that).
>>
>> For your situation, you could probably adapt the
>> wxVTKRenderWindowInteractor.cpp itself (instead of creating a
>> subclass) and add the given routines to the (currently empty)
>> wxVTKRenderWindowInteractor destructor.
>>
>> If this does indeed work, I think it might even be worth considering
>> to add this reference count trick to the wxVTKRenderWindowInteractor
>> destructor of the official wxVTKRenderWindowInteractor package.  
>> Mathieu?
>
>
> I fixed the debug leaks thingy so that vtkDebugLeaks properly report
> whether or not every VTK classes has been deleted. AFAIK everything
> should be  fine now (ie all vtkObject have a ref count == 0 at
> destruction time).
> I know that on Win32 there are some issues, which I thought were fixed
> in VTK 5.0, but this can be fixed as you mentionned by explicitely
> setting the Renderwindow to NULL before destruction.
>
> I'll add those two lines. And since I have some time on my hands, I'll
> review the couple of patch that were send to the mailing list, but
> from the top of my head they were already in CVS HEAD, simply not in
> wxVTK 1.2
>
> Thanks everybody for continued support and suggestions,
> -- 
> Mathieu
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Register now and save $200. Hurry, offer ends at 11:59 p.m.,
> Monday, April 7! Use priority code J8TLD2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users

[wxVTK] Fwd: [ wxvtk-Bugs-1919659 ] keyboard events not caught

[Mathieu M. <mat...@gm...>]

Hi there,

  Is anyone using wx 2.8.7 ? Could anyone confirm the bug ?

Thanks
-Mathieu


---------- Forwarded message ----------
From: SourceForge.net <no...@so...>
Date: Wed, Mar 19, 2008 at 4:30 PM
Subject: [ wxvtk-Bugs-1919659 ] keyboard events not caught
To: no...@so...


Bugs item #1919659, was opened at 2008-03-19 14:30
 Message generated for change (Tracker Item Submitted) made by Item Submitter
 You can respond by visiting:
 https://sourceforge.net/tracker/?func=detail&atid=669338&aid=1919659&group_id=114757

 Please note that this message will contain a full copy of the comment thread,
 including the initial issue submission, for this request,
 not just the latest update.
 Category: Interface
 Group: v1.0 (example)
 Status: Open
 Resolution: None
 Priority: 5
 Private: No
 Submitted By: JulleJuntunen (jullejuntunen)
 Assigned to: Mathieu Malaterre (malat)
 Summary: keyboard events not caught

 Initial Comment:
 Hi,

 Keyboard events are not caught on Gentoo Linux (2.6.22-gentoo-r5)
using wxWidgets GTK 2.8.7.
 This means VTK keyboard interactions won't work in a wxVTK window.

 This behaviour can be seen simply by adding a printout as the first
line in wxVTKRenderWindowInteractor::OnKeyDown() method and then
running any of the included test applications -> on any keypress the
OnKeyDown() is not invoked (no printout).

 Problem seems to be due to not passing keyboard focus to wxVTK
(wxGLCanvas) window.

 One simple fix that works for me is to add line
 SetFocus() into method wxVTKRenderWindowInteractor::OnEnter(), i.e.
when ever the VTK window is entered the keyboard focus is forced to
this window. Not sure if this works as a general fix, but I guess
similar thing should be done at least when clicking the window.

 My wxVTK versions are

  1.30 for wxVTKRenderWindowInteractor.cxx
  1.16 for wxVTKRenderWindowInteractor.h

 I've checked this also on windows, with exactly the same results.

 cheers
 -julle

 ----------------------------------------------------------------------

 You can respond by visiting:
 https://sourceforge.net/tracker/?func=detail&atid=669338&aid=1919659&group_id=114757



-- 
Mathieu

Re: [wxVTK] wxAuiNotebook with wxVTK

[Kerry L. <lo...@gm...>]

Hello Mathieu,

I am new to wxWidgets and have never used any version other than 2.8.7, so I
can't say how new wx->Destroy() is.  I did try to set the pointer to my
wxVTKObject to NULL, but the app still crashes on exit.  I don't think the
problem is that wxWidgets wants to delete a NULL pointer (that's supposed to
be safe?), it's that when the wxAuiNotebook::DeletePage() function is called
(this gets called when the app closes as well as when a page closes), it
tries to call member functions of the wxWindow that is on the notebook
page.  Looking through the code I get very confused - in
wxAuiNotebook::DeletePage(), it makes this assignment:

wxWindow* wnd = m_tabs.GetWindowFromIdx(page_idx);

I would have guessed that this pointer is supposed to point to the page
containing the wxVTKObject (which is now NULL), but then it calls
wnd->IsKindOf() a few lines later.  The crash occurs inside of IsKindOf()
(when it tries to call wxObject::GetClassInfo()), not at the call for
IsKindOf().  I can't explain why this is...

In any case, I still prefer Sander's solution because it works for closing
the application as well as closing just that one notebook tab.  If I were to
call wxVTK->Delete() and set the pointer to NULL, I'd have to put code in
wxVTK's parent's destructor and I'd also have to catch notebook page close
events, check to see if that page was a wxVTKObject, then do the special
handling.

Thanks for the responses!

-Kerry

On Tue, Apr 8, 2008 at 11:07 AM, Mathieu Malaterre <
mat...@gm...> wrote:

> Hi Kerry,
>
>  I never realized that wxWindows now has a ::Destroy,
>
> http://docs.wxwidgets.org/2.8.6/wx_wxwindow.html#wxwindow
>
>  My guess is that VTK->Delete() & wxWidgets::Destroy() might now have
> conflicting behavior. What I do not understand is that no one before
> experienced the issue. Is this wx->Destroy() really that new ?
>
> The thing that I still do not understand is why don't you do something
> like that:
>
> wxVTKObject->Delete();
> wxVTKObject = NULL; // tell wx not do manipulate this pointer anymore
>
>  I have not looked at this wxAUI thingy...
>
> HTH
> -Mathieu
>
> On Mon, Apr 7, 2008 at 10:56 PM, KR Loux <lo...@gm...> wrote:
> > Hello,
> >
> > I am using a wxAuiNotebook which has a page that is a
> > wxVTKRenderWindowInteractor.  Everything works fine until I either close
> the
> > page or exit the application, at which time the application will crash
> or I
> > get an error in the VTK debug window about trying to delete an object
> with a
> > non-zero reference count, depending on how I handle deleting the
> > wxVTKRenderWindowInteractor (wxVTK from here on).  For simplicity, I'll
> > focus on just the case of closing the application.  If in the main
> frame's
> > destructor, I do nothing to remove the wxVTK object, I get the error
> about
> > deleting an object with a non-zero ref. count (makes sense).  I added
> the
> > wxVTKObject->Delete(), which does reduce the reference count to zero,
> but
> > this causes a crash in wxObject (this is called from
> > wxAuiNotebook::DeletePage()):
> >
> > bool wxObject::IsKindOf(wxClassInfo *info) const
> > {
> >     wxClassInfo *thisInfo = GetClassInfo();// Crashes on this line
> >     return (thisInfo) ? thisInfo->IsKindOf(info) : false ;
> > }
> >
> > I think I am successfully deleting the wxVTK object with the ->Delete()
> > function, and then the notebook is trying to access it again in it's
> > destructor.  Is this something anyone has experienced before?  Has
> anyone
> > found a solution?
> >
> > I came up with a method that compiles and runs just fine, but I have
> doubts
> > about whether or not this is a good (safe?) approach.  I have not tested
> for
> > memory leaks, but I suspect that if this method doesn't work, that will
> be
> > why.  Below is the code for my main frame's destructor:
> >
> > MainFrame::~MainFrame()
> > {
> >     m_mgr.UnInit();
> >
> >     if (wxVTKObject)
> >     {
> >         wxVTKObject->Delete();// Delete the wxVTKRenderWindowInteractor
> the
> > proper way
> >         wxWindow *Dummy = new wxWindow();// Create a dummy wxWindow
> >
> >         // Assign the pointer for the wxVTKRenderWindowInteractor to
> point
> > to a wxWindow
> >         // object instead.  Now when the wxAuiNotebook is deleted, this
> will
> > point to
> >         // something than can be deleted?
> >          wxVTKObject = (wxVTKRenderWindowInteractor*)Dummy;
> >     }
> > }
> >
> > Is this OK?  Is there a better way?
> >
> > I'm using wxWidgets 2.8.7 and VTK 5.0 in MSW.
> >
> >
> > Thank you for your help,
> >
> > Kerry
> >
> >
> -------------------------------------------------------------------------
> >  This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> >  Register now and save $200. Hurry, offer ends at 11:59 p.m.,
> >  Monday, April 7! Use priority code J8TLD2.
> >
> >
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> > _______________________________________________
> >  Wxvtk-users mailing list
> >  Wxv...@li...
> >  https://lists.sourceforge.net/lists/listinfo/wxvtk-users
> >
> >
>
>
>
> --
> Mathieu
>

Re: [wxVTK] wxAuiNotebook with wxVTK

[Mathieu M. <mat...@gm...>]

Hi Kerry,

  I never realized that wxWindows now has a ::Destroy,

http://docs.wxwidgets.org/2.8.6/wx_wxwindow.html#wxwindow

  My guess is that VTK->Delete() & wxWidgets::Destroy() might now have
conflicting behavior. What I do not understand is that no one before
experienced the issue. Is this wx->Destroy() really that new ?

The thing that I still do not understand is why don't you do something
like that:

wxVTKObject->Delete();
wxVTKObject = NULL; // tell wx not do manipulate this pointer anymore

  I have not looked at this wxAUI thingy...

HTH
-Mathieu

On Mon, Apr 7, 2008 at 10:56 PM, KR Loux <lo...@gm...> wrote:
> Hello,
>
> I am using a wxAuiNotebook which has a page that is a
> wxVTKRenderWindowInteractor.  Everything works fine until I either close the
> page or exit the application, at which time the application will crash or I
> get an error in the VTK debug window about trying to delete an object with a
> non-zero reference count, depending on how I handle deleting the
> wxVTKRenderWindowInteractor (wxVTK from here on).  For simplicity, I'll
> focus on just the case of closing the application.  If in the main frame's
> destructor, I do nothing to remove the wxVTK object, I get the error about
> deleting an object with a non-zero ref. count (makes sense).  I added the
> wxVTKObject->Delete(), which does reduce the reference count to zero, but
> this causes a crash in wxObject (this is called from
> wxAuiNotebook::DeletePage()):
>
> bool wxObject::IsKindOf(wxClassInfo *info) const
> {
>     wxClassInfo *thisInfo = GetClassInfo();// Crashes on this line
>     return (thisInfo) ? thisInfo->IsKindOf(info) : false ;
> }
>
> I think I am successfully deleting the wxVTK object with the ->Delete()
> function, and then the notebook is trying to access it again in it's
> destructor.  Is this something anyone has experienced before?  Has anyone
> found a solution?
>
> I came up with a method that compiles and runs just fine, but I have doubts
> about whether or not this is a good (safe?) approach.  I have not tested for
> memory leaks, but I suspect that if this method doesn't work, that will be
> why.  Below is the code for my main frame's destructor:
>
> MainFrame::~MainFrame()
> {
>     m_mgr.UnInit();
>
>     if (wxVTKObject)
>     {
>         wxVTKObject->Delete();// Delete the wxVTKRenderWindowInteractor the
> proper way
>         wxWindow *Dummy = new wxWindow();// Create a dummy wxWindow
>
>         // Assign the pointer for the wxVTKRenderWindowInteractor to point
> to a wxWindow
>         // object instead.  Now when the wxAuiNotebook is deleted, this will
> point to
>         // something than can be deleted?
>          wxVTKObject = (wxVTKRenderWindowInteractor*)Dummy;
>     }
> }
>
> Is this OK?  Is there a better way?
>
> I'm using wxWidgets 2.8.7 and VTK 5.0 in MSW.
>
>
> Thank you for your help,
>
> Kerry
>
> -------------------------------------------------------------------------
>  This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>  Register now and save $200. Hurry, offer ends at 11:59 p.m.,
>  Monday, April 7! Use priority code J8TLD2.
>
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
>  Wxvtk-users mailing list
>  Wxv...@li...
>  https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>
>



-- 
Mathieu

Re: [wxVTK] wxAuiNotebook with wxVTK

[Mathieu M. <mat...@gm...>]

Hi there !

  Long time no activity on wxVTK, glad to see it is still active :)

  Kerry, I made some minor tweaks to the wxVTK class so that the
annoying debug leaks message does not appear anymore. You can now
build VTK with DEBUG_LEAKS=ON safely.

On Mon, Apr 7, 2008 at 11:33 PM, Sander Niemeijer <nie...@st...> wrote:
>  wxWidgets and VTK use different ways to delete objects. In this case
>  you want to delete it yourself the VTK way which is using '...-
>   >Delete()' and on the other hand a wx object is doing it the
>  wxWidgets way and thinks it can call 'delete ...'. This generates a
>  conflict. The delete will not decrese the VTK refcount and will result
>  in your VTK error, but you can't really prevent the call to delete
>  either (so doing your own Delete() will also give you trouble).
>
>  I had this problem as well and got it solved differently: I was
>  already using a derived class of wxVTKRenderWindowInteractor and for
>  that class I added the following part to the destructor (at the end):
>
>  ----
>      SetRenderWindow(NULL);
>      SetInteractorStyle(NULL);


That's always safe AFAIK. I can add those two lines to the destructor of wxVTK.

>      // Normally one has to remove a wxVTKRenderWindowInteractor
>  object using 'window->Delete()',
>      // but we also would like 'delete window' to work (which is
>  needed for e.g. Python wrapping)


Yeah, that's where you got me lost. ->Delete() from VTK world always
'delete this', so whatever wxWindows wants should be included in the
destructor (~wxVTK), but ->Delete is just a convention to call
~wxVTK() before doing some other VTK cleanups.

>      // This should be safe as long the reference count is 1 (i.e. no
>  other objects have a reference to this object)
>      // The problem is that we can't use Delete() or Unregister(NULL)
>  here, because that would recursively invoke the
>      // destructor. Therefore, we just explicitly decrease the
>  reference count by 1 if it was 1 (this way you will still
>      // get a warning from VTK if the reference count afterwards was
>  not 0).
>      if (GetReferenceCount() == 1)
>      {
>          SetReferenceCount(0);
>      }
>  ---
>
>  This is the safest solution to this issue that I know of.
>  Note that it also doesn't break a delete using the VTK-style Delete()
>  mechanism (since it won't do anything special if the reference count
>  is already 0, and the VTK Delete function will never call the
>  destructor if the refcount was still higher than that).
>
>  For your situation, you could probably adapt the
>  wxVTKRenderWindowInteractor.cpp itself (instead of creating a
>  subclass) and add the given routines to the (currently empty)
>  wxVTKRenderWindowInteractor destructor.
>
>  If this does indeed work, I think it might even be worth considering
>  to add this reference count trick to the wxVTKRenderWindowInteractor
>  destructor of the official wxVTKRenderWindowInteractor package. Mathieu?


I fixed the debug leaks thingy so that vtkDebugLeaks properly report
whether or not every VTK classes has been deleted. AFAIK everything
should be  fine now (ie all vtkObject have a ref count == 0 at
destruction time).
I know that on Win32 there are some issues, which I thought were fixed
in VTK 5.0, but this can be fixed as you mentionned by explicitely
setting the Renderwindow to NULL before destruction.

I'll add those two lines. And since I have some time on my hands, I'll
review the couple of patch that were send to the mailing list, but
from the top of my head they were already in CVS HEAD, simply not in
wxVTK 1.2

Thanks everybody for continued support and suggestions,
-- 
Mathieu

Re: [wxVTK] wxAuiNotebook with wxVTK

[Sander N. <nie...@st...>]

Dear Kerry,

wxWidgets and VTK use different ways to delete objects. In this case  
you want to delete it yourself the VTK way which is using '...- 
 >Delete()' and on the other hand a wx object is doing it the  
wxWidgets way and thinks it can call 'delete ...'. This generates a  
conflict. The delete will not decrese the VTK refcount and will result  
in your VTK error, but you can't really prevent the call to delete  
either (so doing your own Delete() will also give you trouble).

I had this problem as well and got it solved differently: I was  
already using a derived class of wxVTKRenderWindowInteractor and for  
that class I added the following part to the destructor (at the end):

----
     SetRenderWindow(NULL);
     SetInteractorStyle(NULL);

     // Normally one has to remove a wxVTKRenderWindowInteractor  
object using 'window->Delete()',
     // but we also would like 'delete window' to work (which is  
needed for e.g. Python wrapping)
     // This should be safe as long the reference count is 1 (i.e. no  
other objects have a reference to this object)
     // The problem is that we can't use Delete() or Unregister(NULL)  
here, because that would recursively invoke the
     // destructor. Therefore, we just explicitly decrease the  
reference count by 1 if it was 1 (this way you will still
     // get a warning from VTK if the reference count afterwards was  
not 0).
     if (GetReferenceCount() == 1)
     {
         SetReferenceCount(0);
     }
---

This is the safest solution to this issue that I know of.
Note that it also doesn't break a delete using the VTK-style Delete()  
mechanism (since it won't do anything special if the reference count  
is already 0, and the VTK Delete function will never call the  
destructor if the refcount was still higher than that).

For your situation, you could probably adapt the  
wxVTKRenderWindowInteractor.cpp itself (instead of creating a  
subclass) and add the given routines to the (currently empty)  
wxVTKRenderWindowInteractor destructor.

If this does indeed work, I think it might even be worth considering  
to add this reference count trick to the wxVTKRenderWindowInteractor  
destructor of the official wxVTKRenderWindowInteractor package. Mathieu?

Best regards,
Sander Niemeijer

On 7 apr 2008, at 22:56, KR Loux wrote:

> Hello,
>
> I am using a wxAuiNotebook which has a page that is a  
> wxVTKRenderWindowInteractor.  Everything works fine until I either  
> close the page or exit the application, at which time the  
> application will crash or I get an error in the VTK debug window  
> about trying to delete an object with a non-zero reference count,  
> depending on how I handle deleting the wxVTKRenderWindowInteractor  
> (wxVTK from here on).  For simplicity, I'll focus on just the case  
> of closing the application.  If in the main frame's destructor, I do  
> nothing to remove the wxVTK object, I get the error about deleting  
> an object with a non-zero ref. count (makes sense).  I added the  
> wxVTKObject->Delete(), which does reduce the reference count to  
> zero, but this causes a crash in wxObject (this is called from  
> wxAuiNotebook::DeletePage()):
>
> bool wxObject::IsKindOf(wxClassInfo *info) const
> {
>     wxClassInfo *thisInfo = GetClassInfo();// Crashes on this line
>     return (thisInfo) ? thisInfo->IsKindOf(info) : false ;
> }
>
> I think I am successfully deleting the wxVTK object with the - 
> >Delete() function, and then the notebook is trying to access it  
> again in it's destructor.  Is this something anyone has experienced  
> before?  Has anyone found a solution?
>
> I came up with a method that compiles and runs just fine, but I have  
> doubts about whether or not this is a good (safe?) approach.  I have  
> not tested for memory leaks, but I suspect that if this method  
> doesn't work, that will be why.  Below is the code for my main  
> frame's destructor:
>
> MainFrame::~MainFrame()
> {
>     m_mgr.UnInit();
>
>     if (wxVTKObject)
>     {
>         wxVTKObject->Delete();// Delete the  
> wxVTKRenderWindowInteractor the proper way
>         wxWindow *Dummy = new wxWindow();// Create a dummy wxWindow
>
>         // Assign the pointer for the wxVTKRenderWindowInteractor to  
> point to a wxWindow
>         // object instead.  Now when the wxAuiNotebook is deleted,  
> this will point to
>         // something than can be deleted?
>         wxVTKObject = (wxVTKRenderWindowInteractor*)Dummy;
>     }
> }
>
> Is this OK?  Is there a better way?
>
> I'm using wxWidgets 2.8.7 and VTK 5.0 in MSW.
>
>
> Thank you for your help,
>
> Kerry
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Register now and save $200. Hurry, offer ends at 11:59 p.m.,
> Monday, April 7! Use priority code J8TLD2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users

[wxVTK] wxAuiNotebook with wxVTK

[KR L. <lo...@gm...>]

Hello,

I am using a wxAuiNotebook which has a page that is a
wxVTKRenderWindowInteractor.  Everything works fine until I either close the
page or exit the application, at which time the application will crash or I
get an error in the VTK debug window about trying to delete an object with a
non-zero reference count, depending on how I handle deleting the
wxVTKRenderWindowInteractor (wxVTK from here on).  For simplicity, I'll
focus on just the case of closing the application.  If in the main frame's
destructor, I do nothing to remove the wxVTK object, I get the error about
deleting an object with a non-zero ref. count (makes sense).  I added the
wxVTKObject->Delete(), which does reduce the reference count to zero, but
this causes a crash in wxObject (this is called from
wxAuiNotebook::DeletePage()):

bool wxObject::IsKindOf(wxClassInfo *info) const
{
    wxClassInfo *thisInfo = GetClassInfo();// Crashes on this line
    return (thisInfo) ? thisInfo->IsKindOf(info) : false ;
}

I think I am successfully deleting the wxVTK object with the ->Delete()
function, and then the notebook is trying to access it again in it's
destructor.  Is this something anyone has experienced before?  Has anyone
found a solution?

I came up with a method that compiles and runs just fine, but I have doubts
about whether or not this is a good (safe?) approach.  I have not tested for
memory leaks, but I suspect that if this method doesn't work, that will be
why.  Below is the code for my main frame's destructor:

MainFrame::~MainFrame()
{
    m_mgr.UnInit();

    if (wxVTKObject)
    {
        wxVTKObject->Delete();// Delete the wxVTKRenderWindowInteractor the
proper way
        wxWindow *Dummy = new wxWindow();// Create a dummy wxWindow

        // Assign the pointer for the wxVTKRenderWindowInteractor to point
to a wxWindow
        // object instead.  Now when the wxAuiNotebook is deleted, this will
point to
        // something than can be deleted?
        wxVTKObject = (wxVTKRenderWindowInteractor*)Dummy;
    }
}

Is this OK?  Is there a better way?

I'm using wxWidgets 2.8.7 and VTK 5.0 in MSW.


Thank you for your help,

Kerry

[wxVTK] wxPaintDC/wxClientDC bug?

[Shang M. <smu...@gm...>]

Mathieu,

Mathieu wrote( http://groups.google.com/group/comp.soft-sys.wxwindows/browse_thread/thread/dfc1b064ac30f4f5
):
> But if I now switch to wxWindow I can see a couple of minor issues:
> - When the first OnPaint occur the image is not displayed correctly.
> - When I move another window on top of my wxVTK window and then remove
> it. The display is scrambled (not redrawn correctly).
>


from wxWidgets reference about wxPaintDC:
'''
To draw on a window from outside OnPaint, construct a wxClientDC object.
'''

I don't know if that was the cause for those problems. Apparently
Render() is not only called from within OnPaint() but also in
OnMotion() etc. And I did not see any wxClientDC object in the source
code.

Hope it helps.


Shang

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Sander N. <nie...@st...>]

I had some offline discussion with Marco on the topic.
This provided some insights that I would like to share with the list:

The problem that Marco was seeing is something that we at our company  
have been able to reproduce with our own wxVTK based application. The  
crash after closing a window seems to happen with Ubuntu 7 (and Debian  
Unstable (sid)), but not with earlier Ubuntu/Debian releases.

The Ubuntu 7 machine of Marco has a "Intel Corporation Mobile 945GM/ 
GMS, 943/940GML Express Integrated Graphics Controller" driver while  
our Ubuntu 7 machine uses a Matrox MGA G550 AGP card, so it is  
therefore most likely not a graphics driver issue.

The interesting thing is that I found that installing the wxVTK  
application on our Ubuntu 7 machine, but running the application  
remote (using ssh + X11) from an Ubuntu 6 client machine did not  
trigger the crash. The other way around (install on Ubuntu 6 and run  
remote from Ubuntu 7 client) also does not result in a crash. However,  
trying to connect via ssh + X11 from the Ubuntu 7 machine to itself  
still shows the crash.

Since Ubuntu 7 is using GTK 2.12, I was wondering whether it could be  
this specific GTK version that is causing troubles. Is there anyone on  
the list that has a non-debian based distribution with this specific  
GTK version (such as Fedora 8) that can test whether the crash appears  
on such a system as well?

Best regards,
Sander

On 2 jan 2008, at 18:00, Marco wrote:

> Mathieu Malaterre ha scritto:
>> You have pages after pages of issues with your Intel OpenGL-DRI  and
>> X11. You need to find someone that is either able to help you:
>>
>> 1. Reinstall your hardware accelerated graphic driver, or whatever
>> needs to be done to fix your xorg.conf
>> 2. find a way to use software accelerated OpenGL (if ubuntu is like
>> debian, this is simply a matter of installing mesa and remove your
>> intel specific package). On ATI this is simply a matter of setting  
>> the
>> proper env variable...
>>
>> I don't like all those issues reported against invalid read in wxGTK
>> either. The code is bad, but there is way too much stuff reported by
>> valgrind, send that to the wx-users list.
>>
>> That's all I can do...
>
> Thank you anyway:)
> Marco
>
> P.S.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Marco <tsu...@si...>]

Mathieu Malaterre ha scritto:
> You have pages after pages of issues with your Intel OpenGL-DRI  and
> X11. You need to find someone that is either able to help you:
> 
> 1. Reinstall your hardware accelerated graphic driver, or whatever
> needs to be done to fix your xorg.conf
> 2. find a way to use software accelerated OpenGL (if ubuntu is like
> debian, this is simply a matter of installing mesa and remove your
> intel specific package). On ATI this is simply a matter of setting the
> proper env variable...
> 
> I don't like all those issues reported against invalid read in wxGTK
> either. The code is bad, but there is way too much stuff reported by
> valgrind, send that to the wx-users list.
> 
> That's all I can do...

Thank you anyway:)
Marco

P.S.

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Mathieu M. <mat...@gm...>]

On Jan 2, 2008 4:59 PM, Marco <tsu...@si...> wrote:
> Mathieu Malaterre ha scritto:
> > On Jan 2, 2008 4:44 PM, Marco <tsu...@si...> wrote:
>
> [snip]
>
> >> this is my status:
> >>
> >> with wxGTK 2.6 the visualization is ok but the application crashes when
> >> I close the window;
> >>
> >> with wxGTK 2.8 *without* your patches I have visualization problems (the
> >> ones I described in my previous emails) but the application does not
> >> crash;
> >>
> >> with wxGTK 2.8 *with* your patches the visualization is ok but the
> >> application crashes as with wxGTK 2.6;
> >
> >
> > Run your app (in debug -g) through valgrind -v and send the output.
> >
> > Thanks,
>
> The app is your wxSample sample application. The output is attached.

You have pages after pages of issues with your Intel OpenGL-DRI  and
X11. You need to find someone that is either able to help you:

1. Reinstall your hardware accelerated graphic driver, or whatever
needs to be done to fix your xorg.conf
2. find a way to use software accelerated OpenGL (if ubuntu is like
debian, this is simply a matter of installing mesa and remove your
intel specific package). On ATI this is simply a matter of setting the
proper env variable...

I don't like all those issues reported against invalid read in wxGTK
either. The code is bad, but there is way too much stuff reported by
valgrind, send that to the wx-users list.

That's all I can do...
-- 
Mathieu

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Marco <tsu...@si...>]

Mathieu Malaterre ha scritto:
> On Jan 2, 2008 4:44 PM, Marco <tsu...@si...> wrote:

[snip]

>> this is my status:
>>
>> with wxGTK 2.6 the visualization is ok but the application crashes when
>> I close the window;
>>
>> with wxGTK 2.8 *without* your patches I have visualization problems (the
>> ones I described in my previous emails) but the application does not
>> crash;
>>
>> with wxGTK 2.8 *with* your patches the visualization is ok but the
>> application crashes as with wxGTK 2.6;
> 
> 
> Run your app (in debug -g) through valgrind -v and send the output.
> 
> Thanks,

The app is your wxSample sample application. The output is attached.

Thank you,
Marco

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Mathieu M. <mat...@gm...>]

On Jan 2, 2008 4:44 PM, Marco <tsu...@si...> wrote:
> Sander Niemeijer ha scritto:
> >
> > On 2 jan 2008, at 14:35, Marco wrote:
> >
> >> The patch solved this two problems with wxGTK 2.8, but now, with wxGTK
> >> 2.8 I have the same problem I have using wxGTK 2.6 (as I wrote on
> >> another thread). Closing the window the application crashes trying to
> >> delete the wxVTKRenderWindowInteractor. It seems the use of wxglcanvas
> >> makes the application not to free the resources correctly on my system.
> >>
> >> Any idea?
> >
> > In the destructor of our wxVTKRenderWindowInteractor derived classes we
> > use the following:
> > -----
> >     SetRenderWindow(NULL);
> >     SetInteractorStyle(NULL);
>
> [snip]
>
> > -----
> >
> > However, the samples already seem to use Delete() instead of 'delete',
> > so perhaps setting the renderwindow and interactorstyle to NULL before
> > destruction can solve the problem?
>
>
> It doesn't:(
>
> Do the wxVTK samples work on your system linking against the system
> libvtk5 and libwxgtk2.6 or libwxgtk2.8?
>
> this is my status:
>
> with wxGTK 2.6 the visualization is ok but the application crashes when
> I close the window;
>
> with wxGTK 2.8 *without* your patches I have visualization problems (the
> ones I described in my previous emails) but the application does not
> crash;
>
> with wxGTK 2.8 *with* your patches the visualization is ok but the
> application crashes as with wxGTK 2.6;


Run your app (in debug -g) through valgrind -v and send the output.

Thanks,
-- 
Mathieu

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Marco <tsu...@si...>]

Sander Niemeijer ha scritto:
> 
> On 2 jan 2008, at 14:35, Marco wrote:
> 
>> The patch solved this two problems with wxGTK 2.8, but now, with wxGTK
>> 2.8 I have the same problem I have using wxGTK 2.6 (as I wrote on
>> another thread). Closing the window the application crashes trying to
>> delete the wxVTKRenderWindowInteractor. It seems the use of wxglcanvas
>> makes the application not to free the resources correctly on my system.
>>
>> Any idea?
> 
> In the destructor of our wxVTKRenderWindowInteractor derived classes we 
> use the following:
> -----
>     SetRenderWindow(NULL);
>     SetInteractorStyle(NULL);

[snip]

> -----
> 
> However, the samples already seem to use Delete() instead of 'delete', 
> so perhaps setting the renderwindow and interactorstyle to NULL before 
> destruction can solve the problem?


It doesn't:(

Do the wxVTK samples work on your system linking against the system
libvtk5 and libwxgtk2.6 or libwxgtk2.8?

this is my status:

with wxGTK 2.6 the visualization is ok but the application crashes when
I close the window;

with wxGTK 2.8 *without* your patches I have visualization problems (the
ones I described in my previous emails) but the application does not
crash;

with wxGTK 2.8 *with* your patches the visualization is ok but the
application crashes as with wxGTK 2.6;


Thanks a lot,
Marco

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Sander N. <nie...@st...>]

Dear Mathieu,

I am afraid I also have too many other obligations that eat up my time  
to take on this task.
I can provide you with our updates and patches based on the way we use  
wxVTK in our own application (as I have done in the past), but can not  
provide much more at this point.

Best regards,
Sander

On 2 jan 2008, at 15:13, Mathieu Malaterre wrote:

> On Jan 2, 2008 3:09 PM, Sander Niemeijer <nie...@st...> wrote:
>>
>> On 2 jan 2008, at 14:35, Marco wrote:
>>
>>> your patch solved both the problems. Is it going to be merged with  
>>> the
>>> official wxVTK?
>>
>> It would be nice, but this is up to Mathieu. Furthermore, I haven't
>> tested my patch with older versions of wxWidgets/VTK, so I don't know
>> if it breaks anything there. It may be wise to test it first.
>
> Sander/anybody do you have a sourceforge account ? Would anyone like
> to volonteer in some basic dev work on wxVTK ? It is getting harder
> and harder to find time to work in this project for me.
>
> Thanks,
> -- 
> Mathieu
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Mathieu M. <mat...@gm...>]

On Jan 2, 2008 3:09 PM, Sander Niemeijer <nie...@st...> wrote:
>
> On 2 jan 2008, at 14:35, Marco wrote:
>
> > your patch solved both the problems. Is it going to be merged with the
> > official wxVTK?
>
> It would be nice, but this is up to Mathieu. Furthermore, I haven't
> tested my patch with older versions of wxWidgets/VTK, so I don't know
> if it breaks anything there. It may be wise to test it first.

Sander/anybody do you have a sourceforge account ? Would anyone like
to volonteer in some basic dev work on wxVTK ? It is getting harder
and harder to find time to work in this project for me.

Thanks,
-- 
Mathieu

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Sander N. <nie...@st...>]

On 2 jan 2008, at 14:35, Marco wrote:

> your patch solved both the problems. Is it going to be merged with the
> official wxVTK?

It would be nice, but this is up to Mathieu. Furthermore, I haven't  
tested my patch with older versions of wxWidgets/VTK, so I don't know  
if it breaks anything there. It may be wise to test it first.

> The patch solved this two problems with wxGTK 2.8, but now, with wxGTK
> 2.8 I have the same problem I have using wxGTK 2.6 (as I wrote on
> another thread). Closing the window the application crashes trying to
> delete the wxVTKRenderWindowInteractor. It seems the use of wxglcanvas
> makes the application not to free the resources correctly on my  
> system.
>
> Any idea?

In the destructor of our wxVTKRenderWindowInteractor derived classes  
we use the following:
-----
     SetRenderWindow(NULL);
     SetInteractorStyle(NULL);

     // Normally one has to remove a wxVTKRenderWindowInteractor  
object using 'window->Delete()',
     // but we also would like 'delete window' to work (which is  
needed for e.g. Python wrapping)
     // This should be safe as long as the reference count is 1 (i.e.  
no other objects have a reference to this object)
     // The problem is that we can't use Delete() or Unregister(NULL)  
here, because that would recursively invoke the
     // destructor. Therefore, we just explicitly decrease the  
reference count by 1 if it was 1 (this way you will still
     // get a warning from VTK if the reference count afterwards was  
not 0).
     if (GetReferenceCount() == 1)
     {
         SetReferenceCount(0);
     }
-----

However, the samples already seem to use Delete() instead of 'delete',  
so perhaps setting the renderwindow and interactorstyle to NULL before  
destruction can solve the problem?

> Is there anyone using wxVTK on Ubuntu 7.10?

We are ;)

If you want to see our app (and sources), just download the VISAN  
package from our website: http://www.stcorp.nl/beat
We have a version for Linux, Windows, and Mac OS X.

Best regards,
Sander

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Mathieu M. <mat...@gm...>]

In fact the main dev on wxVTK is a lazy bastard. Shame on you Mathieu !
You should not rely on release being stable, and instead always try
the version from CVS... sorry :(

Good luck
-Mathieu
Ps: there is AFAIK only one patch that did not make it -yet- into
wxVTK, and this has to do with a smoother handling of the mouse wheel

On Jan 2, 2008 2:35 PM, Marco <tsu...@si...> wrote:
> Great,
>
> your patch solved both the problems. Is it going to be merged with the
> official wxVTK?
>
> The patch solved this two problems with wxGTK 2.8, but now, with wxGTK
> 2.8 I have the same problem I have using wxGTK 2.6 (as I wrote on
> another thread). Closing the window the application crashes trying to
> delete the wxVTKRenderWindowInteractor. It seems the use of wxglcanvas
> makes the application not to free the resources correctly on my system.
>
> Any idea?
>
> Is there anyone using wxVTK on Ubuntu 7.10?
>
> Many Thanks,
> Marco
>
>
>
> Sander Niemeijer ha scritto:
>
> > You might want to have a look at the patch I submitted in August last year:
> > http://sourceforge.net/mailarchive/message.php?msg_name=627122B2-45B7-4CB2-A162-E942858EB422%40stcorp.nl
> >
> >
> > Especially the removal of the wxCHECK_VERSION(2, 8, 0) check for the
> > define of USE_WXGLCANVAS.
> >
> > Best regards,
> > Sander Niemeijer
> >
> > On 2 jan 2008, at 12:28, Marco wrote:
> >
> >> Marco ha scritto:
> >>> Deli Geng (David) ha scritto:
> >>>> Hi,
> >>>>
> >>>>
> >>>>
> >>>> I realized on the wxVTK web page it was claimed not to support
> >>>> wxWidgets
> >>>> 2.8 for the moment. However, I did use the
> >>>> wxVTKRenderWindowInteractor.cxx with my wxWidget 2.8 application. It
> >>>> seemed to work ok, although I haven't tested it thoroughly. So I wonder
> >>>> if it actually supports 2.8 now, or if not, is there anything I should
> >>>> be careful with?
> >>>
> >>>
> >>> Hi,
> >>>
> >>> I tried the wxVTK samples with wxWidgets 2.8.4 on Ubuntu, it works but
> >>> there is something strange...the cone does not look as it should,
> >>> something like the surface normals are not oriented the right way.
> >>>
> >>> Anyone experiencing this behaviour?
> >>
> >> Sorry,
> >>
> >> another small thing,
> >>
> >> the rendering windows do not refresh automatically, I have to click on
> >> them.
> >>
> >> Bye,
> >> Marco
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>



-- 
Mathieu

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Marco <tsu...@si...>]

Great,

your patch solved both the problems. Is it going to be merged with the
official wxVTK?

The patch solved this two problems with wxGTK 2.8, but now, with wxGTK
2.8 I have the same problem I have using wxGTK 2.6 (as I wrote on
another thread). Closing the window the application crashes trying to
delete the wxVTKRenderWindowInteractor. It seems the use of wxglcanvas
makes the application not to free the resources correctly on my system.

Any idea?

Is there anyone using wxVTK on Ubuntu 7.10?

Many Thanks,
Marco



Sander Niemeijer ha scritto:
> You might want to have a look at the patch I submitted in August last year:
> http://sourceforge.net/mailarchive/message.php?msg_name=627122B2-45B7-4CB2-A162-E942858EB422%40stcorp.nl 
> 
> 
> Especially the removal of the wxCHECK_VERSION(2, 8, 0) check for the 
> define of USE_WXGLCANVAS.
> 
> Best regards,
> Sander Niemeijer
> 
> On 2 jan 2008, at 12:28, Marco wrote:
> 
>> Marco ha scritto:
>>> Deli Geng (David) ha scritto:
>>>> Hi,
>>>>
>>>>
>>>>
>>>> I realized on the wxVTK web page it was claimed not to support 
>>>> wxWidgets
>>>> 2.8 for the moment. However, I did use the
>>>> wxVTKRenderWindowInteractor.cxx with my wxWidget 2.8 application. It
>>>> seemed to work ok, although I haven’t tested it thoroughly. So I wonder
>>>> if it actually supports 2.8 now, or if not, is there anything I should
>>>> be careful with?
>>>
>>>
>>> Hi,
>>>
>>> I tried the wxVTK samples with wxWidgets 2.8.4 on Ubuntu, it works but
>>> there is something strange...the cone does not look as it should,
>>> something like the surface normals are not oriented the right way.
>>>
>>> Anyone experiencing this behaviour?
>>
>> Sorry,
>>
>> another small thing,
>>
>> the rendering windows do not refresh automatically, I have to click on
>> them.
>>
>> Bye,
>> Marco

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Sander N. <nie...@st...>]

You might want to have a look at the patch I submitted in August last =20=

year:
=
http://sourceforge.net/mailarchive/message.php?msg_name=3D627122B2-45B7-4C=
B2-A162-E942858EB422%40stcorp.nl

Especially the removal of the wxCHECK_VERSION(2, 8, 0) check for the =20
define of USE_WXGLCANVAS.

Best regards,
Sander Niemeijer

On 2 jan 2008, at 12:28, Marco wrote:

> Marco ha scritto:
>> Deli Geng (David) ha scritto:
>>> Hi,
>>>
>>>
>>>
>>> I realized on the wxVTK web page it was claimed not to support =20
>>> wxWidgets
>>> 2.8 for the moment. However, I did use the
>>> wxVTKRenderWindowInteractor.cxx with my wxWidget 2.8 application. It
>>> seemed to work ok, although I haven=92t tested it thoroughly. So I =20=

>>> wonder
>>> if it actually supports 2.8 now, or if not, is there anything I =20
>>> should
>>> be careful with?
>>
>>
>> Hi,
>>
>> I tried the wxVTK samples with wxWidgets 2.8.4 on Ubuntu, it works =20=

>> but
>> there is something strange...the cone does not look as it should,
>> something like the surface normals are not oriented the right way.
>>
>> Anyone experiencing this behaviour?
>
> Sorry,
>
> another small thing,
>
> the rendering windows do not refresh automatically, I have to click on
> them.
>
> Bye,
> Marco
>
>
> =
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Marco <tsu...@si...>]

Marco ha scritto:
> Deli Geng (David) ha scritto:
>> Hi,
>>
>>  
>>
>> I realized on the wxVTK web page it was claimed not to support wxWidgets 
>> 2.8 for the moment. However, I did use the 
>> wxVTKRenderWindowInteractor.cxx with my wxWidget 2.8 application. It 
>> seemed to work ok, although I haven’t tested it thoroughly. So I wonder 
>> if it actually supports 2.8 now, or if not, is there anything I should 
>> be careful with?
> 
> 
> Hi,
> 
> I tried the wxVTK samples with wxWidgets 2.8.4 on Ubuntu, it works but
> there is something strange...the cone does not look as it should,
> something like the surface normals are not oriented the right way.
> 
> Anyone experiencing this behaviour?

Sorry,

another small thing,

the rendering windows do not refresh automatically, I have to click on
them.

Bye,
Marco

Re: [wxVTK] wxVTK and wxWidgets 2.8

[Marco <tsu...@si...>]

Deli Geng (David) ha scritto:
> Hi,
> 
>  
> 
> I realized on the wxVTK web page it was claimed not to support wxWidgets 
> 2.8 for the moment. However, I did use the 
> wxVTKRenderWindowInteractor.cxx with my wxWidget 2.8 application. It 
> seemed to work ok, although I haven’t tested it thoroughly. So I wonder 
> if it actually supports 2.8 now, or if not, is there anything I should 
> be careful with?


Hi,

I tried the wxVTK samples with wxWidgets 2.8.4 on Ubuntu, it works but
there is something strange...the cone does not look as it should,
something like the surface normals are not oriented the right way.

Anyone experiencing this behaviour?

Cheers,
Marco