wxvtk-users — wxVTK users

Re: [wxVTK] wxVTK patch

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

On 3 dec 2008, at 00:11, Mathieu Malaterre wrote:

> Patch looks ok. I do not understand this part, though:
>
> ...
> -#if (!wxCHECK_VERSION(2, 8, 0))
> #define USE_WXGLCANVAS
> -#endif
> ...
>
> So you are saying you are using wxGLCanvas in all cases and never see
> any flickering ? I added this case explicitely for ther wx 2.8.x
> release.

Exactly (but I only use wxGLCanvas for the GTK backend, of course).
I never had any problems with flickering. I actually have display  
problems if I _don't_ use wxGLCanvas:
- The first rendering shows a blank window. Only after clicking inside  
it does the window render properly
- The z-ordering is completely backward.

Best regards,
Sander

Re: [wxVTK] wxVTK patch

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

On Tue, Dec 2, 2008 at 3:10 PM, Sander Niemeijer <nie...@st...> wrote:
> Dear all,
>
> We recently made some improvements to our wxVTK based application and in the
> process were able to solve several problems.
> This email contains a patch (against wxVTK 1.3) to
> wxVTKRenderWindowInteractor to solve those problems.

Patch looks ok. I do not understand this part, though:

...
-#if (!wxCHECK_VERSION(2, 8, 0))
 #define USE_WXGLCANVAS
-#endif
...

So you are saying you are using wxGLCanvas in all cases and never see
any flickering ? I added this case explicitely for ther wx 2.8.x
release.

Thanks,

-- 
Mathieu

[wxVTK] wxVTK patch

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

Dear all,

We recently made some improvements to our wxVTK based application and  
in the process were able to solve several problems.
This email contains a patch (against wxVTK 1.3) to  
wxVTKRenderWindowInteractor to solve those problems.

* Timers work again
First of all, we created a fix for the Timer creation problem (there  
were several mails about this on the list). The attached patch works  
correctly with VTK 5.2 and should still work correctly with previous  
VTK versions as well.
The trick is to create implementations for the new  
InternalCreateTimer() and InternalDestroyTimer() functions.
Note that this patch still assumes that we only have one timer  
associated with our interactor (having multiple timers for an  
interactor is a new VTK feature). It should not be too difficult to  
extend the patch to support multiple timers; this requires keeping a  
list of wxTimers in wxVTKRenderWindowInteractor.

* GTK2 crashes or visualization problems
Thanks to a colleague of mine we were also able to solve the issue  
that was discussed on January 2nd from this year.
As Marco summarized back then, there were two non-working situations.
---
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;
---
The 'your patches' was where we also use wxGLCanvas for wxWidgets 2.8  
(whereas wxVTK 1.3 derives from wxWindow for wxWidgets 2.8).
The solution is to start with the patch we already had (so, use  
wxGLCanvas as base class), and add a workaround to make sure that VTK  
does not crash anymore. The crash happened because VTK was destroying  
the X Display (which it shouldn't). The trick is to explicitly set the  
display on the vtkRenderWindowInteractor, thus telling VTK that it no  
longer 'owns' the X Display and is no longer responsible for its  
destruction.


I would be interested to know if this patch works for other people on  
this list and if so, if this patch could be added to wxVTK CVS.

Best regards,
Sander Niemeijer

[wxVTK] wxVTK: wiki activated

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

I have activated the wxVTK wiki:

  http://apps.sourceforge.net/mediawiki/wxvtk/

This will make it easier for the community to build up knowledge of
information that could be missing from the sole wxVTK/index.html page.

Drop me an email if you want write access to the wiki (you'll need a
sf.net account).

Thanks,

-- 
Mathieu

Re: [wxVTK] Problems with vtkImageViewer2

[Steven H. <ste...@gm...>]

Hi Mathieu, thanks for the reply. Sorry I was not clear about this. What I'm
trying to do is fit my 2D image completely within my WxNoteBook object so
that I don't see the background at all. Right now, the background is showing
as a black border around my image.

Thanks,
Steve

On Wed, Nov 26, 2008 at 11:14 AM, Mathieu Malaterre <
mat...@gm...> wrote:

> Steven
> I have absolutely no clue what you mean, sorry. When using
> vtkImageViewer2 (vs vtkImageViewer) your 2D slice is displayed in the
> 3D world (as a texture), so the background is black by default. I
> guess there should be an option to set it to something else ...
>
> > Also as a quick aside, I am getting the following error message
> > (vtkInteractorStyleJoystickCamera (09E7D2C8): Timer start failed) when I
> > click on my window. I understand this is just a one time warning that I
> > won't get again when I close the error message. I'm wondering is there
> > something I can do in code so that I don't get this message (even if the
> > only way is the disable the camera functionality somehow).
>
> I think you can press 'c' to use camera mode instead of joystick mode.
> This has been broken in VTK since > VTK 4.5 (AFAIK). Simply set
> another interactor style that does not rely on the timer API.
>
> 2cts
> --
> Mathieu
>

