wxvtk-users — wxVTK users

[wxVTK] Re: wxVTK and wxCode

[Mathieu M. <mma...@ny...>]

Francesco,

	Sure go ahead copy wxVTK as you wish. I believe you are only interested 
in the core componenent: the VTK bridge. I'd would still like to keep 
the project around since I was not able to finish the Mac integration: 
Carbon is almost working, Cocoa is still very alpha.

Mathieu

Francesco Montorsi wrote:
> Hi,
>      I`m going to use wxVTK in my apps and, being a wxCode admin ;), I 
> would like to propose you to move/mirror wxVTK (which is small enough to 
> be considered a 'component') to wxCode.
>  
> This would make it easier for wx users to find it (since wxCode hosts a 
> lot of wxcode-specific code) and would give it many services like wiki, 
> bakefile-build system (I know wxVTK already has cmake but bakefile is 
> the standard for wx-based apps), etc...
>  
> Let me know,
> Francesco Montorsi
>  
> 
> ------------------------------------------------------------------------
> *Yahoo! Mail* 
> <http://us.rd.yahoo.com/mail_it/taglines/*http://it.mail.yahoo.com>: 
> gratis 1GB per i messaggi, antispam, antivirus, POP3

RE: [wxVTK] cannot find -lvtkHybrid

[Nigel N. <nN...@au...>]

Hi Francesco,
vtkHybrid is optional (including GUI widgets, etc.)
You need to tell CMake to make vtkHybrid.
Nigel

-----Original Message-----
From: wxv...@li...
On Behalf Of Francesco Montorsi
Sent: Saturday, 12 November 2005 9:40 AM
To: wxv...@li...
Subject: [wxVTK] cannot find -lvtkHybrid

Hi,
     I did:
1) compiled CMake on my FC4 (64bit) with GCC 4
2) compiled VTK-4.4; almost all samples compile & run without problems
3) tried to compile wxVTK.=20

After a successfull "cmake ." I get the following:

[frm@Linux wxVTK]$ make
Linking CXX executable bin/Sample
/usr/bin/ld: cannot find -lvtkHybrid
collect2: ld returned 1 exit status
make[2]: *** [bin/Sample] Error 1
make[1]: *** [CMakeFiles/Sample.dir/all] Error 2
make: *** [all] Error 2

and in fact, I cannot find any vtkHybrid in the "bin" folder of VTK:

[snip]

So, why wxVTK tried to link against vtkHybrid ?
I've compiled wx2.7.0 (cvs) with opengl and static options=20
enabled, if that makes any difference.

Thanks,
Francesco Montorsi

[wxVTK] cannot find -lvtkHybrid

[Francesco M. <f18...@ya...>]

Hi,
     I did:
1) compiled CMake on my FC4 (64bit) with GCC 4
2) compiled VTK-4.4; almost all samples compile & run without problems
3) tried to compile wxVTK. After a successfull "cmake ." I get the following:

[frm@Linux wxVTK]$ make
Linking CXX executable bin/Sample
/usr/bin/ld: cannot find -lvtkHybrid
collect2: ld returned 1 exit status
make[2]: *** [bin/Sample] Error 1
make[1]: *** [CMakeFiles/Sample.dir/all] Error 2
make: *** [all] Error 2

and in fact, I cannot find any vtkHybrid in the "bin" folder of VTK:

[frm@Linux bin]$ ll
totale 91684
-rwxrwxr-x  1 frm frm  2593580 11 nov 20:38 CommonCxxTests
-rwxrwxr-x  1 frm frm   928142 11 nov 20:38 FilteringCxxTests
-rw-rw-r--  1 frm frm   129264  8 nov 16:05 g3states.h
-rwxrwxr-x  1 frm frm  6683567 11 nov 20:38 GraphicsCxxTests
-rwxrwxr-x  1 frm frm  6378409 11 nov 20:38 ImagingCxxTests
-rwxrwxr-x  1 frm frm  1087068 11 nov 20:38 IOCxxTests
-rw-rw-r--  1 frm frm  9021388 11 nov 20:37 libvtkCommon.a
-rw-rw-r--  1 frm frm   731194 11 nov 20:38 libvtkDICOMParser.a
-rw-rw-r--  1 frm frm   302528 11 nov 20:38 libvtkexpat.a
-rw-rw-r--  1 frm frm  3048460 11 nov 20:37 libvtkFiltering.a
-rw-rw-r--  1 frm frm   553040 11 nov 20:38 libvtkfreetype.a
-rw-rw-r--  1 frm frm   129228 11 nov 20:38 libvtkftgl.a
-rw-rw-r--  1 frm frm 12863374 11 nov 20:38 libvtkGraphics.a
-rw-rw-r--  1 frm frm 11603784 11 nov 20:37 libvtkImaging.a
-rw-rw-r--  1 frm frm 12006228 11 nov 20:38 libvtkIO.a
-rw-rw-r--  1 frm frm   264310 11 nov 20:38 libvtkjpeg.a
-rw-rw-r--  1 frm frm   285720 11 nov 20:38 libvtkpng.a
-rw-rw-r--  1 frm frm  9391872 11 nov 20:38 libvtkRendering.a
-rw-rw-r--  1 frm frm   524786 11 nov 20:38 libvtktiff.a
-rw-rw-r--  1 frm frm   111870 11 nov 20:38 libvtkzlib.a
-rwxrwxr-x  1 frm frm    12173 11 nov 20:38 mkg3states
-rwxrwxr-x  1 frm frm  3876644 11 nov 20:38 RenderingCxxTests
-rwxrwxr-x  1 frm frm    26496 11 nov 20:38 TestCxxFeatures
-rw-rw-r--  1 frm frm        0  8 nov 16:05 TestCxxFeatures_TestBinaryWriting
-rwxrwxr-x  1 frm frm  3232297 11 nov 20:38 TestInstantiator
-rwxrwxr-x  1 frm frm  3946343 11 nov 20:38 TimeRenderer
-rwxrwxr-x  1 frm frm  3919233 11 nov 20:38 TimeRenderer2


So, why wxVTK tried to link against vtkHybrid ?
I've compiled wx2.7.0 (cvs) with opengl and static options enabled, if that makes any 
difference.

Thanks,
Francesco Montorsi

[wxVTK] linker error ::GetClassName

[tobes <tob...@gm...>]

hi...

after some hours of trying im realy willing to give up..=20
here's what happend

i use wx-2.6.2 build as dll
vtk 4-4 also tried 4.2 as dll
all compiled with vstudio 7.1

my project itself is a dll (plugin), having wxvtk* as sources added.
i also inlude the export libs of wx/vtk.
so my configuration should be the 4th point (all shared)

Theres one error i couldnt resolve:
        vtkRenderWindowInteractor::GetClassName=20

looking at the vtkuser archive there seem alot of people having
the same proplem, but still  i couldnt resolve it. I havent tried to
remove "#include <windows.h>" from the vtk headers, cos=20
it think this cant be the solution.

Looking at vtkRender.dll with depenendy walker i see GetClassNameA (with =
an A).

I want to inegrate vtk to my project
www.uni-koblenz.de/~jesus/asi
to make it more powerfull. but after the last hours im unsure, cos i =
cant remember the
last time havin big compiler trouble, and vtk isnt really easy to debug. =


Strange thing.. the static version of  vtk worked fine, but i cant use =
it because=20
there will be alot of plugin dlls.

Im out of idears... so i need help!!!
regards, Tobi

Re: [wxVTK] RE: wxVTK [Panther Carbon, wx 2.6.2 ] Key event within wxSashLayoutWindow

[Mathieu M. <mma...@ny...>]

Nigel,

	Thanks for taking the time to test it.
	Unfortunately the problem I am reporting is happening even before I get 
the hand on the event. The function OnChar, OnKeyUp and OnKeyDown never 
gets call. The trouble is I don't really know where to start looking.

Advices ?
Mathieu

Nigel Nunn wrote:
> Hi Mathieu,
> 
> On Sun, 16 Oct 2005 <mat...@ki...> wrote
> 
> 
>>Unfortunately I cannot get the EVT_CHAR/ EVT_KEYDOWN 
>>to work in this case. Any suggestion on how to debug 
>>and understand what is going on ?
> 
> 
> 
> I noticed a few probs after updating to a recent CVS Vtk.  While 
> debugging I added a few lines to v1.21 of your wxVtkRWI.cxx.  
> (My wx is __WXMSW__ using VC++ 7.1):
> 
>   Module:    $RCSfile: wxVTKRenderWindowInteractor.cxx,v $
>   Language:  C++
>   Date:      $Date: 2005/10/16 21:40:31 $
>   Version:   $Revision: 1.21 $
> 
> 
> I appended the following to both OnKeyDown, OnKeyUp:
> 
> 
>   // ... 
>   // ...
>   // ...
> 
>   wxWindow* pW = GetParent(); 
>   if (pW) {
>     pW->ProcessEvent(event); 
>   }
> }
> 
> 
> Below are my versions.  May help with your issue.
> thanks,
> Nigel
> 
> 
> //---------------------------------------------------------
> void wxVtkRWI::OnKeyDown(wxKeyEvent &event)
> //---------------------------------------------------------
> {
>   if (!Enabled) {
>     return;
>   }
> 
> #if VTK_MAJOR_VERSION == 5 || (VTK_MAJOR_VERSION == 4 && VTK_MINOR_VERSION > 0)
>   // new style
>   int keycode = event.GetKeyCode();
>   char key = '\0';
>   if (keycode < 256) {
>     // TODO: Unicode in non-Unicode mode ??
>     key = (char)keycode;
>   }
> 
>   SetEventInformationFlipY(event.GetX(), event.GetY(), event.ControlDown(), 
>                            event.ShiftDown(), key, 0, NULL);
>   InvokeEvent(vtkCommand::KeyPressEvent, NULL);
>   InvokeEvent(vtkCommand::CharEvent, NULL);
> #else
>   InteractorStyle->OnKeyDown(event.ControlDown(), event.ShiftDown(), 
>                              event.GetKeyCode(), 1);
> #endif
> 
>   event.Skip();
> 
>   // NBN:
>   wxWindow* pW= GetParent();
>   if (pW) {
>     pW->ProcessEvent(event);
>   }
> }
> 
> 
> //---------------------------------------------------------
> void wxVtkRWI::OnKeyUp(wxKeyEvent &event)
> //---------------------------------------------------------
> {
>   if (!Enabled) {
>     return;
>   }
> 
> #if VTK_MAJOR_VERSION == 5 || (VTK_MAJOR_VERSION == 4 && VTK_MINOR_VERSION > 0)
>   // new style
>   int keycode = event.GetKeyCode();
>   char key = '\0';
>   if (keycode < 256) {
>     // TODO: Unicode in non-Unicode mode ??
>     key = (char)keycode;
>   }
> 
>   SetEventInformationFlipY(event.GetX(), event.GetY(), event.ControlDown(), 
>                            event.ShiftDown(), key, 0, NULL);
>   InvokeEvent(vtkCommand::KeyReleaseEvent, NULL);
> #else
>   InteractorStyle->OnKeyUp(event.ControlDown(), event.ShiftDown(), 
>                            event.GetKeyCode(), 1);
> #endif
> 
>   event.Skip();
> 
>   // NBN:
>   wxWindow* pW = GetParent();
>   if (pW) {
>     pW->ProcessEvent(event);
>   }
> }
> 
> ---
> NN.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------------------
> This message is intended for the addressee named and may contain confidential and priveleged information.  If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful.  If you receive this message in error, please delete it and notify the sender.
> 
> Keep up to date with what's happening in Australian sport.
> Visit http://www.ausport.gov.au
> -------------------------------------------------------------------------------------

[wxVTK] RE: wxVTK [Panther Carbon, wx 2.6.2 ] Key event within wxSashLayoutWindow

[Nigel N. <nN...@au...>]

Hi Mathieu,

On Sun, 16 Oct 2005 <mat...@ki...> wrote

> Unfortunately I cannot get the EVT_CHAR/ EVT_KEYDOWN=20
> to work in this case. Any suggestion on how to debug=20
> and understand what is going on ?


I noticed a few probs after updating to a recent CVS Vtk.  While=20
debugging I added a few lines to v1.21 of your wxVtkRWI.cxx. =20
(My wx is __WXMSW__ using VC++ 7.1):

  Module:    $RCSfile: wxVTKRenderWindowInteractor.cxx,v $
  Language:  C++
  Date:      $Date: 2005/10/16 21:40:31 $
  Version:   $Revision: 1.21 $


I appended the following to both OnKeyDown, OnKeyUp:


  // ...=20
  // ...
  // ...

  wxWindow* pW =3D GetParent();=20
  if (pW) {
    pW->ProcessEvent(event);=20
  }
}


Below are my versions.  May help with your issue.
thanks,
Nigel


//---------------------------------------------------------
void wxVtkRWI::OnKeyDown(wxKeyEvent &event)
//---------------------------------------------------------
{
  if (!Enabled) {
    return;
  }

#if VTK_MAJOR_VERSION =3D=3D 5 || (VTK_MAJOR_VERSION =3D=3D 4 && =
VTK_MINOR_VERSION > 0)
  // new style
  int keycode =3D event.GetKeyCode();
  char key =3D '\0';
  if (keycode < 256) {
    // TODO: Unicode in non-Unicode mode ??
    key =3D (char)keycode;
  }

  SetEventInformationFlipY(event.GetX(), event.GetY(), =
event.ControlDown(),=20
                           event.ShiftDown(), key, 0, NULL);
  InvokeEvent(vtkCommand::KeyPressEvent, NULL);
  InvokeEvent(vtkCommand::CharEvent, NULL);
#else
  InteractorStyle->OnKeyDown(event.ControlDown(), event.ShiftDown(),=20
                             event.GetKeyCode(), 1);
#endif

  event.Skip();

  // NBN:
  wxWindow* pW=3D GetParent();
  if (pW) {
    pW->ProcessEvent(event);
  }
}


//---------------------------------------------------------
void wxVtkRWI::OnKeyUp(wxKeyEvent &event)
//---------------------------------------------------------
{
  if (!Enabled) {
    return;
  }

#if VTK_MAJOR_VERSION =3D=3D 5 || (VTK_MAJOR_VERSION =3D=3D 4 && =
VTK_MINOR_VERSION > 0)
  // new style
  int keycode =3D event.GetKeyCode();
  char key =3D '\0';
  if (keycode < 256) {
    // TODO: Unicode in non-Unicode mode ??
    key =3D (char)keycode;
  }

  SetEventInformationFlipY(event.GetX(), event.GetY(), =
event.ControlDown(),=20
                           event.ShiftDown(), key, 0, NULL);
  InvokeEvent(vtkCommand::KeyReleaseEvent, NULL);
#else
  InteractorStyle->OnKeyUp(event.ControlDown(), event.ShiftDown(),=20
                           event.GetKeyCode(), 1);
#endif

  event.Skip();

  // NBN:
  wxWindow* pW =3D GetParent();
  if (pW) {
    pW->ProcessEvent(event);
  }
}

---
NN.

Re: [wxVTK] Problems with wxMac 2.6.2

[Mathieu M. <mma...@ny...>]

Hum... don't try to update wxVTK from CVS right now, it seems sf.net is 
doing some kind of bufferization for anonymous CVS...
It looks like it take around ~4h to sync CVS

Mathieu

Mathieu Malaterre wrote:
> Sample: I don't really understand what is going on. I'll try to 
> duplicate the problem (I have now access to a Mac machine)
> 
> SplitSample: This is due to the lack of support of Carbon in VTK 4.4.2, 
> I need to update wxVTK to work with VTK 5.0. Wait and see (or patch 
> welcome:)
> 
> Mathieu
> 
> Paulo Abreu wrote:
> 
>> Hi:
>>
>> My system: MacOSX 10.4, wxMac 2.6.2 (Carbon, not Cocoa), VTK 4.4.2.
>>
>> I have found several problems. I understand that Mac support is not  
>> complete, and that you don't have a Mac system, so I'll be glad to  
>> help in fixing this for the Mac.
>>
>> Here is the description of the problem:
>>
>> Sample:
>>
>> When launched, it seems fine. However, there's no task bar and no  
>> resize handle. The VTK window covers the wx window completely.
>>
>> The VTK events are captured fine.
>>
>> Although I can't see the resize handle, if I click and drag where it  
>> should be (lower right corner), resizing occurs. However, this is  
>> where everything gets really weird:
>>
>> * The cone is resized, but the pink background is not. The wx window  
>> below the vtk window is resized. This leads me to believe that the  
>> vtk window is not resized, but that it gets the new size somehow, so  
>> the the cone itself changes size.
>>
>> * So if I make the window bigger, I can see wx background and I can  
>> see the borders that were missing in the beginning. If I click on the  
>> wx window, the rotation is much faster then when I click on the vtk  
>> background.
>>
>>
>> SplitSample:
>>
>> * When launched, I only see one cone. It only receives events if I  
>> click on the right half of the image.
>>
>> * When I resize it, a similar problem occurs as in Sample: the VTK  
>> background doesn't change size, and the wx window resizes.
>>
>> * If I make it bigger, I can see that the wx window is split. If I  
>> click on the right split, the window receives events.
>>
>> * I suspect the left vtk window is below the right one, so I only see  
>> the right one move.
>>
>>
>> In general, it seems to me we have a problem in resizing and  
>> positioning a vtk window to a wx window.
>>
>> Paulo
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by:
>> Power Architecture Resource Center: Free content, downloads, discussions,
>> and more. http://solutions.newsforge.com/ibmarch.tmpl
>> _______________________________________________
>> Wxvtk-users mailing list
>> Wxv...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>>
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
> 

Re: [wxVTK] Problems with wxMac 2.6.2

[Mathieu M. <mma...@ny...>]

Paulo,

	I got Sample working again with wx 2.6.2 both on Cocoa and Carbon. 
Could you give it a shot. You'll have to download wxVTK from CVS .

	I did reproduce the problem with SplitSample and cocoa/keyboard event. 
Hopefully I'll find some time tomorrow.

HTH
Mathieu

Mathieu Malaterre wrote:
> Sample: I don't really understand what is going on. I'll try to 
> duplicate the problem (I have now access to a Mac machine)
> 
> SplitSample: This is due to the lack of support of Carbon in VTK 4.4.2, 
> I need to update wxVTK to work with VTK 5.0. Wait and see (or patch 
> welcome:)
> 
> Mathieu
> 
> Paulo Abreu wrote:
> 
>> Hi:
>>
>> My system: MacOSX 10.4, wxMac 2.6.2 (Carbon, not Cocoa), VTK 4.4.2.
>>
>> I have found several problems. I understand that Mac support is not  
>> complete, and that you don't have a Mac system, so I'll be glad to  
>> help in fixing this for the Mac.
>>
>> Here is the description of the problem:
>>
>> Sample:
>>
>> When launched, it seems fine. However, there's no task bar and no  
>> resize handle. The VTK window covers the wx window completely.
>>
>> The VTK events are captured fine.
>>
>> Although I can't see the resize handle, if I click and drag where it  
>> should be (lower right corner), resizing occurs. However, this is  
>> where everything gets really weird:
>>
>> * The cone is resized, but the pink background is not. The wx window  
>> below the vtk window is resized. This leads me to believe that the  
>> vtk window is not resized, but that it gets the new size somehow, so  
>> the the cone itself changes size.
>>
>> * So if I make the window bigger, I can see wx background and I can  
>> see the borders that were missing in the beginning. If I click on the  
>> wx window, the rotation is much faster then when I click on the vtk  
>> background.
>>
>>
>> SplitSample:
>>
>> * When launched, I only see one cone. It only receives events if I  
>> click on the right half of the image.
>>
>> * When I resize it, a similar problem occurs as in Sample: the VTK  
>> background doesn't change size, and the wx window resizes.
>>
>> * If I make it bigger, I can see that the wx window is split. If I  
>> click on the right split, the window receives events.
>>
>> * I suspect the left vtk window is below the right one, so I only see  
>> the right one move.
>>
>>
>> In general, it seems to me we have a problem in resizing and  
>> positioning a vtk window to a wx window.
>>
>> Paulo
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by:
>> Power Architecture Resource Center: Free content, downloads, discussions,
>> and more. http://solutions.newsforge.com/ibmarch.tmpl
>> _______________________________________________
>> Wxvtk-users mailing list
>> Wxv...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>>
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
> 

Re: [wxVTK] Problems with wxMac 2.6.2

[Mathieu M. <mma...@ny...>]

Sample: I don't really understand what is going on. I'll try to 
duplicate the problem (I have now access to a Mac machine)

SplitSample: This is due to the lack of support of Carbon in VTK 4.4.2, 
I need to update wxVTK to work with VTK 5.0. Wait and see (or patch 
welcome:)

Mathieu

Paulo Abreu wrote:
> Hi:
> 
> My system: MacOSX 10.4, wxMac 2.6.2 (Carbon, not Cocoa), VTK 4.4.2.
> 
> I have found several problems. I understand that Mac support is not  
> complete, and that you don't have a Mac system, so I'll be glad to  help 
> in fixing this for the Mac.
> 
> Here is the description of the problem:
> 
> Sample:
> 
> When launched, it seems fine. However, there's no task bar and no  
> resize handle. The VTK window covers the wx window completely.
> 
> The VTK events are captured fine.
> 
> Although I can't see the resize handle, if I click and drag where it  
> should be (lower right corner), resizing occurs. However, this is  where 
> everything gets really weird:
> 
> * The cone is resized, but the pink background is not. The wx window  
> below the vtk window is resized. This leads me to believe that the  vtk 
> window is not resized, but that it gets the new size somehow, so  the 
> the cone itself changes size.
> 
> * So if I make the window bigger, I can see wx background and I can  see 
> the borders that were missing in the beginning. If I click on the  wx 
> window, the rotation is much faster then when I click on the vtk  
> background.
> 
> 
> SplitSample:
> 
> * When launched, I only see one cone. It only receives events if I  
> click on the right half of the image.
> 
> * When I resize it, a similar problem occurs as in Sample: the VTK  
> background doesn't change size, and the wx window resizes.
> 
> * If I make it bigger, I can see that the wx window is split. If I  
> click on the right split, the window receives events.
> 
> * I suspect the left vtk window is below the right one, so I only see  
> the right one move.
> 
> 
> In general, it seems to me we have a problem in resizing and  
> positioning a vtk window to a wx window.
> 
> Paulo
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
> 

[wxVTK] Problems with wxMac 2.6.2

[Paulo A. <pau...@is...>]

Hi:

My system: MacOSX 10.4, wxMac 2.6.2 (Carbon, not Cocoa), VTK 4.4.2.

I have found several problems. I understand that Mac support is not  
complete, and that you don't have a Mac system, so I'll be glad to  
help in fixing this for the Mac.

Here is the description of the problem:

Sample:

When launched, it seems fine. However, there's no task bar and no  
resize handle. The VTK window covers the wx window completely.

The VTK events are captured fine.

Although I can't see the resize handle, if I click and drag where it  
should be (lower right corner), resizing occurs. However, this is  
where everything gets really weird:

* The cone is resized, but the pink background is not. The wx window  
below the vtk window is resized. This leads me to believe that the  
vtk window is not resized, but that it gets the new size somehow, so  
the the cone itself changes size.

* So if I make the window bigger, I can see wx background and I can  
see the borders that were missing in the beginning. If I click on the  
wx window, the rotation is much faster then when I click on the vtk  
background.


SplitSample:

* When launched, I only see one cone. It only receives events if I  
click on the right half of the image.

* When I resize it, a similar problem occurs as in Sample: the VTK  
background doesn't change size, and the wx window resizes.

* If I make it bigger, I can see that the wx window is split. If I  
click on the right split, the window receives events.

* I suspect the left vtk window is below the right one, so I only see  
the right one move.


In general, it seems to me we have a problem in resizing and  
positioning a vtk window to a wx window.

Paulo

[wxVTK] [Fwd: Re: [vtkusers] wxVTK for Windows]

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

If you download wxVTK from the website, it comes with a README. Do you 
read Q2 ?


Q2. Linkage has to be consistent. The class has been succesfully built 
with these four cases:

                      VTK static     VTK dynamic
wxWindows static        1                3
wxWindows dynamic       2                4

Just open the file: wxVTKRenderWindowInteractor.h, find the line:
class VTK_RENDERING_EXPORT wxVTKRenderWindowInteractor : public 
wxWindow, public vtkRenderWindowInteractor
       ^^^^^^^^^^^^^^^^^^^^
And change it accordingly

   1. VTK_RENDERING_EXPORT is ok
   2. VTK_RENDERING_EXPORT is ok
   3. WXDLLEXPORT is ok
   4. remove WXDLLEXPORT / VTK_RENDERING_EXPORT

Mathieu

-------- Original Message --------
Subject: Re: [vtkusers] wxVTK for Windows
Date: Thu, 6 Oct 2005 14:04:57 +0200 (CEST)

> If you send an email there, please send the error log you are getting.

Sorry about that.

I've got same error with wxWindows 2.4.2.

Thx

Yoan

--------------------Configuration: Sample - Win32 Debug--------------------
Compiling...
wxVTKRenderWindowInteractor.cxx
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.h(83) : warning C4275:
non dll-interface class 'wxWindow' used as base for dll-interface class
'wxVTKRenderWindowInteractor'
         c:\wxWindows-2.4.2\include\wx/msw/window.h(53) : see declaration
of 'wxWindow'
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) : warning
C4273: 'public: static class wxClassInfo
wxVTKRenderWindowInteractor::sm_classwxVTKRenderWindowInteractor' :
inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) : error C2491:
'wxVTKRenderWindowInteractor::sm_classwxVTKRenderWindowInteractor' :
definition of dllimport static data member not allowed
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : warning
C4273: 'GetEventTable' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : warning
C4273: 'protected: static struct wxEventTable const
wxVTKRenderWindowInteractor::sm_eventTable' : inconsistent dll linkage.
dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : error C2491:
'wxVTKRenderWindowInteractor::sm_eventTable' : definition of dllimport
static data member not allowed
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : warning
C4273: 'private: static struct wxEventTableEntry const * const
wxVTKRenderWindowInteractor::sm_eventTableEntries' : inconsistent dll
linkage.
dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : error C2491:
'wxVTKRenderWindowInteractor::sm_eventTableEntries' : definition of
dllimport static data member not allowed
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(105) : warning
C4273: 'wxVTKRenderWindowInteractor::wxVTKRenderWindowInteractor' :
inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(108) : warning
C4355: 'this' : used in base member initializer list
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(130) : warning
C4273: 'wxVTKRenderWindowInteractor::wxVTKRenderWindowInteractor' :
inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(133) : warning
C4355: 'this' : used in base member initializer list
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(147) : warning
C4273: 'wxVTKRenderWindowInteractor::~wxVTKRenderWindowInteractor' :
inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(151) : warning
C4273: 'New' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(157) : warning
C4273: 'Initialize' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(167) : warning
C4273: 'Enable' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(178) : warning
C4273: 'Disable' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(189) : warning
C4273: 'Start' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(196) : warning
C4273: 'UpdateSize' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(211) : warning
C4273: 'CreateTimer' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(221) : warning
C4273: 'DestroyTimer' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(227) : warning
C4273: 'OnTimer' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(241) : warning
C4273: 'GetHandle' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(300) : warning
C4273: 'OnPaint' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(318) : warning
C4273: 'OnEraseBackground' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(324) : warning
C4273: 'OnSize' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(327) : error C2039:
'OnSize' : is not a member of 'wxWindow'
         c:wxWindows-2.4.2\include\wx/msw/window.h(53) : see declaration of
'wxWindow'
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(346) : warning
C4273: 'OnMotion' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(364) : warning
C4273: 'OnEnter' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(384) : warning
C4273: 'OnLeave' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(404) : warning
C4273: 'OnKeyDown' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(433) : warning
C4273: 'OnKeyUp' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(461) : warning
C4273: 'OnButtonDown' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(517) : warning
C4273: 'OnButtonUp' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(574) : warning
C4273: 'Render' : inconsistent dll linkage.  dllexport assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(611) : warning
C4273: 'SetRenderWhenDisabled' : inconsistent dll linkage.  dllexport
assumed.
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(628) : warning
C4800: 'int' : forcing value to bool 'true' or 'false' (performance
warning)
C:\wxVTK-0.8\wxVTK\src\wxVTKRenderWindowInteractor.cxx(636) : warning
C4273: 'SetStereo' : inconsistent dll linkage.  dllexport assumed.
Error executing cl.exe.

ALL_BUILD - 4 error(s), 34 warning(s)
_______________________________________________
This is the private VTK discussion list.
Please keep messages on-topic. Check the FAQ at: 
http://www.vtk.org/Wiki/VTK_FAQ
Follow this link to subscribe/unsubscribe:
http://www.vtk.org/mailman/listinfo/vtkusers

Re: [wxVTK] I need your help for fixing a bug in wxVtk

[Mathieu M. <mma...@ny...>]

Nicolas,

	What email client are you using ? The hotmail interface ? That's weird=20
it put '>' instead of '>' ... Also could you keep the mail on the ML=20
this is great for archive, and for me to read when away from home...

	Anyway as I said I don't know the answer, BUT I could really help you=20
if you could reproduce it with a small example. Could you try modifying=20
the SplitSample (from the examples) so that I can play with on my mac.=20
That would be really helpfull.

	BTW the patch from Alexis was somehow commited in CVS, I did another=20
approach but the only thing this could affect is a resize problem on=20
Win32... so nothing related to your problem.

Thanks,
Mathieu
Ps: j'ai aucune idee comment passer a 250 mo, ma solution a ete de=20
prendre un email gmail.com ...

Nicolas . wrote:

>=20
>=20
> >I remember having seen this issue but again I did not had time to
> >spent on that. Anyway here are a few thought, could you please try
> >the wxWidget 2.6 on your Mac. Built/install it, then this becomes
> >tricky: You'll have to use the new member function they have added
> >in wxWidget: GetHandle. Hopefully *their* function GetHandle should
> >work when mine does not. So all you have to do is removed from the
> >cxx the code of my GetHandle function. And instead do:
> >
> >long wxVTK...::GetHandle()
> >{
> >    return (long)wxWindow::GetHandle();
> >}
> >
> >Let me know how this work,
> >Mathieu
>=20
> Thank's for your rapid answer. I see you are french ;-) , me too (c'est=
=20
> pour ca qu' il y a surement des fautes d'orthographe dans mes messages.=
=20
> Et mon compte Cyberniko est limit=E9 a 2 mo :-( si tu sait comment le=20
> faire passer au moins a 250 mo dis le moi)
>=20
> In My application you can find:
> MyApp (the general class)
> Myframe (the main wimdow)
> PanelLeft (a simple panel with a text inside)
> PanelVtk (the vtk render window)
> PanelLeft and PanelVtk are in MyFrame with a wxSplitterWindow
>=20
> I already had tested with wxMac-2.6.0, and differents versions of VTK.
> Here is my results :
> -Case1 : The render takes all the window, so you can't see PanelLeft
> -Case2 : The window is divided into 2 parts, as it should be. But there=
=20
> is no rendering (PanelVtk is white).
> -Case3 : Buss Error (the progam don't start)
>=20
> wxMac 2.4.2 and VTK Carbon =3D> Case1
> wxMac 2.4.2 and VTK Cocoa=3D> Case3
> wxMac 2.4.2 and VTK X11=3D> Not Tested
>=20
> wxMac 2.5.2 and VTK Carbon =3D> Case2
> wxMac 2.5.2 and VTK Cocoa=3D> Case2
> wxMac 2.5.2 and VTK X11=3D> Case2
>=20
> wxMac 2.6.0 and VTK Carbon =3D> Case1
> wxMac 2.6.0 and VTK Carbon and the "return (long)wxWindow::GetHandle();=
"=20
> =3D> Case2
> wxMac 2.6.0 and VTK Cocoa=3D> Case3
> wxMac 2.6.0 and VTK Cocoa and the "return (long)wxWindow::GetHandle();"=
=20
> =3D> Case3
> wxMac 2.6.0 and VTK X11=3D> NotTested
>=20
>=20
> So, my program still doesn't work. I tried the patch by Alexis H.=20
> Rivera-Rios, I didn't get my program working fine...
>=20
> Any ideas ?
>=20
> _________________________________________________________________
> MSN Messenger : personnalisez votre messagerie instantan=E9e !=20
> http://g.msn.fr/FR1001/866
>=20
>=20

Re: [wxVTK] I need your help for fixing a bug in wxVtk

[Mathieu M. <mma...@ny...>]

Hi Nicolas,

[/cyberniko/ j'en reviens pas, depuis combien de temps t'as cette 
adresse, elle doit s'arracher au marche noir :)]

I remember having seen this issue but again I did not had time to spent 
on that. Anyway here are a few thought, could you please try the 
wxWidget 2.6 on your Mac. Built/install it, then this becomes tricky: 
You'll have to use the new member function they have added in wxWidget: 
GetHandle. Hopefully *their* function GetHandle should work when mine 
does not. So all you have to do is removed from the cxx the code of my 
GetHandle function. And instead do:

long wxVTK...::GetHandle()
{
    return (long)wxWindow::GetHandle();
}

Let me know how this work,
Mathieu


Nicolas . wrote:

> hello,
> I have a little problem with your application and I hope you will help 
> me ;)
> I have to develop an application for windows and mac, with 3d 
> visualisation in VTK and a nice interface in wxWidget.
> So I need your wxVtk render window intercactor...
> 
> My window is splitted into several parts with wxSplitters.
> It works fine in windows whith wxWidget 2.4.2 ans VTK 4.5
> 
> My problem is whith Mac OSX
> The render of my VTKWindow takes all the space in the root window, so I 
> can't seen my incons, status bar...
> Your Sample works fine but the SplitSample makes the same mistake.
> 
> Perhaps the error is in the .cxx file, in GetHandle(), you do :
> 
> #ifdef __WXMAC__
> #if wxCHECK_VERSION(2, 5, 2)
>   //this function became in wx 2.5.2 : MacGetTopLevelWindowRef()
>    handle_tmp = (long)this->MacGetTopLevelWindowRef();
> #else
>    handle_tmp = (long)this->MacGetRootWindow();
> #endif //wxCHECK_VERSION(2, 5, 2)
> #endif //__WXMAC__
> 
> If you render in the root window or in the top level window, I 
> understand why it's not in my splitterWindow.
> 
> I didn't found how to do, I tried to call MacGetWindowRef but it doesn't 
> work...
> 
> I need your help, it's so important for me...
> 
> Thank's
> 
> nico.
> 
> _________________________________________________________________
> Ne cherchez plus, trouvez ! Avec le nouveau MSN Search. 
> http://search.msn.fr/
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
> 

[wxVTK] [Fwd: RE: wxVTK: Support one time VTK key down event for keeping key pressed]

[Mathieu M. <mma...@ny...>]

[Forwarding to wxVTK usersML]

Thanks Reinhold I have just patch wxVTK with a different patch. Could=20
you please double check and try compiling it on your side. I am planning=20
on releasing a 0.8.1, and I'd hate releasing something that does not=20
even compile. I need to update wx to wx 2.6 now that is out, to check=20
why the compilation failed on your side.

I did check the compilation against 2.4 and 2.5.3 only

Thanks again for your time
Mathieu

-------- Original Message --------
Subject: RE: wxVTK: Support one time VTK key down event for keeping key=20
pressed
Date: Wed, 27 Apr 2005 12:07:35 +0100
From: Reinhold F=FCreder <>
To: Mathieu Malaterre <>

Dear Mathieu,

Sorry for the annoying email traffic, but I just found out an annoying
problem in relation with the OnSize() patch from Alexis:

Somehow (I have not thoroughly investigated it) when there are several
wxVtkRwis (for example making up 1 perspective view, and 3 parallel
views) then the interaction is only working on some (often only one) of
them presumable depending on some concrete application and wxWidgets
window specific circumstances I don't really know. Thus, only after a
resize of the application (or the wxVtkRwi view container?) the
interaction works in all wxVtkRwis as it should. -- Your original code
does NOT have this problem, i.e. I have now changed back to:

------------------
void wxVTKRenderWindowInteractor::OnSize(wxSizeEvent &event)
{
/*
   //this is also necessary to update the context on MSW
#ifdef __WXMSW__
   // [Reinhold:] Was not compiling with our wxWidgets version from
August 2003:
   //wxWindow::OnSize(event); //wxNO_FULL_REPAINT_ON_RESIZE ??
#endif
   int w, h;
   GetClientSize(&w, &h);
   UpdateSize(w, h);
*/
/*
   // Patch by Alexis H. Rivera-Rios sent to me by Mathieu:
   int a, b;
   this->GetClientSize (&a, &b);
   int *size3;
   size3 =3D this->RenderWindow->GetSize ();
   if (size3[0]=3D=3D0 && size3[1]=3D=3D0)  //// <-- new code
   {
	  UpdateSize(a,b);
   }
   else
   {
	  UpdateSize(size3[0], size3[1]);
   }
*/
   int w, h;
   GetClientSize(&w, &h);
   UpdateSize(w, h);

   if (!Enabled)
     ...
------------------

Sorry for the inconvenience,
	Reinhold

[wxVTK] I need your help for fixing a bug in wxVtk

[Nicolas . <cyb...@ho...>]

hello,
I have a little problem with your application and I hope you will help me ;)
I have to develop an application for windows and mac, with 3d visualisation 
in VTK and a nice interface in wxWidget.
So I need your wxVtk render window intercactor...

My window is splitted into several parts with wxSplitters.
It works fine in windows whith wxWidget 2.4.2 ans VTK 4.5

My problem is whith Mac OSX
The render of my VTKWindow takes all the space in the root window, so I 
can't seen my incons, status bar...
Your Sample works fine but the SplitSample makes the same mistake.

Perhaps the error is in the .cxx file, in GetHandle(), you do :

#ifdef __WXMAC__
#if wxCHECK_VERSION(2, 5, 2)
   //this function became in wx 2.5.2 : MacGetTopLevelWindowRef()
    handle_tmp = (long)this->MacGetTopLevelWindowRef();
#else
    handle_tmp = (long)this->MacGetRootWindow();
#endif //wxCHECK_VERSION(2, 5, 2)
#endif //__WXMAC__

If you render in the root window or in the top level window, I understand 
why it's not in my splitterWindow.

I didn't found how to do, I tried to call MacGetWindowRef but it doesn't 
work...

I need your help, it's so important for me...

Thank's

nico.

_________________________________________________________________
Ne cherchez plus, trouvez ! Avec le nouveau MSN Search. 
http://search.msn.fr/

Re: [wxVTK] about wxVTK

[f18m_217828 <f18...@ya...>]

Hi,

>     I'll try my best to answer this, but this looks like a question more 
> appropriate to the vtkusers mailing list (remember wxVTK does not bring 
> anything).
thanks again for your help :-)

> VTK definitely support user click/interaction. 
good; I'll download paraview & give a look to it...


>> My program could give to VTK a dataset which it then would plot; 
>> another question: can I draw axes and labels with VTK ?
> Yes and yes, you can select fonts for the labels... Have a look at the 
> doxygen here:
> 
> http://www.vtk.org/doc/nightly/html/classvtkXYPlotActor.html
thanks!


>> 1) open source (gnuplot, for example, is not GPL)
> Be carefull here, VTK is BSD like !


> Again Francesco I have to warn you, VTK is really build on top of 
> OpenGL. So using VTK for simple 2D plot seems to me quite akward. Even 
> if I haven't search for package as you seems to have been doing, I would 
> have another look before staring learning VTK if you plan to only use 
> this very subset of VTK.
I forgot to put in my required-feature for a plotter the ability to plot
2D but also 3D plots; I'll give another look around but the only open
source alternative seems to be gnuplot which I don't like very much...
since I require 3D plots, OpenGL is good for me ;-)

> Did you search for project on freshmeat.net, sf.net, gnu.org. I would 
> also check with the gnumeric people what they use internally for 
> displaying charts.
I'll make another deep research but I think that plotting with VTK will
be a good occasion to learn to use it... ;-)

Thanks,
Francesco Montorsi

Re: [wxVTK] [Fwd: wxVTK: MSW compilation vs. resizing problem]

[Johnny C. N. I. <jn...@mc...>]

Hi,

I'm afraid I won't be much help here.  My patch consisted of adding the=20
following three lines in wxVTKRenderWindowInteractor::OnPaint():

#ifdef __WXMSW__
RenderWindow->SetParentId(reinterpret_cast<void*>(this->GetParent()->GetH=
WND()));
#endif //__WXMSW__

I didn't touch wxVTKRenderWindowInteractor::OnSize() at all.

John

mma...@ny... wrote:
> [Forwarding to wxVTK users]
>=20
> John could you comment on your patch ? Which wx did you used ? I have
> also laying around patch from Alexis H. Rivera-Rios which apparently
> changed the function OnSize to something like:
>=20
> void wxVTKRenderWindowInteractor::OnSize(wxSizeEvent
> &event)
> {
>=20
>   GetClientSize(&a,&b);
>   int *size3;
>   size3 =3D RenderWindow->GetSize(); =20
>   if (size3[0]=3D=3D0 && size3[1]=3D=3D0)  //// <-- new code
>   {
> 	  UpdateSize(a,b);
>   }
>   else
>   {
> 	  UpdateSize(size3[0], size3[1]);
>   }
>=20
>   if (!Enabled)=20
>     {
>     return;
>     }
>=20
> #if (VTK_MAJOR_VERSION =3D=3D 4 && VTK_MINOR_VERSION > 0)
>   InvokeEvent(vtkCommand::ConfigureEvent, NULL);
> #endif
>   //this will check for Handle
>   Render();
> }
>=20
>=20
> It seems wxNO_FULL_REPAINT_ON_RESIZE only affect windows (not my primar=
y
> plateform). I was also looking at solution like vtkFlRenderWindow and
> there seems to be some tricks to consider to properly set the size of
> the renderwindow.
>=20
> I'll have to investigate before applying another patch.
>=20
> sorry for the troubles,
> Mathieu
>=20
> -------- Original Message --------
> Subject: wxVTK: MSW compilation vs. resizing problem
> Date: Wed, 20 Apr 2005 15:19:55 +0100
> From: Reinhold F=FCreder <R.F...@ex...>
> To: <mat...@cr...>
>=20
> Dear Mathieu,
>=20
> When updating to your latest version (0.8) of wxVtk (from 0.7) I am
> experiencing a compilation problem (and still the resizing problem).
>=20
> During compilation MSVC++ 6 (Windows 2k) using wxWidgets version from
> August 2003 (in between 2.4.2 and 2.5.0) and VTK from end of February
> this year it reports the following error message
> "...\wxVTK\wxVTKRenderWindowInteractor.cpp(327) : error C2039: 'OnSize'
> : is not a member of 'wxWindow'
>         D:\CVS\wxWindows\include\wx/msw/window.h(53) : see declaration
> of 'wxWindow'"
>=20
> This is HERE:
> ----
> void wxVTKRenderWindowInteractor::OnSize(wxSizeEvent &event)
> {
>   //this is also necessary to update the context on MSW=20
> #ifdef __WXMSW__
>   wxWindow::OnSize(event); //wxNO_FULL_REPAINT_ON_RESIZE ?? <<<< HERE
> !!!
> #endif
> ...
> ----
>=20
> If I comment it out the patch provided by John Norris concerning the
> resizing problems under wxMSW does not work (consequently?).
>=20
> Do I miss something? I am still using the old CMake files as for versio=
n
> 0.7. And also in the CVS head of wxWidgets I cannot find a
> wxWindow::OnSize() method on the first view. Should the resizing event
> be reproduced/recreated in a different way to solve the resizing
> problem? Or is this not linked?


--=20
John Norris
Research Programmer
Center for Simulation of Advanced Rockets
http://www.uiuc.edu/ph/www/jnorris

[wxVTK] RE: [Fwd: wxVTK: MSW compilation vs. resizing problem]

[<R.F...@ex...>]

Dear Mathieu et al.,

Thanks for your extremely fast response!

Using the cited patch from Alexis the resizing problem is really solved
in my (specific little test) case (cf. platform and library versions
below): one render window in a wx frame with a menu and a status bar --
before the patch, resizing was hiding the status bar.

In fact, I am instantiating your class by "iren =3D new
wxVTKRenderWindowInteractor(this, MY_VTK_WINDOW);", thus,
wxNO_FULL_REPAINT_ON_RESIZE should be active.

Nevertheless, I am still wondering if the parent class call
"wxWindow::OnSize(event);" code is required/correct/illegal/...?

Thanks for your help and for providing this extremely helpful class,
	Reinhold


> -----Original Message-----
> From: mma...@ny... [mailto:mma...@ny...]=20
> Sent: Wednesday, April 20, 2005 2:44 PM
> To: wxv...@li...
> Cc: R.F...@ex...; ahr...@ya...
> Subject: [Fwd: wxVTK: MSW compilation vs. resizing problem]
>=20
>=20
> [Forwarding to wxVTK users]
>=20
> John could you comment on your patch ? Which wx did you used=20
> ? I have also laying around patch from Alexis H. Rivera-Rios=20
> which apparently changed the function OnSize to something like:
>=20
> void wxVTKRenderWindowInteractor::OnSize(wxSizeEvent
> &event)
> {
>=20
>   GetClientSize(&a,&b);
>   int *size3;
>   size3 =3D RenderWindow->GetSize(); =20
>   if (size3[0]=3D=3D0 && size3[1]=3D=3D0)  //// <-- new code
>   {
> 	  UpdateSize(a,b);
>   }
>   else
>   {
> 	  UpdateSize(size3[0], size3[1]);
>   }
>=20
>   if (!Enabled)=20
>     {
>     return;
>     }
>=20
> #if (VTK_MAJOR_VERSION =3D=3D 4 && VTK_MINOR_VERSION > 0)
>   InvokeEvent(vtkCommand::ConfigureEvent, NULL);
> #endif
>   //this will check for Handle
>   Render();
> }
>=20
>=20
> It seems wxNO_FULL_REPAINT_ON_RESIZE only affect windows (not=20
> my primary plateform). I was also looking at solution like=20
> vtkFlRenderWindow and there seems to be some tricks to=20
> consider to properly set the size of the renderwindow.
>=20
> I'll have to investigate before applying another patch.
>=20
> sorry for the troubles,
> Mathieu
>=20
> -------- Original Message --------
> Subject: wxVTK: MSW compilation vs. resizing problem
> Date: Wed, 20 Apr 2005 15:19:55 +0100
> From: Reinhold F=FCreder <R.F...@ex...>
> To: <mat...@cr...>
>=20
> Dear Mathieu,
>=20
> When updating to your latest version (0.8) of wxVtk (from=20
> 0.7) I am experiencing a compilation problem (and still the=20
> resizing problem).
>=20
> During compilation MSVC++ 6 (Windows 2k) using wxWidgets=20
> version from August 2003 (in between 2.4.2 and 2.5.0) and VTK=20
> from end of February this year it reports the following error message
> "...\wxVTK\wxVTKRenderWindowInteractor.cpp(327) : error=20
> C2039: 'OnSize'
> : is not a member of 'wxWindow'
>         D:\CVS\wxWindows\include\wx/msw/window.h(53) : see=20
> declaration of 'wxWindow'"
>=20
> This is HERE:
> ----
> void wxVTKRenderWindowInteractor::OnSize(wxSizeEvent &event)
> {
>   //this is also necessary to update the context on MSW=20
> #ifdef __WXMSW__
>   wxWindow::OnSize(event); //wxNO_FULL_REPAINT_ON_RESIZE ??=20
> <<<< HERE !!! #endif ...
> ----
>=20
> If I comment it out the patch provided by John Norris=20
> concerning the resizing problems under wxMSW does not work=20
> (consequently?).
>=20
> Do I miss something? I am still using the old CMake files as=20
> for version 0.7. And also in the CVS head of wxWidgets I cannot find a
> wxWindow::OnSize() method on the first view. Should the=20
> resizing event be reproduced/recreated in a different way to=20
> solve the resizing problem? Or is this not linked?
>=20
> Thanks for your time,
> 	Reinhold
>=20
> --------------------
> Reinhold F=FCreder
> MPhil Student
> School of Eng., CS and Maths
> University of Exeter, UK
> =20
>=20
>=20
>=20
>=20

[wxVTK] [Fwd: wxVTK: MSW compilation vs. resizing problem]

[<mma...@ny...>]

=5BForwarding to wxVTK users=5D

John could you comment on your patch =3F Which wx did you used =3F I have=

also laying around patch from Alexis H=2E Rivera-Rios which apparently
changed the function OnSize to something like=3A

void wxVTKRenderWindowInteractor=3A=3AOnSize(wxSizeEvent
=26event)
=7B

  GetClientSize(=26a=2C=26b)=3B
  int *size3=3B
  size3 =3D RenderWindow-=3EGetSize()=3B  =

  if (size3=5B0=5D=3D=3D0 =26=26 size3=5B1=5D=3D=3D0)  //// =3C-- new cod=
e
  =7B
	  UpdateSize(a=2Cb)=3B
  =7D
  else
  =7B
	  UpdateSize(size3=5B0=5D=2C size3=5B1=5D)=3B
  =7D

  if (!Enabled) =

    =7B
    return=3B
    =7D

=23if (VTK=5FMAJOR=5FVERSION =3D=3D 4 =26=26 VTK=5FMINOR=5FVERSION =3E 0)=

  InvokeEvent(vtkCommand=3A=3AConfigureEvent=2C NULL)=3B
=23endif
  //this will check for Handle
  Render()=3B
=7D


It seems wxNO=5FFULL=5FREPAINT=5FON=5FRESIZE only affect windows (not my =
primary
plateform)=2E I was also looking at solution like vtkFlRenderWindow and
there seems to be some tricks to consider to properly set the size of
the renderwindow=2E

I=27ll have to investigate before applying another patch=2E

sorry for the troubles=2C
Mathieu

-------- Original Message --------
Subject=3A wxVTK=3A MSW compilation vs=2E resizing problem
Date=3A Wed=2C 20 Apr 2005 15=3A19=3A55 +0100
From=3A Reinhold F=FCreder =3CR=2EFureder=40exeter=2Eac=2Euk=3E
To=3A =3Cmathieu=2Emalaterre=40creatis=2Einsa-lyon=2Efr=3E

Dear Mathieu=2C

When updating to your latest version (0=2E8) of wxVtk (from 0=2E7) I am
experiencing a compilation problem (and still the resizing problem)=2E

During compilation MSVC++ 6 (Windows 2k) using wxWidgets version from
August 2003 (in between 2=2E4=2E2 and 2=2E5=2E0) and VTK from end of Febr=
uary
this year it reports the following error message
=22=2E=2E=2E=5CwxVTK=5CwxVTKRenderWindowInteractor=2Ecpp(327) =3A error C=
2039=3A =27OnSize=27
=3A is not a member of =27wxWindow=27
        D=3A=5CCVS=5CwxWindows=5Cinclude=5Cwx/msw/window=2Eh(53) =3A see =
declaration
of =27wxWindow=27=22

This is HERE=3A
----
void wxVTKRenderWindowInteractor=3A=3AOnSize(wxSizeEvent =26event)
=7B
  //this is also necessary to update the context on MSW =

=23ifdef =5F=5FWXMSW=5F=5F
  wxWindow=3A=3AOnSize(event)=3B //wxNO=5FFULL=5FREPAINT=5FON=5FRESIZE =3F=
=3F =3C=3C=3C=3C HERE
!!!
=23endif
=2E=2E=2E
----

If I comment it out the patch provided by John Norris concerning the
resizing problems under wxMSW does not work (consequently=3F)=2E

Do I miss something=3F I am still using the old CMake files as for versio=
n
0=2E7=2E And also in the CVS head of wxWidgets I cannot find a
wxWindow=3A=3AOnSize() method on the first view=2E Should the resizing ev=
ent
be reproduced/recreated in a different way to solve the resizing
problem=3F Or is this not linked=3F

Thanks for your time=2C
	Reinhold

--------------------
Reinhold F=FCreder
MPhil Student
School of Eng=2E=2C CS and Maths
University of Exeter=2C UK
 =

Re: [wxVTK] about wxVTK

[Mathieu M. <mma...@ny...>]

Francesco,

	I'll try my best to answer this, but this looks like a question more 
appropriate to the vtkusers mailing list (remember wxVTK does not bring 
anything).

> well, I would like to create a plotter with two main features (which are 
> lacking from a lot of other packages out there):
> 
> 1) user-interaction: I would like to be able to intercept user clicks on 
> the plot and then perform some actions if the click was over the 
> function plot, some others if user clicked over the axes and so on... I 
> could not find a plot package with something like a HitTest function 
> which tells me which part of the plot is tied to (x,y); can VTK do this ?


> 2) animated plots: I would like to be able to render flickering-free 
> animating plots (imagine a parametric function plot where the user can 
> see the different plots for different values of the parameter in real 
> time...); I suppose VTK should have no excessive problems to do this.... 
> is it ?

VTK definitely support user click/interaction. You should maybe download 
paraview just for a try. Then start paraview open a dataset that comes 
with it, do a 'probe', select line from the left panel. You'll get an 
histogram you can export as CSV file. You can move it around with 2D 
mouse, and if you move the probe line you'll see that the histogram 
reflect the dataset being probe. (a nice example to probe could be 
vox8_bin.vtk).


> My program could give to VTK a dataset which it then would plot; another 
> question: can I draw axes and labels with VTK ?

Yes and yes, you can select fonts for the labels... Have a look at the 
doxygen here:

http://www.vtk.org/doc/nightly/html/classvtkXYPlotActor.html

> I'm asking you because I've been searching a good plot packages flexible 
> enough to give me those two features I told you before; I've found a LOT 
> of plotting packages but when you select those which are:
> 
> 1) open source (gnuplot, for example, is not GPL)

Be carefull here, VTK is BSD like !

> 2) written in c++

ok

> 3) cross-platform

VTK compiles on almost any plateform / compilers out there !!

> you'll find that the list is not so long ;-)
> I thought that with some additional work in my program (basically to do 
> the dataset creation) I could solve my problems with wxVTK...

Again Francesco I have to warn you, VTK is really build on top of 
OpenGL. So using VTK for simple 2D plot seems to me quite akward. Even 
if I haven't search for package as you seems to have been doing, I would 
have another look before staring learning VTK if you plan to only use 
this very subset of VTK.

Mathieu
Did you search for project on freshmeat.net, sf.net, gnu.org. I would 
also check with the gnumeric people what they use internally for 
displaying charts.

My 2 cents,
Mathieu

Re: [wxVTK] about wxVTK

[f18m_217828 <f18...@ya...>]

Hi,

Mathieu Malaterre wrote:

 >     More seriously you cannot compare gnuplot to VTK, but VTK does a 
pretty good job at large dataset, and tons of 3d stuff. This is an 
abstract layer above OpenGL. It has wrapping for Tcl, Python, Java and 
even octave (matlab clone). The learning curve is reasonable not too 
steep but keep in mind that there is almost 1000 classes just in VTK 
itself (not counting users contrib, example, and project like paraview).

well, I would like to create a plotter with two main features (which are 
lacking from a lot of other packages out there):

1) user-interaction: I would like to be able to intercept user clicks on 
the plot and then perform some actions if the click was over the 
function plot, some others if user clicked over the axes and so on... I 
could not find a plot package with something like a HitTest function 
which tells me which part of the plot is tied to (x,y); can VTK do this ?

2) animated plots: I would like to be able to render flickering-free 
animating plots (imagine a parametric function plot where the user can 
see the different plots for different values of the parameter in real 
time...); I suppose VTK should have no excessive problems to do this.... 
is it ?

My program could give to VTK a dataset which it then would plot; another 
question: can I draw axes and labels with VTK ?


 > As for 2. wxVTK is only a bridge between wxWidget and VTK. So you can 
use it in your wx project and it allow you access to the full power of 
VTK. But wxVTK is pretty generic there is nothing done in particular for 
math user like you.

I'm asking you because I've been searching a good plot packages flexible 
enough to give me those two features I told you before; I've found a LOT 
of plotting packages but when you select those which are:

1) open source (gnuplot, for example, is not GPL)
2) written in c++
3) cross-platform

you'll find that the list is not so long ;-)
I thought that with some additional work in my program (basically to do 
the dataset creation) I could solve my problems with wxVTK...

Thanks a lot,
Francesco


 > f18m_217828 wrote:
 >
 >> Hi,
 >>    I'm the admin of the MathStudio project 
(http://mathstudio.sourceforge.net) and I'd like to ask you a couple of 
things about your wxVTK project:
 >>
 >> 1) I'm a C++ wx-user since quite much time but I've never used VTK; 
so, before any other question, I need to know: VTK can be used to plot 
math data ?
 >>
 >> 2) If yes, wxVTK allows to use VTK in this sense ?
 >>
 >> Thanks,
 >> Francesco Montorsi
 >>
 >>
 >>
 >>
 >> -------------------------------------------------------
 >> SF email is sponsored by - The IT Product Guide
 >> Read honest & candid reviews on hundreds of IT Products from real users.
 >> Discover which products truly live up to the hype. Start reading now.
 >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
 >> _______________________________________________
 >> Wxvtk-users mailing list
 >> Wxv...@li...
 >> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
 >>
 >
 >
 >
 > -------------------------------------------------------
 > This SF.Net email is sponsored by: New Crystal Reports XI.
 > Version 11 adds new functionality designed to reduce time involved in
 > creating, integrating, and deploying reporting solutions. Free 
runtime info,
 > new features, or free trial, at: http://www.businessobjects.com/devxi/728
 > _______________________________________________
 > Wxvtk-users mailing list
 > Wxv...@li...
 > https://lists.sourceforge.net/lists/listinfo/wxvtk-users
 >

Re: [wxVTK] about wxVTK

[Mathieu M. <mma...@ny...>]

Hello Francesco,

	Welcome to the VTK world ! Once you discover you won't go back ever :).

	More seriously you cannot compare gnuplot to VTK, but VTK does a pretty 
good job at large dataset, and tons of 3d stuff. This is an abstract 
layer above OpenGL. It has wrapping for Tcl, Python, Java and even 
octave (matlab clone). The learning curve is reasonable not too steep 
but keep in mind that there is almost 1000 classes just in VTK itself 
(not counting users contrib, example, and project like paraview).

As for 2. wxVTK is only a bridge between wxWidget and VTK. So you can 
use it in your wx project and it allow you access to the full power of 
VTK. But wxVTK is pretty generic there is nothing done in particular for 
math user like you.

HTH
Mathieu

f18m_217828 wrote:
> Hi,
>    I'm the admin of the MathStudio project 
> (http://mathstudio.sourceforge.net) and I'd like to ask you a couple of 
> things about your wxVTK project:
> 
> 1) I'm a C++ wx-user since quite much time but I've never used VTK; so, 
> before any other question, I need to know: VTK can be used to plot math 
> data ?
> 
> 2) If yes, wxVTK allows to use VTK in this sense ?
> 
> Thanks,
> Francesco Montorsi
> 
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
> 

[wxVTK] about wxVTK

[f18m_217828 <f18...@ya...>]

Hi,
    I'm the admin of the MathStudio project 
(http://mathstudio.sourceforge.net) and I'd like to ask you a couple of 
things about your wxVTK project:

1) I'm a C++ wx-user since quite much time but I've never used VTK; so, 
before any other question, I need to know: VTK can be used to plot math 
data ?

2) If yes, wxVTK allows to use VTK in this sense ?

Thanks,
Francesco Montorsi

Re: [wxVTK] Resizing problem under wxMSW

[Mathieu M. <mma...@ny...>]

John,

	Thanks a lot for your patch. I just patched wxVTK with your proposed 
changed.:

$ cvs ci -m"BUG: Fix resize problem. Thanks to patch from John Norris" 
wxVTKRenderWindowInteractor.cxx
Checking in wxVTKRenderWindowInteractor.cxx;
/cvsroot/wxvtk/wxVTK/src/wxVTKRenderWindowInteractor.cxx,v  <-- 
wxVTKRenderWindowInteractor.cxx
new revision: 1.17; previous revision: 1.16
done

	I'll try to release wxVTK 0.8 ASAP.
Mathieu

John Norris wrote:
> Hi,
> 
> I ran into a highly frustrating problem when using 
> wxVTKRenderWindowInteractor as a child window in wxMSW.  Specifically, I 
>  have a wxFrame with a few wxSashLayoutWindows, and I'm using the wxVTK 
> window as the "filler" window in wxLayoutAlgorithm::LayoutFrame().
> 
> When the frame first poped up, everything would look fine.  But when I 
> resized the window or dragged a sash, the wxVTKRenderWindowInteractor 
> would mysteriously get too big for its alloted space.
> 
> After much investigation I discovered that when its ParentId is not set, 
> vtkWin32OpenGLRenderWindow automatically increases its size to make room 
> for the title bar and window borders.  In my case at least, this is 
> undesirable behavior.
> 
> The solution is for wxVTKRenderWindowInteractor to set its render 
> window's ParentId as well as its WindowId.  In 
> wxVTKRenderWindowInteractor::OnPaint(), I changed
> 
>   if(!Handle)
>   {
>     Handle = GetHandle();
>     RenderWindow->SetWindowId(reinterpret_cast<void *>(Handle));
>   }
> 
> to
> 
>   if(!Handle)
>   {
>     Handle = GetHandle();
>     RenderWindow->SetWindowId(reinterpret_cast<void *>(Handle));
> #ifdef __WXMSW__
>     RenderWindow->SetParentId(reinterpret_cast<void 
> *>(this->GetParent()->GetHWND()));
> #endif //__WXMSW__
>   }
> 
> I made the call to SetParentId() wxMSW-specific, since wxGTK et al seem 
> to work just fine, and I didn't want to break them.
> 
> Thanks,
> John

[wxVTK] Resizing problem under wxMSW

[John N. <jn...@mc...>]

Hi,

I ran into a highly frustrating problem when using 
wxVTKRenderWindowInteractor as a child window in wxMSW.  Specifically, I 
  have a wxFrame with a few wxSashLayoutWindows, and I'm using the wxVTK 
window as the "filler" window in wxLayoutAlgorithm::LayoutFrame().

When the frame first poped up, everything would look fine.  But when I 
resized the window or dragged a sash, the wxVTKRenderWindowInteractor 
would mysteriously get too big for its alloted space.

After much investigation I discovered that when its ParentId is not set, 
vtkWin32OpenGLRenderWindow automatically increases its size to make room 
for the title bar and window borders.  In my case at least, this is 
undesirable behavior.

The solution is for wxVTKRenderWindowInteractor to set its render 
window's ParentId as well as its WindowId.  In 
wxVTKRenderWindowInteractor::OnPaint(), I changed

   if(!Handle)
   {
     Handle = GetHandle();
     RenderWindow->SetWindowId(reinterpret_cast<void *>(Handle));
   }

to

   if(!Handle)
   {
     Handle = GetHandle();
     RenderWindow->SetWindowId(reinterpret_cast<void *>(Handle));
#ifdef __WXMSW__
     RenderWindow->SetParentId(reinterpret_cast<void 
*>(this->GetParent()->GetHWND()));
#endif //__WXMSW__
   }

I made the call to SetParentId() wxMSW-specific, since wxGTK et al seem 
to work just fine, and I didn't want to break them.

Thanks,
John
-- 
John Norris
Research Programmer
Center for Simulation of Advanced Rockets
http://www.uiuc.edu/ph/www/jnorris