Re: [wxVTK] Problems with vtkImageViewer2

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

Steven,

On Tue, Nov 25, 2008 at 9:50 PM, Steven Hou <ste...@gm...> wrote:
> Hi Mathieu, thanks for the reply. I was able to display the image by
> changing my code to mimic how it's done in the comments of the example you
> linked for me.
>
> Not working code:
>
> viewer->SetInput(image);
> viewer->SetColorWindow(1230100);
> viewer->SetColorLevel(615050);
> viewer->SetupInteractor ( m_pVTKWindow );
>
> Working code:
>
> viewer->SetColorWindow(1230100);
> viewer->SetColorLevel(615050);
> viewer->SetupInteractor (NULL);
> viewer->SetRenderWindow(m_pVTKWindow->GetRenderWindow());
> viewer->SetInput(image);
> viewer->GetRenderer()->ResetCamera();

cool, thanks for report !

> The problem for me now is that I have this black border around my image. I
> have attached an example of what I mean. My image does resize properly when
> I change the window size but the black border is always there. Do you have
> any ideas about how I can get rid of it?

I have absolutely no clue what you mean, sorry. When using
vtkImageViewer2 (vs vtkImageViewer) your 2D slice is displayed in the
3D world (as a texture), so the background is black by default. I
guess there should be an option to set it to something else ...

> Also as a quick aside, I am getting the following error message
> (vtkInteractorStyleJoystickCamera (09E7D2C8): Timer start failed) when I
> click on my window. I understand this is just a one time warning that I
> won't get again when I close the error message. I'm wondering is there
> something I can do in code so that I don't get this message (even if the
> only way is the disable the camera functionality somehow).

I think you can press 'c' to use camera mode instead of joystick mode.
This has been broken in VTK since > VTK 4.5 (AFAIK). Simply set
another interactor style that does not rely on the timer API.

2cts
-- 
Mathieu

Re: [wxVTK] Problems with vtkImageViewer2

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

On Sun, Nov 23, 2008 at 5:01 AM, Steven Hou <ste...@gm...> wrote:
> Hi everyone, I am trying to display a 2D image using wxVTK:
>
> My code looks something like this:
>
> vtkImageViewer2 *viewer;
> wxVTKRenderWindowInteractor *m_pVTKWindow;
>
> viewer = vtkImageViewer2::New();
> m_pVTKWindow = new wxVTKRenderWindowInteractor(notebook, MY_VTK_WINDOW);
> notebook->AddPage(m_pVTKWindow, "wxVTK");
>
> vtkImageData *image = vtkImageData::New();
> image->SetDimensions(xSize+1,ySize+1,zSize+1);
> image->SetScalarTypeToDouble();
> image->AllocateScalars();
>
> double *x = static_cast<double*>(image->GetScalarPointer());
>
>     ... I fill x with data
>
> viewer->SetInput(image);
> viewer->SetColorWindow(1230100);
> viewer->SetColorLevel(615050);
> viewer->SetupInteractor (  m_pVTKWindow );
>
> When I compile this code, the image viewer displays a black screen. If I
> change vtkImageViewer2 to vtkImageViewer, the image is displayed properly.
> Are there compatibility issues with wxVTK and vtkImageViewer2?

Yes.
I think it happen somewhere in between VTK 4.4 and VTK 5.0 (during the
pipeline transition). I tried once to figure out what was going on,
but gave up.

I think the ordering with SetupInteractor is important. For instance,
this used to work:

http://gdcm.svn.sf.net/viewvc/gdcm/trunk/Utilities/wxWidgets/wxGDCMFrame.cpp?view=markup

If you find anything, please let me know !

Thanks
-- 
Mathieu

[wxVTK] Problems with vtkImageViewer2

[Steven H. <ste...@gm...>]

Hi everyone, I am trying to display a 2D image using wxVTK:

My code looks something like this:

vtkImageViewer2 *viewer;
wxVTKRenderWindowInteractor *m_pVTKWindow;

viewer = vtkImageViewer2::New();
m_pVTKWindow = new wxVTKRenderWindowInteractor(notebook, MY_VTK_WINDOW);
notebook->AddPage(m_pVTKWindow, "wxVTK");

vtkImageData *image = vtkImageData::New();
image->SetDimensions(xSize+1,ySize+1,zSize+1);
image->SetScalarTypeToDouble();
image->AllocateScalars();

double *x = static_cast<double*>(image->GetScalarPointer());

    ... I fill x with data

viewer->SetInput(image);
viewer->SetColorWindow(1230100);
viewer->SetColorLevel(615050);
viewer->SetupInteractor (  m_pVTKWindow );

When I compile this code, the image viewer displays a black screen. If I
change vtkImageViewer2 to vtkImageViewer, the image is displayed properly.
Are there compatibility issues with wxVTK and vtkImageViewer2?

Thanks

Re: [wxVTK] LeftButtonReleaseEvent - wxVTKRenderWindowInteractor

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

That's the python version of wxVTK. I do not maintain it. Add
debug/print statement in the wxVTK.py code and try to understand why
the event is not triggered.

On Tue, Nov 4, 2008 at 5:42 PM, Paulo Henrique Junqueira Amorim
<pau...@gm...> wrote:
> Hello,
>
> I'm having a problem dealing with the event LeftButtonPressEvent in
> wxVTKRenderWindowInteractor, this event only occurs if you click twice
> quickly.
>
>
> The code:
>
> interactor.AddObserver ( "LeftButtonReleaseEvent", myfunction)
>
>
> I'm using the version that is available at:
>
> http://www.vtk.org/cgi-bin/viewcvs.cgi/*checkout*/Wrapping/Python/vtk/wx/wxVTKRenderWindowInteractor.py
> http://www.vtk.org/cgi-bin/viewcvs.cgi/*checkout*/Wrapping/Python/vtk/wx/wxVTKRenderWindow.py
>
>
>
> Regards,
> Paulo Amorim
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>
>



-- 
Mathieu

[wxVTK] LeftButtonReleaseEvent - wxVTKRenderWindowInteractor

[Paulo H. J. A. <pau...@gm...>]

Hello,

I'm having a problem dealing with the event LeftButtonPressEvent in
wxVTKRenderWindowInteractor, this event only occurs if you click twice
quickly.


The code:

interactor.AddObserver ( "LeftButtonReleaseEvent", myfunction)


I'm using the version that is available at:

http://www.vtk.org/cgi-bin/viewcvs.cgi/*checkout*/Wrapping/Python/vtk/wx/wxVTKRenderWindowInteractor.py
http://www.vtk.org/cgi-bin/viewcvs.cgi/*checkout*/Wrapping/Python/vtk/wx/wxVTKRenderWindow.py



Regards,
Paulo Amorim

Re: [wxVTK] still problems on MAC

[Nigel N. <nn...@gm...>]

On 10/27/08, Doug McCorkle <mc...@ia...> wrote:

> The only way I have been able to get wxVTK to work on Mac is with VTK
> compiled with Carbon support. This is required since wxWidgets does
> not have strong Cocoa support yet. I know it is in the works and
> available but is not as robust as their Carbon support.

For those with an interest in Macs, there is helpful discussion here:

http://wiki.wxwidgets.org/Development:_wxMac

Sounds like the wx team are evolving wxOSX to accommodate full support
for future Apple operating systems (i.e. by moving Cocoa code into
wxOSX rather than extending wxMac).

For current projects, as Doug suggests, just use the stable Carbon version.

Nigel

Re: [wxVTK] still problems on MAC

[Doug M. <mc...@ia...>]

On Oct 22, 2008, at 8:08 AM, Mathieu Malaterre wrote:

> Hi,
>
> On Wed, Oct 22, 2008 at 10:52 AM, genesy genesy <ge...@gm...>  
> wrote:
>>>> ERROR: In /Users/xael/VTK/Rendering/vtkPicker.cxx, line 170
>>>> vtkCellPicker (0x2435270): Bad homogeneous coordinates
>>>
>>> So it does confirm the interactions are working properly. At least  
>>> it
>>> is going from the system to wx to VTK. There is something else going
>>> on. You need to debug the application (gdb) to understand why the
>>> object is not moving.
>>
>> Maybe it's helpful: the object is not rendered at all . A grey window
>> is visualized.
>
>
> I understand that, but I am working only on linux. I have no way to
> reproduce your issue. This goes beyond my understanding. Since I
> believe the issue can be reproduce using straight Cocoa + VTK, I would
> suggest you try the regular VTK example, debug them until you get them
> working.
>
> I've CC the vtkusers lists, where there are a lot more people using
> mac (and hopefully understanding your issue.)

The only way I have been able to get wxVTK to work on Mac is with VTK  
compiled with Carbon support. This is required since wxWidgets does  
not have strong Cocoa support yet. I know it is in the works and  
available but is not as robust as their Carbon support.

Doug

Re: [wxVTK] still problems on MAC

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

Hi,

On Wed, Oct 22, 2008 at 10:52 AM, genesy genesy <ge...@gm...> wrote:
>>> ERROR: In /Users/xael/VTK/Rendering/vtkPicker.cxx, line 170
>>> vtkCellPicker (0x2435270): Bad homogeneous coordinates
>>
>> So it does confirm the interactions are working properly. At least it
>> is going from the system to wx to VTK. There is something else going
>> on. You need to debug the application (gdb) to understand why the
>> object is not moving.
>
> Maybe it's helpful: the object is not rendered at all . A grey window
> is visualized.


I understand that, but I am working only on linux. I have no way to
reproduce your issue. This goes beyond my understanding. Since I
believe the issue can be reproduce using straight Cocoa + VTK, I would
suggest you try the regular VTK example, debug them until you get them
working.

I've CC the vtkusers lists, where there are a lot more people using
mac (and hopefully understanding your issue.)

Good luck;
-- 
Mathieu

Re: [wxVTK] still problems on MAC

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

On Wed, Oct 22, 2008 at 10:25 AM, genesy genesy <ge...@gm...> wrote:
>> ok then. Please try:
>>
>> $ /Developer/Tools/Rez Carbon.r -o
>> /Users/xael/wxVTK_latest/wxVTK/build/bin/wxSample.app/Contents/MacOS/wxSample
>>
>> then rerun your app.
>>
>
> I used the Rez command as you suggested and I ran  the application.
>
> ..
>>
>> none of the usual interaction works either ? ('t','p','f' ...)
>>
>
> pressing 'p' I get :
>
> ERROR: In /Users/xael/VTK/Rendering/vtkPicker.cxx, line 170
> vtkCellPicker (0x2435270): Bad homogeneous coordinates

So it does confirm the interactions are working properly. At least it
is going from the system to wx to VTK. There is something else going
on. You need to debug the application (gdb) to understand why the
object is not moving. But you have *everything* to have it working
AFAIK.

2cts
-- 
Mathieu

Re: [wxVTK] still problems on MAC

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

On Wed, Oct 22, 2008 at 10:05 AM, genesy genesy <ge...@gm...> wrote:
> Hi
>
> ...
>>
>> ok looks fine. And when you execute:
>>
>> $ /Users/xael/wxVTK_latest/wxVTK/build/bin/wxSample
>>
>
> /Users/xael/wxVTK_latest/wxVTK/build/bin/wxSample is an empty file.
> I ran    the executable in the boundle
> /Users/xael/wxVTK_latest/wxVTK/build/bin/wxSample.app/Contents/MacOS/wxSample.

ok then. Please try:

$ /Developer/Tools/Rez Carbon.r -o
/Users/xael/wxVTK_latest/wxVTK/build/bin/wxSample.app/Contents/MacOS/wxSample

then rerun your app.

> When I move the  mouse holding the mouse button  + CTRL I get  this error :
>
> ERROR: In /Users/xael/VTK/Rendering/vtkInteractorStyleJoystickCamera.cxx,
> line 315
> vtkInteractorStyleJoystickCamera (0x2435ac0): Bad zoom factor encountered

hum... so that means mouse interaction are working fine... since we
are in the VTK layer...

> Nothing happens with "w".

none of the usual interaction works either ? ('t','p','f' ...)


-- 
Mathieu

Re: [wxVTK] still problems on MAC

[genesy g. <ge...@gm...>]

Hi

...
>
> ok looks fine. And when you execute:
>
> $ /Users/xael/wxVTK_latest/wxVTK/build/bin/wxSample
>

/Users/xael/wxVTK_latest/wxVTK/build/bin/wxSample is an empty file.
I ran    the executable in the boundle
/Users/xael/wxVTK_latest/wxVTK/build/bin/wxSample.app/Contents/MacOS/wxSample.

When I move the  mouse holding the mouse button  + CTRL I get  this error :

ERROR: In /Users/xael/VTK/Rendering/vtkInteractorStyleJoystickCamera.cxx,
line 315
vtkInteractorStyleJoystickCamera (0x2435ac0): Bad zoom factor encountered

Nothing happens with "w".
bye


MacOsX 10.4
G.

Re: [wxVTK] still problems on MAC

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

On Tue, Oct 21, 2008 at 6:50 PM, genesy genesy <ge...@gm...> wrote:
> 2008/10/21 Mathieu Malaterre <mat...@gm...>:
>> On Tue, Oct 21, 2008 at 6:14 PM, genesy genesy <ge...@gm...> wrote:
>>> I tried the latest version (the Rez attempt) you committed but nothing
>>> is changed.
>>> When I launch the wxSample application I see  a grey window and nothing else.
>>> Any Idea ? :-)
>>
>>
>> ok do that for me:
>>
>> $ make clean
>> $ make wxVTKSample VERBOSE=1 >& matt.log
>>
>
> done

ok looks fine. And when you execute:

$ /Users/xael/wxVTK_latest/wxVTK/build/bin/wxSample

do you see any error message ? It starts ok, but interaction
(mouse/keyboard are not working: try 'w')

>> and send me the matt.log file.
>>
>>> p.s. there is a typo in the CMakeList file:  the lines referring to
>>> SRCS_VTKNotebook  have been stripped.
>>
>> Hu ? Where did you see that ?
>>
>> http://wxvtk.cvs.sf.net/viewvc/wxvtk/wxVTK/CMakeLists.txt?r1=1.33&r2=1.34
>>
>> The line are still there, simply not compiled since it require a more
>> recent VTK version ...
>>
>
> you' right but
> this  is the error I still  get from cmake:
>  ********************
>  CMake Error at CMakeLists.txt:141 (ADD_EXECUTABLE):
>   add_executable called with incorrect number of arguments, no sources
>   provided
> ********************

Sorry about that...


$ cvs ci -m"COMP: fix comp thanks to genesy genesy for report"
CMakeLists.txt

~/Projects/wxVTK
Checking in CMakeLists.txt;
/cvsroot/wxvtk/wxVTK/CMakeLists.txt,v  <--  CMakeLists.txt
new revision: 1.36; previous revision: 1.35
done
Mailing wxv...@li......
Generating notification message...
Generating notification message... done.

Thanks
-- 
Mathieu

[wxVTK] wxVTK CMakeLists.txt,1.35,1.36

[Mathieu M. <ma...@us...>]

Update of /cvsroot/wxvtk/wxVTK
In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv23286

Modified Files:
	CMakeLists.txt 
Log Message:
COMP: fix comp thanks to genesy genesy for report

Index: CMakeLists.txt
===================================================================
RCS file: /cvsroot/wxvtk/wxVTK/CMakeLists.txt,v
retrieving revision 1.35
retrieving revision 1.36
diff -C2 -d -r1.35 -r1.36
*** CMakeLists.txt	21 Oct 2008 15:30:17 -0000	1.35
--- CMakeLists.txt	21 Oct 2008 21:42:44 -0000	1.36
***************
*** 101,105 ****
    )
  
- IF( "${VTK_MAJOR_VERSION}" STREQUAL "5")
  # need vtkrenderwindow::finalize which has been added ~VTK 5.0
  SET(SRCS_VTKNotebook
--- 101,104 ----
***************
*** 107,111 ****
    src/wxVTKRenderWindowInteractor.cxx
    )
- ENDIF( "${VTK_MAJOR_VERSION}" STREQUAL "5")
  
  IF(NOT VTK_USE_RENDERING)
--- 106,109 ----
***************
*** 139,143 ****
--- 137,143 ----
  ADD_EXECUTABLE(wxImageViewer ${GUI_EXECUTABLE} ${SRCS_ImageViewer})
  ADD_EXECUTABLE(wxMedical3 ${GUI_EXECUTABLE} ${SRCS_Medical3})
+ IF( "${VTK_MAJOR_VERSION}" STREQUAL "5")
  ADD_EXECUTABLE(wxVTKNotebook ${GUI_EXECUTABLE} ${SRCS_VTKNotebook})
+ ENDIF( "${VTK_MAJOR_VERSION}" STREQUAL "5")
  
    INSTALL(TARGETS

Re: [wxVTK] still problems on MAC

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

On Tue, Oct 21, 2008 at 6:14 PM, genesy genesy <ge...@gm...> wrote:
> I tried the latest version (the Rez attempt) you committed but nothing
> is changed.
> When I launch the wxSample application I see  a grey window and nothing else.
> Any Idea ? :-)


ok do that for me:

$ make clean
$ make wxVTKSample VERBOSE=1 >& matt.log

and send me the matt.log file.

> p.s. there is a typo in the CMakeList file:  the lines referring to
> SRCS_VTKNotebook  have been stripped.

Hu ? Where did you see that ?

http://wxvtk.cvs.sf.net/viewvc/wxvtk/wxVTK/CMakeLists.txt?r1=1.33&r2=1.34

The line are still there, simply not compiled since it require a more
recent VTK version ...

-- 
Mathieu

[wxVTK] still problems on MAC

[genesy g. <ge...@gm...>]

I tried the latest version (the Rez attempt) you committed but nothing
is changed.
When I launch the wxSample application I see  a grey window and nothing else.
Any Idea ? :-)

p.s. there is a typo in the CMakeList file:  the lines referring to
SRCS_VTKNotebook  have been stripped.


G.

Re: [wxVTK] a compilation problem and a .... mystery

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

On Tue, Oct 21, 2008 at 4:58 PM, Mathieu Malaterre
<mat...@gm...> wrote:
> On Tue, Oct 21, 2008 at 4:47 PM, genesy genesy <ge...@gm...> wrote:
>> thanks Mathieu for your quickness!
>>
>> the compilation goes fine with this only exception:
>>
>>
>> Scanning dependencies of target wxVTKNotebook
>> [ 91%] Building CXX object
>> CMakeFiles/wxVTKNotebook.dir/Sample/wxVTKNotebook.cxx.o
>> /Users/xael/wxVTK_latest/wxVTK/Sample/wxVTKNotebook.cxx: In member
>> function 'void MyFrame::OnNoteBookChanging(wxNotebookEvent&)':
>> /Users/xael/wxVTK_latest/wxVTK/Sample/wxVTKNotebook.cxx:181: error:
>> 'class vtkRenderWindow' has no member named 'Finalize'
>> /Users/xael/wxVTK_latest/wxVTK/Sample/wxVTKNotebook.cxx: In member
>> function 'void MyFrame::FillVTK(wxPanel*, wxGridSizer*)':
>> /Users/xael/wxVTK_latest/wxVTK/Sample/wxVTKNotebook.cxx:215: error:
>> 'wxGetDisplay' was not declared in this scope
>> make[2]: *** [CMakeFiles/wxVTKNotebook.dir/Sample/wxVTKNotebook.cxx.o] Error 1
>> make[1]: *** [CMakeFiles/wxVTKNotebook.dir/all] Error 2
>> make: *** [all] Error 2
>
> Fixed:
>
> $ cvs ci -m"COMP: fix compilation for vtkrw::finalize"
>
>
> ~/Projects/wxVTK
> ? Sample/wxLeaks.cxx
> ? current.patch
> ? bin
> Checking in CMakeLists.txt;
> /cvsroot/wxvtk/wxVTK/CMakeLists.txt,v  <--  CMakeLists.txt
> new revision: 1.34; previous revision: 1.33
> done
> Mailing wxv...@li......
> Generating notification message...
> Generating notification message... done.
>
> thx !
>>
>> but the big trouble appears when I launch wxImagePlaneWidget :  two
>> windows are shown and I can't do nothing with them .
>> The first one is  is  white and is labeled "vtkX - Carbon#1"   the
>> second one is grey  and its name is "wxWindows - VTK App".
>
> Hum... I fear this is a nasty issue on the mac (cannot reproduce it here...).
> Can you press the 't' key,  this should go into trackball mode, and
> you'll be able to interact a little more smoothly with the cone.
>
>> If you think is helpful  I could  load the application in a debugger
>> (gdb command line or Xcode) and with your help find out information
>> about this problem...
>
> If the previous comment does not work, I think you are suffering from
> the 'Rez' issue.
>
> From the command line, try typing:
>
> /Developer/Tools/Rez Carbon.r -o wxVTKSample

Try again now:


$ cvs ci -m"ENH: attempt for MacOSX" CMakeLists.txt


~/Projects/wxVTK
Checking in CMakeLists.txt;
/cvsroot/wxvtk/wxVTK/CMakeLists.txt,v  <--  CMakeLists.txt
new revision: 1.35; previous revision: 1.34
done
Mailing wxv...@li......
Generating notification message...
Generating notification message... done.


Can you get interaction working on the wxSample example ?


-- 
Mathieu

[wxVTK] wxVTK CMakeLists.txt,1.34,1.35

[Mathieu M. <ma...@us...>]

Update of /cvsroot/wxvtk/wxVTK
In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv32705

Modified Files:
	CMakeLists.txt 
Log Message:
ENH: attempt for MacOSX

Index: CMakeLists.txt
===================================================================
RCS file: /cvsroot/wxvtk/wxVTK/CMakeLists.txt,v
retrieving revision 1.34
retrieving revision 1.35
diff -C2 -d -r1.34 -r1.35
*** CMakeLists.txt	21 Oct 2008 14:53:02 -0000	1.34
--- CMakeLists.txt	21 Oct 2008 15:30:17 -0000	1.35
***************
*** 124,127 ****
--- 124,137 ----
  
  ADD_EXECUTABLE(wxSample ${GUI_EXECUTABLE} ${SRCS_Sample})
+ GET_TARGET_PROPERTY(wxSample_PATH wxSample LOCATION)
+ 
+  IF(APPLE)
+    FIND_PROGRAM(APPLE_RESOURCE Rez /Developer/Tools)
+    IF(APPLE_RESOURCE)
+      ADD_CUSTOM_COMMAND(TARGET wxSample POST_BUILD
+                         COMMAND ${APPLE_RESOURCE} Carbon.r -o ${wxSample_PATH})
+    ENDIF(APPLE_RESOURCE)
+  ENDIF(APPLE)
+ 
  ADD_EXECUTABLE(wxSplitSample ${GUI_EXECUTABLE} ${SRCS_SplitSample})
  

Re: [wxVTK] a compilation problem and a .... mystery

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

On Tue, Oct 21, 2008 at 4:47 PM, genesy genesy <ge...@gm...> wrote:
> thanks Mathieu for your quickness!
>
> the compilation goes fine with this only exception:
>
>
> Scanning dependencies of target wxVTKNotebook
> [ 91%] Building CXX object
> CMakeFiles/wxVTKNotebook.dir/Sample/wxVTKNotebook.cxx.o
> /Users/xael/wxVTK_latest/wxVTK/Sample/wxVTKNotebook.cxx: In member
> function 'void MyFrame::OnNoteBookChanging(wxNotebookEvent&)':
> /Users/xael/wxVTK_latest/wxVTK/Sample/wxVTKNotebook.cxx:181: error:
> 'class vtkRenderWindow' has no member named 'Finalize'
> /Users/xael/wxVTK_latest/wxVTK/Sample/wxVTKNotebook.cxx: In member
> function 'void MyFrame::FillVTK(wxPanel*, wxGridSizer*)':
> /Users/xael/wxVTK_latest/wxVTK/Sample/wxVTKNotebook.cxx:215: error:
> 'wxGetDisplay' was not declared in this scope
> make[2]: *** [CMakeFiles/wxVTKNotebook.dir/Sample/wxVTKNotebook.cxx.o] Error 1
> make[1]: *** [CMakeFiles/wxVTKNotebook.dir/all] Error 2
> make: *** [all] Error 2

Fixed:

$ cvs ci -m"COMP: fix compilation for vtkrw::finalize"


~/Projects/wxVTK
? Sample/wxLeaks.cxx
? current.patch
? bin
Checking in CMakeLists.txt;
/cvsroot/wxvtk/wxVTK/CMakeLists.txt,v  <--  CMakeLists.txt
new revision: 1.34; previous revision: 1.33
done
Mailing wxv...@li......
Generating notification message...
Generating notification message... done.

thx !
>
> but the big trouble appears when I launch wxImagePlaneWidget :  two
> windows are shown and I can't do nothing with them .
> The first one is  is  white and is labeled "vtkX - Carbon#1"   the
> second one is grey  and its name is "wxWindows - VTK App".

Hum... I fear this is a nasty issue on the mac (cannot reproduce it here...).
Can you press the 't' key,  this should go into trackball mode, and
you'll be able to interact a little more smoothly with the cone.

> If you think is helpful  I could  load the application in a debugger
> (gdb command line or Xcode) and with your help find out information
> about this problem...

If the previous comment does not work, I think you are suffering from
the 'Rez' issue.

>From the command line, try typing:

/Developer/Tools/Rez Carbon.r -o wxVTKSample

HTH
-- 
Mathieu

[wxVTK] wxVTK CMakeLists.txt,1.33,1.34

[Mathieu M. <ma...@us...>]

Update of /cvsroot/wxvtk/wxVTK
In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv30289

Modified Files:
	CMakeLists.txt 
Log Message:
COMP: fix compilation for vtkrw::finalize

Index: CMakeLists.txt
===================================================================
RCS file: /cvsroot/wxvtk/wxVTK/CMakeLists.txt,v
retrieving revision 1.33
retrieving revision 1.34
diff -C2 -d -r1.33 -r1.34
*** CMakeLists.txt	21 Oct 2008 14:15:28 -0000	1.33
--- CMakeLists.txt	21 Oct 2008 14:53:02 -0000	1.34
***************
*** 101,108 ****
--- 101,111 ----
    )
  
+ IF( "${VTK_MAJOR_VERSION}" STREQUAL "5")
+ # need vtkrenderwindow::finalize which has been added ~VTK 5.0
  SET(SRCS_VTKNotebook
    Sample/wxVTKNotebook.cxx
    src/wxVTKRenderWindowInteractor.cxx
    )
+ ENDIF( "${VTK_MAJOR_VERSION}" STREQUAL "5")
  
  IF(NOT VTK_USE_RENDERING)

[wxVTK] a compilation problem and a .... mystery

[genesy g. <ge...@gm...>]

thanks Mathieu for your quickness!

the compilation goes fine with this only exception:


Scanning dependencies of target wxVTKNotebook
[ 91%] Building CXX object
CMakeFiles/wxVTKNotebook.dir/Sample/wxVTKNotebook.cxx.o
/Users/xael/wxVTK_latest/wxVTK/Sample/wxVTKNotebook.cxx: In member
function 'void MyFrame::OnNoteBookChanging(wxNotebookEvent&)':
/Users/xael/wxVTK_latest/wxVTK/Sample/wxVTKNotebook.cxx:181: error:
'class vtkRenderWindow' has no member named 'Finalize'
/Users/xael/wxVTK_latest/wxVTK/Sample/wxVTKNotebook.cxx: In member
function 'void MyFrame::FillVTK(wxPanel*, wxGridSizer*)':
/Users/xael/wxVTK_latest/wxVTK/Sample/wxVTKNotebook.cxx:215: error:
'wxGetDisplay' was not declared in this scope
make[2]: *** [CMakeFiles/wxVTKNotebook.dir/Sample/wxVTKNotebook.cxx.o] Error 1
make[1]: *** [CMakeFiles/wxVTKNotebook.dir/all] Error 2
make: *** [all] Error 2


but the big trouble appears when I launch wxImagePlaneWidget :  two
windows are shown and I can't do nothing with them .
The first one is  is  white and is labeled "vtkX - Carbon#1"   the
second one is grey  and its name is "wxWindows - VTK App".

If you think is helpful  I could  load the application in a debugger
(gdb command line or Xcode) and with your help find out information
about this problem...

bye


SO: MacOsX 10.4.11
xcode: 2.4.1
gcc version: 4.0.1
wx-config --version-full :  2.6.3.1
VTK 4.4 Carbon
ccmake version 2.6-patch 1

G.