wxvtk-users — wxVTK users

Re: [wxVTK] Basic Question. Compiling on Linux and Windows.

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

For gtk2 the situation is a bit less troublesome if you make use of  
pkg-config.
For our project I add the output of `pkg-config --cflags gtk+-2.0` to  
the CPPFLAGS together with -I/usr/X11R6/include and add -lgdk-x11-2.0  
as an additional library to link to.
The use of pkg-config saves you the trouble of enumerating all the -I  
paths for gtk2 yourself.

However, this is all without using CMake.

Best regards,
Sander

On 11 jun 2008, at 09:44, Mathieu Malaterre wrote:

> Hi RS,
>
>
> On Wed, Jun 11, 2008 at 1:04 AM, R S <gri...@ho...> wrote:
>> Hi,
>>
>> This is probably a basic question for all of you, I would like to  
>> use wxVTK
>> in my own project. I tried to include the source files directly in my
>> project but I gave up because I had to add all the gtk  
>> dependencies, headers
>> and what not to the project which I don't really want to do because  
>> I am
>> using wx.
>
> Yeah I know, I can give you all the details for this one. For  
> instance:
>
> http://lists.wxwidgets.org/pipermail/wx-dev/2004-September/050814.html
>
> I have been begging since 2004 for just *ONE* hook in the wxWidgets
> library, and they have consistently refuse. Basically they are not
> happy that I want to access the XWindow pointer on UNIX to open a
> window. There point of view if if you are using wx-gtk1 you need to
> know that internally you have open a gtk1 window, and if you want to
> access anything hidden in gtk1, then YOU need to include all the gtk1
> headers, same goes for gtk2...
> So the real problem is that that port that most people use on *NIX is
> a double indirection on top of X11, and wx people only probivde access
> to the first indirection layer.
>
> the thing that really pi*** me off, is that Robert Roebling has made
> this hook available in his python-wx library (the python code of wxVTK
> is actually cleaner than the c++ library and does not require
> importing anything from gtk*).
>
> Actually if you have python-wx installed on your machine you could
> call this python function :-P
>
>> So I did the standard cmake compilation but that pretty much builds  
>> the
>> samples and leaves with only an object file burried deep in the  
>> directory
>> structure.
>
> I cannot simply make a library made of a single class, the overhead is
> AFAIK way too high (dll initialization, static linking...). Therefore
> I assumed people would just simply integrate the single C++ class
> directly into there project. (*)
>
>> How can I compile it into a static or dynamic library on linux to  
>> include it
>> into my project? OR how can I add it to my project without going  
>> through the
>> whole gtk run around?
>
> Suscribe to wx-dev mailing list, and tell them your story...
>
>> I am newbie to cmake so if there is a simple command... don't  
>> scream at me
>
> No that's not a cmake issue, you HAVE TO (last time I checked) include
> the gtk header to be able to extract the XWindow pointer from a
> GTKWindow pointer.
>
> HTH
> -- 
> Mathieu
> (*) There is also a nasty problem due to my initial design, the wxVTK
> class has multiple inheritance which make it actually difficult to
> wrap in a shared/static library...
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users

Re: [wxVTK] Basic Question. Compiling on Linux and Windows.

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

Hi RS,


On Wed, Jun 11, 2008 at 1:04 AM, R S <gri...@ho...> wrote:
> Hi,
>
> This is probably a basic question for all of you, I would like to use wxVTK
> in my own project. I tried to include the source files directly in my
> project but I gave up because I had to add all the gtk dependencies, headers
> and what not to the project which I don't really want to do because I am
> using wx.

Yeah I know, I can give you all the details for this one. For instance:

http://lists.wxwidgets.org/pipermail/wx-dev/2004-September/050814.html

I have been begging since 2004 for just *ONE* hook in the wxWidgets
library, and they have consistently refuse. Basically they are not
happy that I want to access the XWindow pointer on UNIX to open a
window. There point of view if if you are using wx-gtk1 you need to
know that internally you have open a gtk1 window, and if you want to
access anything hidden in gtk1, then YOU need to include all the gtk1
headers, same goes for gtk2...
So the real problem is that that port that most people use on *NIX is
a double indirection on top of X11, and wx people only probivde access
to the first indirection layer.

the thing that really pi*** me off, is that Robert Roebling has made
this hook available in his python-wx library (the python code of wxVTK
is actually cleaner than the c++ library and does not require
importing anything from gtk*).

Actually if you have python-wx installed on your machine you could
call this python function :-P

> So I did the standard cmake compilation but that pretty much builds the
> samples and leaves with only an object file burried deep in the directory
> structure.

I cannot simply make a library made of a single class, the overhead is
AFAIK way too high (dll initialization, static linking...). Therefore
I assumed people would just simply integrate the single C++ class
directly into there project. (*)

> How can I compile it into a static or dynamic library on linux to include it
> into my project? OR how can I add it to my project without going through the
> whole gtk run around?

Suscribe to wx-dev mailing list, and tell them your story...

> I am newbie to cmake so if there is a simple command... don't scream at me

No that's not a cmake issue, you HAVE TO (last time I checked) include
the gtk header to be able to extract the XWindow pointer from a
GTKWindow pointer.

HTH
-- 
Mathieu
(*) There is also a nasty problem due to my initial design, the wxVTK
class has multiple inheritance which make it actually difficult to
wrap in a shared/static library...

[wxVTK] Basic Question. Compiling on Linux and Windows.

[R S <gri...@ho...>]

Hi,

This is probably a basic question for all of you, I would like to use wxVTK in my own project. I tried to include the source files directly in my project but I gave up because I had to add all the gtk dependencies, headers and what not to the project which I don't really want to do because I am using wx.

So I did the standard cmake compilation but that pretty much builds the samples and leaves with only an object file burried deep in the directory structure.

How can I compile it into a static or dynamic library on linux to include it into my project? OR how can I add it to my project without going through the whole gtk run around?

I am newbie to cmake so if there is a simple command... don't scream at me :P  


RS
_________________________________________________________________
Try Chicktionary, a game that tests how many words you can form from the letters given. Find this and more puzzles at Live Search Games!
http://g.msn.ca/ca55/207

Re: [wxVTK] wxVTK with python

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

Hi Brian,

  I doubt you'll get much help here, as most people here -AFAIK- only
uses the C++ wxVTK. Anyway you did not specify the OS you are running
this (very) short python script into ?

  If this is linux symply run the whole thing via gdb:

$ gdb python
(gdb) run myscript.py

  I would suggest you get rid of the ITK dependencie by either
rewriting your data into something simple (like vtk format), and then
use a simple vtk class to load that data back again.

  If the gdb backtrace is not clear, feel free to send it here.

HTH
-Mathieu

On Tue, Jun 10, 2008 at 10:53 PM, Brian Eastwood <bea...@em...> wrote:
> Hello everyone,
>
> I have used wxVTK in C++ for a while, and wanted to try it in Python.  I
> have a fairly simple pipeline, using WrapITK and vtk's python wrappers:
>
>            imageType = itk.Image[itk.US, 3]
>            reader = itk.ImageFileReader[imageType].New()
>            reader.SetFileName(fileIn)
>
>            convert = itkvtk.ImageToVTKImageFilter[imageType].New()
>            convert.SetInput(reader.GetOutput())
>
>            render = vtk.vtkRenderer()
>            self.rwi.GetRenderWindow().AddRenderer(render)
>
>            viewer = vtk.vtkImagePlaneWidget()
>            viewer.SetInput(convert.GetOutput())
>            viewer.SetPlaneOrientationToZAxes()
>            viewer.SetInteractor(self.rwi)
>            viewer.SetWindowLevel(2000, 1000)
>            viewer.DisplayTextOn()
>            viewer.SetSliceIndex(60)
>            viewer.On()
>
>            self.rwi.GetRenderWindow().Render()
>
> The image displays, but the application crashes when the render window
> is moused-over at wxVTKRenderWindowInteractor line 330:
>
>        self._Iren.MouseMoveEvent()
>
> Some other widgets don't seem to have this problem (e.g. a vtkImageActor
> added to a vtkRenderer by hand).
>
> I am using:
> cmake 2.6.0
> ITK 3.6.0 with WrapITK
> VTK 5.0.4
> wxWidgets 2.8.7
> wxVTK packaged from vtk or from the download here:
> http://www.vtk.org/cgi-bin/viewcvs.cgi/*checkout*/Wrapping/Python/vtk/wx/wxVTKRenderWindowInteractor.py
>
> Has any one else had a similar experience?  Any help on this would be
> very much appreciated.
>
> Thank you in advance,
> Brian Eastwood
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>



-- 
Mathieu

[wxVTK] wxVTK with python

[Brian E. <bea...@em...>]

Hello everyone,

I have used wxVTK in C++ for a while, and wanted to try it in Python.  I 
have a fairly simple pipeline, using WrapITK and vtk's python wrappers:

            imageType = itk.Image[itk.US, 3]
            reader = itk.ImageFileReader[imageType].New()
            reader.SetFileName(fileIn)
           
            convert = itkvtk.ImageToVTKImageFilter[imageType].New()
            convert.SetInput(reader.GetOutput())
                                  
            render = vtk.vtkRenderer()
            self.rwi.GetRenderWindow().AddRenderer(render)

            viewer = vtk.vtkImagePlaneWidget()
            viewer.SetInput(convert.GetOutput())
            viewer.SetPlaneOrientationToZAxes()
            viewer.SetInteractor(self.rwi)
            viewer.SetWindowLevel(2000, 1000)
            viewer.DisplayTextOn()
            viewer.SetSliceIndex(60)
            viewer.On()

            self.rwi.GetRenderWindow().Render()

The image displays, but the application crashes when the render window 
is moused-over at wxVTKRenderWindowInteractor line 330:

        self._Iren.MouseMoveEvent()

Some other widgets don't seem to have this problem (e.g. a vtkImageActor 
added to a vtkRenderer by hand).

I am using:
cmake 2.6.0
ITK 3.6.0 with WrapITK
VTK 5.0.4
wxWidgets 2.8.7
wxVTK packaged from vtk or from the download here:  
http://www.vtk.org/cgi-bin/viewcvs.cgi/*checkout*/Wrapping/Python/vtk/wx/wxVTKRenderWindowInteractor.py

Has any one else had a similar experience?  Any help on this would be 
very much appreciated.

Thank you in advance,
Brian Eastwood

Re: [wxVTK] Timer start failed

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

Ruopeng,

  By turning rendering mode on, I mean that you would usually run your
vtk test like this:

ctest -R MyTest -V

  But instead try this:

ctest -R MyTest -V -N

copy the command line and execute. Usually something like that:

./bin/RenderingCxxTest MyTest -I

  The windows will stay open for you to play with.

  I think the bug crept in around VTK 5. If you are lucky, then maybe
it's not in VTK 5.0. You'll have to try ayway I only have a vague
notion when it appeared.

HTH
-Mathieu

On Mon, Jun 2, 2008 at 9:09 PM, Ruopeng Wang <rp...@nm...> wrote:
> Hi Mathieu,
>
> Thank you so much for your quick reply. I don't know how to turn on the
> interactor mode for those tests. However, in "RenderingCxxTest", there is an
> option for TestInteractorTimers, it seems to be working for me... anyway, I
> don't mind using vtk5.0 for now. Just want to clarify, by vtk5.0 do you mean
> vtk5.0.x? Or only vtk5.0.0?
>
> Thank you,
>
> Ruopeng
>
> Mathieu Malaterre wrote:
>>
>> Hi RP,
>>
>>  This is not an issue with wxVTK but with VTK > 5.0. They broke the
>> internal API for the timer, and no one took the time to fix it. If you
>> are familiar with VTK, simply run ANY of the test that take '-I' to
>> run in interactor more and you'll see that even from pure tcl the
>> timer is failing (whatever that mean).
>>  Please make some noise on the vtk-dev list, as I have already
>> mentionned that a couple of tme, but no one seems to care :(
>>
>> Thanks
>> -Mathieu
>>
>> On Mon, Jun 2, 2008 at 8:23 PM, Ruopeng Wang <rp...@nm...>
>> wrote:
>>
>>>
>>> Hi all,
>>>
>>> I wonder if anyone has experienced this issue with wxGTK-2.8.7. When I
>>> run the sample, I got lots of:
>>>
>>> ERROR: In
>>>
>>> /usr/pubsw/packages/vtk/5.1.0-CVS-stable/src/VTK/Rendering/vtkInteractorStyle.cxx,
>>> line 392
>>> vtkInteractorStyleJoystickCamera (0xc093db8): Timer start failed
>>>
>>> The interactor of course doesn't work properly. At first it is not a big
>>> issue to me, because I usually use trackball style instead of the
>>> default Joystick style in my vtk code. Then here comes the big issue,
>>> because the timer failed to start, vtkLODActor doesn't work anymore,
>>> since it requires timer to manage the active level of detail. Did anyone
>>> have this issue and/or figure out a workaround?
>>>
>>> BTW, I just tried with the latest wxVTK 1.3 code, same problem.
>>>
>>> Thank you!
>>>
>>> RP
>>>
>>>
>>>
>>> -------------------------------------------------------------------------
>>> This SF.net email is sponsored by: Microsoft
>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>> _______________________________________________
>>> Wxvtk-users mailing list
>>> Wxv...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>>>
>>>
>>
>>
>>
>>
>
>



-- 
Mathieu

Re: [wxVTK] Timer start failed

[Ruopeng W. <rp...@nm...>]

Hi Mathieu,

Thank you so much for your quick reply. I don't know how to turn on the 
interactor mode for those tests. However, in "RenderingCxxTest", there 
is an option for TestInteractorTimers, it seems to be working for me... 
anyway, I don't mind using vtk5.0 for now. Just want to clarify, by 
vtk5.0 do you mean vtk5.0.x? Or only vtk5.0.0?

Thank you,

Ruopeng

Mathieu Malaterre wrote:
> Hi RP,
>
>   This is not an issue with wxVTK but with VTK > 5.0. They broke the
> internal API for the timer, and no one took the time to fix it. If you
> are familiar with VTK, simply run ANY of the test that take '-I' to
> run in interactor more and you'll see that even from pure tcl the
> timer is failing (whatever that mean).
>   Please make some noise on the vtk-dev list, as I have already
> mentionned that a couple of tme, but no one seems to care :(
>
> Thanks
> -Mathieu
>
> On Mon, Jun 2, 2008 at 8:23 PM, Ruopeng Wang <rp...@nm...> wrote:
>   
>> Hi all,
>>
>> I wonder if anyone has experienced this issue with wxGTK-2.8.7. When I
>> run the sample, I got lots of:
>>
>> ERROR: In
>> /usr/pubsw/packages/vtk/5.1.0-CVS-stable/src/VTK/Rendering/vtkInteractorStyle.cxx,
>> line 392
>> vtkInteractorStyleJoystickCamera (0xc093db8): Timer start failed
>>
>> The interactor of course doesn't work properly. At first it is not a big
>> issue to me, because I usually use trackball style instead of the
>> default Joystick style in my vtk code. Then here comes the big issue,
>> because the timer failed to start, vtkLODActor doesn't work anymore,
>> since it requires timer to manage the active level of detail. Did anyone
>> have this issue and/or figure out a workaround?
>>
>> BTW, I just tried with the latest wxVTK 1.3 code, same problem.
>>
>> Thank you!
>>
>> RP
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Wxvtk-users mailing list
>> Wxv...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>>
>>     
>
>
>
>   

Re: [wxVTK] Timer start failed

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

Hi RP,

  This is not an issue with wxVTK but with VTK > 5.0. They broke the
internal API for the timer, and no one took the time to fix it. If you
are familiar with VTK, simply run ANY of the test that take '-I' to
run in interactor more and you'll see that even from pure tcl the
timer is failing (whatever that mean).
  Please make some noise on the vtk-dev list, as I have already
mentionned that a couple of tme, but no one seems to care :(

Thanks
-Mathieu

On Mon, Jun 2, 2008 at 8:23 PM, Ruopeng Wang <rp...@nm...> wrote:
> Hi all,
>
> I wonder if anyone has experienced this issue with wxGTK-2.8.7. When I
> run the sample, I got lots of:
>
> ERROR: In
> /usr/pubsw/packages/vtk/5.1.0-CVS-stable/src/VTK/Rendering/vtkInteractorStyle.cxx,
> line 392
> vtkInteractorStyleJoystickCamera (0xc093db8): Timer start failed
>
> The interactor of course doesn't work properly. At first it is not a big
> issue to me, because I usually use trackball style instead of the
> default Joystick style in my vtk code. Then here comes the big issue,
> because the timer failed to start, vtkLODActor doesn't work anymore,
> since it requires timer to manage the active level of detail. Did anyone
> have this issue and/or figure out a workaround?
>
> BTW, I just tried with the latest wxVTK 1.3 code, same problem.
>
> Thank you!
>
> RP
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>



-- 
Mathieu

[wxVTK] Timer start failed

[Ruopeng W. <rp...@nm...>]

Hi all,

I wonder if anyone has experienced this issue with wxGTK-2.8.7. When I 
run the sample, I got lots of:

ERROR: In 
/usr/pubsw/packages/vtk/5.1.0-CVS-stable/src/VTK/Rendering/vtkInteractorStyle.cxx, 
line 392
vtkInteractorStyleJoystickCamera (0xc093db8): Timer start failed

The interactor of course doesn't work properly. At first it is not a big 
issue to me, because I usually use trackball style instead of the 
default Joystick style in my vtk code. Then here comes the big issue, 
because the timer failed to start, vtkLODActor doesn't work anymore, 
since it requires timer to manage the active level of detail. Did anyone 
have this issue and/or figure out a workaround?

BTW, I just tried with the latest wxVTK 1.3 code, same problem.

Thank you!

RP

[wxVTK] wxvtk 1.3 is out

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

That was a painful release... still not quite out... I need to add the
changelog and add the thanks section (without the wxVTK community this
release would not have been possible).

Just for fun I added win32 i386 executables of wxVTK (using wxMSW
2.8.7 and VTK 5.2 both in release and using /MT flags). I'll check the
stats to see if anyone is indeed interested.

I know there is still an issue with char event (?) that need to be
addressed, but unfortunately this did not make it into this release.

Thanks again all for your patience,
-- 
Mathieu

[wxVTK] Fwd: #1315: EVT_SCROLL_THUMBRELEASE not generated

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

FYI


---------- Forwarded message ----------
From: wxTrac <no...@wx...>
Date: Fri, May 30, 2008 at 12:22 AM
Subject: Re: #1315: EVT_SCROLL_THUMBRELEASE not generated
To:
Cc: wx...@li...


Ticket URL: <http://trac.wxwidgets.org/ticket/1315#comment:2>

#1315: EVT_SCROLL_THUMBRELEASE not generated
-----------------------+----------------------------------------------------
 Reporter:  abaecker  |       Owner:
     Type:  defect    |      Status:  closed
 Priority:  normal    |   Milestone:
 Component:  wxGTK     |     Version:
Resolution:  outdated  |    Keywords:
 Blockedby:            |       Patch:  0
 Blocking:            |
-----------------------+----------------------------------------------------
Changes (by wojdyr):

 * status:  new => closed
 * resolution:  => outdated


Comment:

 I tested the program, it works with wx2.8.7


--
Ticket URL: <http://trac.wxwidgets.org/ticket/1315#comment:2>



-- 
Mathieu

Re: [wxVTK] wxVTK + GTK + EVT_CHAR

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

I find it strange that this is needed.

In the CVS version for wxVTKRenderWindowInteractor there are  
registrations for EVT_KEY_DOWN, EVT_KEY_UP, and EVT_CHAR. We should  
thus be receiving both EVT_KEY_DOWN and EVT_CHAR events from  
wxWidgets. This should result in invoke events for both  
vtkCommand::KeyPressEvent and vtkCommand::CharEvent.

We even call the event.Skip() in the OnKeyDown handler in order to  
make sure we also get the EVT_CHAR event (as explained in http://docs.wxwidgets.org/stable/wx_wxkeyevent.html#wxkeyevent) 
.

If the wxVTKRenderWindowInteractor object is not receiving EVT_CHAR  
events (after a EVT_KEY_DOWN event) then this sounds more like a  
wxWidgets issue.

On 24 mei 2008, at 17:36, Nigel Nunn wrote:

> Hello Quoc Cuong and Mathieu,
>
> On Sat, May 24, 2008 at 3:58 PM, <Quo...@ce...> wrote:
>
>> I am using wxVTK 1.2 with GTK2 under linux (FC8).
>> My wxVTKRenderWindowInteractor is embedded in a wxScrolledWindow
>> (child of a frame). I can intercept mouse events but the EVT_CHAR
>> is never sent. Has anybody experienced this problem?
>
>
> I'm using wxVTKRenderWindowInteractor 1.36 (WinXP, VC++2005)
>
>  Date:      $Date: 2008/04/14 15:12:00 $
>  Version:   $Revision: 1.36 $
>
>
> with wx v.2.8.7.  I have a single wxVTK window in a wxAUI docking
> frame layout.  I too found that OnChar() was not getting passed
> through to the wxVTKRWI, but that OnKeyDown() was working fine.
>
> A quick fix for me was to handle the char event in OnKeyDown().
> I invoke a CharEvent after the KeyPressEvent (near line 485):
>
>  InvokeEvent(vtkCommand::KeyPressEvent, NULL);
>  InvokeEvent(vtkCommand::CharEvent, NULL);   // <--- added
>
>
> This fixes the problem for my current case.
>
> Also noticed an issue with small offset to the vertical "y" pick
> position.  When I get a moment I'll try to track that down.
>
> Nigel
>
>
> --
>
>
> -------------------------------------------------------------------------------------
> Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au
>
> This message is intended for the addressee named and may contain  
> confidential and privileged 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.
> -------------------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users

Re: [wxVTK] wxVTK + GTK + EVT_CHAR

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

Hello Quoc Cuong and Mathieu,

On Sat, May 24, 2008 at 3:58 PM, <Quo...@ce...> wrote:

> I am using wxVTK 1.2 with GTK2 under linux (FC8). 
> My wxVTKRenderWindowInteractor is embedded in a wxScrolledWindow 
> (child of a frame). I can intercept mouse events but the EVT_CHAR 
> is never sent. Has anybody experienced this problem?


I'm using wxVTKRenderWindowInteractor 1.36 (WinXP, VC++2005)

  Date:      $Date: 2008/04/14 15:12:00 $
  Version:   $Revision: 1.36 $


with wx v.2.8.7.  I have a single wxVTK window in a wxAUI docking 
frame layout.  I too found that OnChar() was not getting passed 
through to the wxVTKRWI, but that OnKeyDown() was working fine. 

A quick fix for me was to handle the char event in OnKeyDown().
I invoke a CharEvent after the KeyPressEvent (near line 485):

  InvokeEvent(vtkCommand::KeyPressEvent, NULL);
  InvokeEvent(vtkCommand::CharEvent, NULL);   // <--- added


This fixes the problem for my current case. 

Also noticed an issue with small offset to the vertical "y" pick 
position.  When I get a moment I'll try to track that down.

Nigel


--


-------------------------------------------------------------------------------------
Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au

This message is intended for the addressee named and may contain confidential and privileged 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.
-------------------------------------------------------------------------------------

Re: [wxVTK] wxVTK + GTK + EVT_CHAR

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

Quoc Cuong

  I would suggest you try wxVTK from CVS before anything else. I was
supposed to release wxVTK 1.3 right after cmake 2.6 was released but a
regression went in my way:

http://www.cmake.org/pipermail/cmake/2008-May/021814.html

  I am getting seriously tired now at wx & cmake people... they
externalize bugs report & solving to there customer :( I did not even
try to solve the issue.

  If CVS does not solve your issue, please report again.

Thanks
-Mathieu

On Sat, May 24, 2008 at 3:58 PM, PHAM Quoc-Cuong 203899
<Quo...@ce...> wrote:
> Hi
> I am using wxVTK 1.2 with GTK2 under linux (FC8). My wxVTKRenderWindowInteractor is embedded in a wxScrolledWindow (child of a frame).
> I can intercept mouse events but the EVT_CHAR is never sent.
> Has anybody experienced this problem?
>
> Quoc Cuong
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>



-- 
Mathieu

[wxVTK] wxVTK + GTK + EVT_CHAR

[PHAM Quoc-C. 2. <Quo...@ce...>]

Hi
I am using wxVTK 1.2 with GTK2 under linux (FC8). My wxVTKRenderWindowInteractor is embedded in a wxScrolledWindow (child of a frame).
I can intercept mouse events but the EVT_CHAR is never sent. 
Has anybody experienced this problem?

Quoc Cuong

[wxVTK] Crash with wxVTKRWI as a wxAuiManager pane

[Juha-Ville J. <jul...@gm...>]

Hello,

Not sure if this is the right place to report possible bugs ? Anyways:

I'm using a wxVTKRenderWindowInteractor as a wxAUIManager pane. When trying
to undock the pane I get crash with

...
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 54 error_code 3 request_code 12 minor_code 0)
...

This happens on both GTK2 and MSW versions.

After a bit of debugging I found out that the crash happens on this line in
wxVTKRenderWindowInteractor::UpdateSize(int x, int y):

    RenderWindow->SetSize(x, y);

and only when x = y = 20  !?

Seems that when the undock/drag starts the dragged wxWindow/wxAUI pane is
sets to some minimum size that happens to be 20 and is not taken nicely by
RenderWindow->SetSize ?!

I was able solve this problem by  following temporary hack:

      if (x!=20 && y!=20) RenderWindow->SetSize(x, y);

I'm using wxGTK 2.8.7, wxVTK version is (wxVTKRWI.cxx)
  Date:      $Date: 2008/04/13 22:06:52 $
  Version:   $Revision: 1.35 $

on Gentoo Linux 2.6-22/gcc4.1.2 environment.

cheers
-j

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

[Juha-Ville J. <jul...@gm...>]

Hi,

Tried this, I believe you meant this line in wxVTKRWI.h:

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

After commenting the #define I couldn't see any difference in the behaviour,
not
in original case nor with my paint event -fix.

cheers
-j

2008/4/14, Mathieu Malaterre <mat...@gm...>:
>
> Please CC the wxVTK mailing list, as other might also have seen this
> issue.
>
> Just as a first step, did you try switching the wxGLCanvas to a
> regular wxWindow. You need to edit wxVTKRWI and remove the
>
> #define WX_USEGLCANVAS
>
> I have seen some flickering issue with wxGLCanvas, so...
>
> Anyone else seen this ?
>
> Thanks
> -Mathieu
>
> On Mon, Apr 14, 2008 at 5:58 PM, Juha-Ville Juntunen
>
> <jul...@gm...> wrote:
> > Thanks Mathieu,
> >
> > I'm using wxVTK on both linux and winXP and we might even port our app
> to OS
> > X at some point, so
> > I guess this makes me a suitable guinea pig for wxVTK testing ;)  And
> I'm
> > happy to try out new versions of wxVTK in our environments when ever
> > available.
> >
> > Btw. I found another small weirdness in GTK version and this one does
> not
> > happen on windows:
> >
> > Apparently screen refreshing does not go right in GTK version because
> simply
> > calling wxWindows::Refresh() on the wxVTKRenderWindowInteractor leaves
> the
> > GL canvas blank.
> >  Or it looks more like the GL content is first drawn and then the
> wxWidgets
> > container paints it over with the background color.
> >
> > This behaviour can be also seen with the wxSample app: when started the
> > screen is blank until user clicks the screen with mouse. Also, if user
> > switches between windows (e.g. alt-TAB) so that wxSample gets hidden and
> > then exposed/activated again the window is blank. Some times the content
> > (the cone) flashes in just for fraction of second before its painted
> over,
> > and this makes me believe it's overdrawn by the background colour by
> > wxWidgets.
> >
> > I got this problem fixed by explicitly throwing wxPaintEvent to
> > wxVTKrenderWindowInteractor when ever I need to refresh the VTK image.
> This
> > behgaviour can be seen in the Sample.cpp this by adding handler for
> > wxFocusEvent with following implementation:
> >
> > void MyFrame::OnFocus(wxFocusEvent&event)
> > {
> >    wxPaintEvent e;
> >    m_pVTKWindow->GetEventHandler()->AddPendingEvent(e);
> >
> >    // if above line is commented and following uncommented
> >    // screen refreshing does not work anymore
> >     //m_pVTKWindow->Refresh();
> > }
> >
> > I.e. with above implementation wxVTK screen gets correctly drawn when
> ever
> > mouse is moved over it. And if the Refresh() is used instead of
> > AddPendindgEvent() above,  the wxVTK gets erased when ever mouse is
> moved
> > out and back over the wxVTK window.
> >
> > Not sure, however, if this one is bug or just a feature ?
> >
> > cheers
> > -j
> >
> >
> >
> >
> > 2008/4/14, Mathieu Malaterre <mat...@gm...>:
> >
> > > Hello,
> > >
> > > On Mon, Apr 14, 2008 at 4:25 PM, Juha-Ville Juntunen
> > > <jul...@gm...> wrote:
> > > > Hi Mathieu,
> > > >
> > > > Tried HEAD version on Gentoo with wxSample and the problem is still
> > there.
> > > >
> > > > Btw. I noticed
> > > >
> > > >      this->SetFocus()
> > > >
> > > > added into OnButtonDown(event) method, but it's #ifdefine'd only for
> Mac
> > OSX
> > > > and Windows. If I take those #ifdefines out, behaviour changes a
> bit:I
> > still
> > > > don't get keyboard events caught by wxVTK when I enter the wxSample
> > window,
> > > > but after I click the window keyevents are caught. Is there reason
> > > > SetFocus() is not meant to be  invoked on linux ?
> > >
> > > Simply because you are the first person to have this issue :)
> > > Well it looks like the patch was not tested under linux, or at least
> > > not under your specific configuration. I am pretty sure this is again
> > > a GTK 1.X vs GTK 2.x problem. I'll add the SetFocus for everybody, and
> > > hope that someone complains back if I broke anything :)
> > >
> > > Thanks again for your time, your feedback is extremely important, as I
> > > cannot test all possible configurations.
> > > --
> > >
> > > Mathieu
> > >
> >
> >
>
>
>
>
> --
>
> Mathieu
>

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

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

Please CC the wxVTK mailing list, as other might also have seen this issue.

Just as a first step, did you try switching the wxGLCanvas to a
regular wxWindow. You need to edit wxVTKRWI and remove the

#define WX_USEGLCANVAS

I have seen some flickering issue with wxGLCanvas, so...

Anyone else seen this ?

Thanks
-Mathieu

On Mon, Apr 14, 2008 at 5:58 PM, Juha-Ville Juntunen
<jul...@gm...> wrote:
> Thanks Mathieu,
>
> I'm using wxVTK on both linux and winXP and we might even port our app to OS
> X at some point, so
> I guess this makes me a suitable guinea pig for wxVTK testing ;)  And I'm
> happy to try out new versions of wxVTK in our environments when ever
> available.
>
> Btw. I found another small weirdness in GTK version and this one does not
> happen on windows:
>
> Apparently screen refreshing does not go right in GTK version because simply
> calling wxWindows::Refresh() on the wxVTKRenderWindowInteractor leaves the
> GL canvas blank.
>  Or it looks more like the GL content is first drawn and then the wxWidgets
> container paints it over with the background color.
>
> This behaviour can be also seen with the wxSample app: when started the
> screen is blank until user clicks the screen with mouse. Also, if user
> switches between windows (e.g. alt-TAB) so that wxSample gets hidden and
> then exposed/activated again the window is blank. Some times the content
> (the cone) flashes in just for fraction of second before its painted over,
> and this makes me believe it's overdrawn by the background colour by
> wxWidgets.
>
> I got this problem fixed by explicitly throwing wxPaintEvent to
> wxVTKrenderWindowInteractor when ever I need to refresh the VTK image. This
> behgaviour can be seen in the Sample.cpp this by adding handler for
> wxFocusEvent with following implementation:
>
> void MyFrame::OnFocus(wxFocusEvent&event)
> {
>    wxPaintEvent e;
>    m_pVTKWindow->GetEventHandler()->AddPendingEvent(e);
>
>    // if above line is commented and following uncommented
>    // screen refreshing does not work anymore
>     //m_pVTKWindow->Refresh();
> }
>
> I.e. with above implementation wxVTK screen gets correctly drawn when ever
> mouse is moved over it. And if the Refresh() is used instead of
> AddPendindgEvent() above,  the wxVTK gets erased when ever mouse is moved
> out and back over the wxVTK window.
>
> Not sure, however, if this one is bug or just a feature ?
>
> cheers
> -j
>
>
>
>
> 2008/4/14, Mathieu Malaterre <mat...@gm...>:
>
> > Hello,
> >
> > On Mon, Apr 14, 2008 at 4:25 PM, Juha-Ville Juntunen
> > <jul...@gm...> wrote:
> > > Hi Mathieu,
> > >
> > > Tried HEAD version on Gentoo with wxSample and the problem is still
> there.
> > >
> > > Btw. I noticed
> > >
> > >      this->SetFocus()
> > >
> > > added into OnButtonDown(event) method, but it's #ifdefine'd only for Mac
> OSX
> > > and Windows. If I take those #ifdefines out, behaviour changes a bit:I
> still
> > > don't get keyboard events caught by wxVTK when I enter the wxSample
> window,
> > > but after I click the window keyevents are caught. Is there reason
> > > SetFocus() is not meant to be  invoked on linux ?
> >
> > Simply because you are the first person to have this issue :)
> > Well it looks like the patch was not tested under linux, or at least
> > not under your specific configuration. I am pretty sure this is again
> > a GTK 1.X vs GTK 2.x problem. I'll add the SetFocus for everybody, and
> > hope that someone complains back if I broke anything :)
> >
> > Thanks again for your time, your feedback is extremely important, as I
> > cannot test all possible configurations.
> > --
> >
> > Mathieu
> >
>
>



-- 
Mathieu

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

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

done thanks.

$ cvs ci -m"BUG: Apparently SetFocus is also needed on linux. Thanks
to Juha-Ville Juntunen for report/patch"
wxVTKRenderWindowInteractor.cxx
Checking in wxVTKRenderWindowInteractor.cxx;
/cvsroot/wxvtk/wxVTK/src/wxVTKRenderWindowInteractor.cxx,v  <--
wxVTKRenderWindowInteractor.cxx
new revision: 1.36; previous revision: 1.35
done

On Mon, Apr 14, 2008 at 4:25 PM, Juha-Ville Juntunen
<jul...@gm...> wrote:
> Hi Mathieu,
>
> Tried HEAD version on Gentoo with wxSample and the problem is still there.
>
> Btw. I noticed
>
>      this->SetFocus()
>
> added into OnButtonDown(event) method, but it's #ifdefine'd only for Mac OSX
> and Windows. If I take those #ifdefines out, behaviour changes a bit:I still
> don't get keyboard events caught by wxVTK when I enter the wxSample window,
> but after I click the window keyevents are caught. Is there reason
> SetFocus() is not meant to be  invoked on linux ?
>
> cheers
> -j
>
> 2008/4/13, Mathieu Malaterre <mat...@gm...>:
>
> > Julle
> >
> >   If you get a chance, could you please try the CVS HEAD version of wxVTK.
> >
> > Thanks
> > -Mathieu
> >
> > On Tue, Apr 8, 2008 at 11:11 PM, Mathieu Malaterre
> > <mat...@gm...> wrote:
> > > Hi there,
> > >
> > >   Is anyone using wx 2.8.7 ? Could anyone confirm the bug ?
> > >
> > >  Thanks
> > >  -Mathieu
> >
> > >
> > >
> > >
> > >
> > >  ---------- Forwarded message ----------
> > >  From: SourceForge.net <no...@so...>
> > >  Date: Wed, Mar 19, 2008 at 4:30 PM
> > >  Subject: [ wxvtk-Bugs-1919659 ] keyboard events not caught
> > >  To: no...@so...
> > >
> > >
> > >  Bugs item #1919659, was opened at 2008-03-19 14:30
> > >   Message generated for change (Tracker Item Submitted) made by Item
> Submitter
> > >   You can respond by visiting:
> > >
> https://sourceforge.net/tracker/?func=detail&atid=669338&aid=1919659&group_id=114757
> > >
> > >   Please note that this message will contain a full copy of the comment
> thread,
> > >   including the initial issue submission, for this request,
> > >   not just the latest update.
> > >   Category: Interface
> > >   Group: v1.0 (example)
> > >   Status: Open
> > >   Resolution: None
> > >   Priority: 5
> > >   Private: No
> > >   Submitted By: JulleJuntunen (jullejuntunen)
> > >   Assigned to: Mathieu Malaterre (malat)
> > >   Summary: keyboard events not caught
> > >
> > >   Initial Comment:
> > >   Hi,
> > >
> > >   Keyboard events are not caught on Gentoo Linux (2.6.22-gentoo-r5)
> > >  using wxWidgets GTK 2.8.7.
> > >   This means VTK keyboard interactions won't work in a wxVTK window.
> > >
> > >   This behaviour can be seen simply by adding a printout as the first
> > >  line in wxVTKRenderWindowInteractor::OnKeyDown() method and then
> > >  running any of the included test applications -> on any keypress the
> > >  OnKeyDown() is not invoked (no printout).
> > >
> > >   Problem seems to be due to not passing keyboard focus to wxVTK
> > >  (wxGLCanvas) window.
> > >
> > >   One simple fix that works for me is to add line
> > >   SetFocus() into method wxVTKRenderWindowInteractor::OnEnter(), i.e.
> > >  when ever the VTK window is entered the keyboard focus is forced to
> > >  this window. Not sure if this works as a general fix, but I guess
> > >  similar thing should be done at least when clicking the window.
> > >
> > >   My wxVTK versions are
> > >
> > >   1.30 for wxVTKRenderWindowInteractor.cxx
> > >   1.16 for wxVTKRenderWindowInteractor.h
> > >
> > >   I've checked this also on windows, with exactly the same results.
> > >
> > >   cheers
> > >   -julle
> > >
> > >   ----------------------------------------------------------------------
> > >
> > >   You can respond by visiting:
> > >
> https://sourceforge.net/tracker/?func=detail&atid=669338&aid=1919659&group_id=114757
> > >
> > >
> > >
> >
> > >  --
> > >  Mathieu
> > >
> >
> >
> >
> > --
> >
> > Mathieu
> >
>
>



-- 
Mathieu

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

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

Hello,

On Mon, Apr 14, 2008 at 4:25 PM, Juha-Ville Juntunen
<jul...@gm...> wrote:
> Hi Mathieu,
>
> Tried HEAD version on Gentoo with wxSample and the problem is still there.
>
> Btw. I noticed
>
>      this->SetFocus()
>
> added into OnButtonDown(event) method, but it's #ifdefine'd only for Mac OSX
> and Windows. If I take those #ifdefines out, behaviour changes a bit:I still
> don't get keyboard events caught by wxVTK when I enter the wxSample window,
> but after I click the window keyevents are caught. Is there reason
> SetFocus() is not meant to be  invoked on linux ?

Simply because you are the first person to have this issue :)
Well it looks like the patch was not tested under linux, or at least
not under your specific configuration. I am pretty sure this is again
a GTK 1.X vs GTK 2.x problem. I'll add the SetFocus for everybody, and
hope that someone complains back if I broke anything :)

Thanks again for your time, your feedback is extremely important, as I
cannot test all possible configurations.
-- 
Mathieu

Re: [wxVTK] Problem with wxVTK and _UNICODE wxwidgets.

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

Hi Mathieu,

Thanks for advices.
I think I made a beginner mistake.
>From the error message I posted, it seems that the linker wasn't able to find the default constructor. So I simply include both wxVTKRenderWindowInteractor.cxx and wxVTKRenderWindowInteractor.h into my project and then everything's perfect fine now.?
PS. There is?no problem incorprate wxVTK with "_UNICODE" built wxWedgets.

Thanks for the great effort on wxVTK.


Cheers mate.
John


-----Original Message-----
From: Mathieu Malaterre <mat...@gm...>
To: joh...@ao...
CC: wxv...@li...
Sent: Sun, 13 Apr 2008 23:23
Subject: Re: [wxVTK] Problem with wxVTK and _UNICODE wxwidgets.



I forgot to mention, can you see the wxVTKRWI cstor symbol when you
load the dll in 'depends'

Thanks
-M
ref: http://www.dependencywalker.com/

On Mon, Apr 14, 2008 at 12:22 AM, Mathieu Malaterre
<mat...@gm...> wrote:
> Hi John,
>
>
>  On Sat, Apr 12, 2008 at 2:10 AM,  <joh...@ao...> wrote:
>  >
>  > Dear All,
>  >
>  >  I am doing a project with wxwidgets, wxVTK and VTK under VISTA and VC9
>  > environment.
>  >  I have several question as follows:
>  >
>  >  1. Does wxVTK support _UNICODE built wxwidgets?
>
>  I would think so. non-UNICODE was my default build at the time.
>
>
>
>  >  2. How can I tell the compiler to use the "non-unicode" build? In my
>  > project under the VISTA and VC9 environment, it seems that the "_UNICODE"
>  > has been defined so it forces me to use unicode version of wxwidgets
>  > otherwise it won't compiled.
>  >
>  >  Using "unicode built" ver. of wxwidgets, everything works fine without
>  > using wxVTK, but if I use wxVTK, the compiler generates error linking
>  > messages as follows.
>  >
>  >  1>------ Build started: Project: wxTRY1, Configuration: Debug Win32 ------
>  >  1>Compiling...
>  >  1>TRYWXMyFrameTRY1.cpp
>  >  1>Compiling...
>  >  1>TRYWxFrameMain.cpp
>  >  1>Linking...
>  >  1>   Creating library C:\TRY1\wxTRY1.lib and object
>  > C:\TRY1\Debug\wxTRY1.exp
>  >  1>TRYWXMyFrameTRY1.obj : error LNK2019: unresolved external symbol 
"public:
>  > __thiscall wxVTKRenderWindowInteractor::wxVTKRenderWindowInteractor(class
>  > wxWindow *,int,class wxPoint const &,class wxSize const &,long,class
>  > wxString const &)"
>  > (??0wxVTKRenderWindowInteractor@@QAE@PAVwxWindow@@HABVwxPoint@@ABVwxSize@@JABVwxString@@@Z)
>  > referenced in function "public: __thiscall
>  > TRYWXMyFrameTRY1::TRYWXMyFrameTRY1(class wxWindow *)"
>  > (??0TRYWXMyFrameTRY1@@QAE@PAVwxWindow@@@Z)
>  >  1>C:\TRY1\Debug\wxTRY1.exe : fatal error LNK1120: 1 unresolved externals
>  >  1>Build log was saved at "file://c:\TRY1\Debug\BuildLog.htm"
>  >  1>wxTRY1 - 2 error(s), 0 warning(s)
>  >  ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped 
==========
>
>  I am not a WIN32 expert, but it seems your linker cannot find the
>  cstor symbol, which would make me think that wxVTKRWI cstor is not
>  exported properly. Are you using wxVTK in your project, are you
>  confident with your setting for the 'declspec( dllexport)' thingy ? If
>  not please read Q2 in the README shipped with wxVTK.
>
>  wxVTK is kindda tricky to build as it relies on two configiuration :
>  the wx one and the VTK ones. Make sure that when you compare your
>  wx-unicode and wx-non-unicode you are also confident there are no
>  other differences (VTK version, compiler flags...).
>
>
>  >
>  >  I have tried to build the whole wxVTK project and samples with 
"non-uncode"
>  > ver. of wxwidgets, everything's fine, but if I use "unicode" version, the
>  > compiler generates similar linking error like in my project.
>
>  I do not like the word 'similar', but I'll assume you are correct, and
>  did not mislead two different linker errors. Again see Q2 for my
>  suspicion.
>
>
>  >  How should I solve this problem?
>  >  PS. I am sure that there's no "_UNICODE" in my IDE's pre-processor 
setting.
>  >
>  >  Environment: vc9, vista 32, wxwidgets 2.8.7, wxVTK 1.2, vtk 5.1x and all
>  > compiled under vc9
>
>  If anything else works, give CVS HEAD a shot:
>
>  http://sourceforge.net/cvs/?group_id=114757
>
>  ->  cvs -d:pserver:ano...@wx...:/cvsroot/wxvtk login
>    ->  cvs -z3 -d:pserver:ano...@wx...:/cvsroot/wxvtk
>  co -P wxVTK
>
>
>  HTH
>  --
>  Mathieu
>



-- 
Mathieu


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

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

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

Julle

  If you get a chance, could you please try the CVS HEAD version of wxVTK.

Thanks
-Mathieu

On Tue, Apr 8, 2008 at 11:11 PM, Mathieu Malaterre
<mat...@gm...> wrote:
> Hi there,
>
>   Is anyone using wx 2.8.7 ? Could anyone confirm the bug ?
>
>  Thanks
>  -Mathieu
>
>
>
>
>  ---------- Forwarded message ----------
>  From: SourceForge.net <no...@so...>
>  Date: Wed, Mar 19, 2008 at 4:30 PM
>  Subject: [ wxvtk-Bugs-1919659 ] keyboard events not caught
>  To: no...@so...
>
>
>  Bugs item #1919659, was opened at 2008-03-19 14:30
>   Message generated for change (Tracker Item Submitted) made by Item Submitter
>   You can respond by visiting:
>   https://sourceforge.net/tracker/?func=detail&atid=669338&aid=1919659&group_id=114757
>
>   Please note that this message will contain a full copy of the comment thread,
>   including the initial issue submission, for this request,
>   not just the latest update.
>   Category: Interface
>   Group: v1.0 (example)
>   Status: Open
>   Resolution: None
>   Priority: 5
>   Private: No
>   Submitted By: JulleJuntunen (jullejuntunen)
>   Assigned to: Mathieu Malaterre (malat)
>   Summary: keyboard events not caught
>
>   Initial Comment:
>   Hi,
>
>   Keyboard events are not caught on Gentoo Linux (2.6.22-gentoo-r5)
>  using wxWidgets GTK 2.8.7.
>   This means VTK keyboard interactions won't work in a wxVTK window.
>
>   This behaviour can be seen simply by adding a printout as the first
>  line in wxVTKRenderWindowInteractor::OnKeyDown() method and then
>  running any of the included test applications -> on any keypress the
>  OnKeyDown() is not invoked (no printout).
>
>   Problem seems to be due to not passing keyboard focus to wxVTK
>  (wxGLCanvas) window.
>
>   One simple fix that works for me is to add line
>   SetFocus() into method wxVTKRenderWindowInteractor::OnEnter(), i.e.
>  when ever the VTK window is entered the keyboard focus is forced to
>  this window. Not sure if this works as a general fix, but I guess
>  similar thing should be done at least when clicking the window.
>
>   My wxVTK versions are
>
>   1.30 for wxVTKRenderWindowInteractor.cxx
>   1.16 for wxVTKRenderWindowInteractor.h
>
>   I've checked this also on windows, with exactly the same results.
>
>   cheers
>   -julle
>
>   ----------------------------------------------------------------------
>
>   You can respond by visiting:
>   https://sourceforge.net/tracker/?func=detail&atid=669338&aid=1919659&group_id=114757
>
>
>
>  --
>  Mathieu
>



-- 
Mathieu

Re: [wxVTK] Problem with wxVTK and _UNICODE wxwidgets.

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

I forgot to mention, can you see the wxVTKRWI cstor symbol when you
load the dll in 'depends'

Thanks
-M
ref: http://www.dependencywalker.com/

On Mon, Apr 14, 2008 at 12:22 AM, Mathieu Malaterre
<mat...@gm...> wrote:
> Hi John,
>
>
>  On Sat, Apr 12, 2008 at 2:10 AM,  <joh...@ao...> wrote:
>  >
>  > Dear All,
>  >
>  >  I am doing a project with wxwidgets, wxVTK and VTK under VISTA and VC9
>  > environment.
>  >  I have several question as follows:
>  >
>  >  1. Does wxVTK support _UNICODE built wxwidgets?
>
>  I would think so. non-UNICODE was my default build at the time.
>
>
>
>  >  2. How can I tell the compiler to use the "non-unicode" build? In my
>  > project under the VISTA and VC9 environment, it seems that the "_UNICODE"
>  > has been defined so it forces me to use unicode version of wxwidgets
>  > otherwise it won't compiled.
>  >
>  >  Using "unicode built" ver. of wxwidgets, everything works fine without
>  > using wxVTK, but if I use wxVTK, the compiler generates error linking
>  > messages as follows.
>  >
>  >  1>------ Build started: Project: wxTRY1, Configuration: Debug Win32 ------
>  >  1>Compiling...
>  >  1>TRYWXMyFrameTRY1.cpp
>  >  1>Compiling...
>  >  1>TRYWxFrameMain.cpp
>  >  1>Linking...
>  >  1>   Creating library C:\TRY1\wxTRY1.lib and object
>  > C:\TRY1\Debug\wxTRY1.exp
>  >  1>TRYWXMyFrameTRY1.obj : error LNK2019: unresolved external symbol "public:
>  > __thiscall wxVTKRenderWindowInteractor::wxVTKRenderWindowInteractor(class
>  > wxWindow *,int,class wxPoint const &,class wxSize const &,long,class
>  > wxString const &)"
>  > (??0wxVTKRenderWindowInteractor@@QAE@PAVwxWindow@@HABVwxPoint@@ABVwxSize@@JABVwxString@@@Z)
>  > referenced in function "public: __thiscall
>  > TRYWXMyFrameTRY1::TRYWXMyFrameTRY1(class wxWindow *)"
>  > (??0TRYWXMyFrameTRY1@@QAE@PAVwxWindow@@@Z)
>  >  1>C:\TRY1\Debug\wxTRY1.exe : fatal error LNK1120: 1 unresolved externals
>  >  1>Build log was saved at "file://c:\TRY1\Debug\BuildLog.htm"
>  >  1>wxTRY1 - 2 error(s), 0 warning(s)
>  >  ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
>
>  I am not a WIN32 expert, but it seems your linker cannot find the
>  cstor symbol, which would make me think that wxVTKRWI cstor is not
>  exported properly. Are you using wxVTK in your project, are you
>  confident with your setting for the 'declspec( dllexport)' thingy ? If
>  not please read Q2 in the README shipped with wxVTK.
>
>  wxVTK is kindda tricky to build as it relies on two configiuration :
>  the wx one and the VTK ones. Make sure that when you compare your
>  wx-unicode and wx-non-unicode you are also confident there are no
>  other differences (VTK version, compiler flags...).
>
>
>  >
>  >  I have tried to build the whole wxVTK project and samples with "non-uncode"
>  > ver. of wxwidgets, everything's fine, but if I use "unicode" version, the
>  > compiler generates similar linking error like in my project.
>
>  I do not like the word 'similar', but I'll assume you are correct, and
>  did not mislead two different linker errors. Again see Q2 for my
>  suspicion.
>
>
>  >  How should I solve this problem?
>  >  PS. I am sure that there's no "_UNICODE" in my IDE's pre-processor setting.
>  >
>  >  Environment: vc9, vista 32, wxwidgets 2.8.7, wxVTK 1.2, vtk 5.1x and all
>  > compiled under vc9
>
>  If anything else works, give CVS HEAD a shot:
>
>  http://sourceforge.net/cvs/?group_id=114757
>
>  ->  cvs -d:pserver:ano...@wx...:/cvsroot/wxvtk login
>    ->  cvs -z3 -d:pserver:ano...@wx...:/cvsroot/wxvtk
>  co -P wxVTK
>
>
>  HTH
>  --
>  Mathieu
>



-- 
Mathieu

Re: [wxVTK] Problem with wxVTK and _UNICODE wxwidgets.

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

Hi John,

On Sat, Apr 12, 2008 at 2:10 AM,  <joh...@ao...> wrote:
>
> Dear All,
>
>  I am doing a project with wxwidgets, wxVTK and VTK under VISTA and VC9
> environment.
>  I have several question as follows:
>
>  1. Does wxVTK support _UNICODE built wxwidgets?

I would think so. non-UNICODE was my default build at the time.

>  2. How can I tell the compiler to use the "non-unicode" build? In my
> project under the VISTA and VC9 environment, it seems that the "_UNICODE"
> has been defined so it forces me to use unicode version of wxwidgets
> otherwise it won't compiled.
>
>  Using "unicode built" ver. of wxwidgets, everything works fine without
> using wxVTK, but if I use wxVTK, the compiler generates error linking
> messages as follows.
>
>  1>------ Build started: Project: wxTRY1, Configuration: Debug Win32 ------
>  1>Compiling...
>  1>TRYWXMyFrameTRY1.cpp
>  1>Compiling...
>  1>TRYWxFrameMain.cpp
>  1>Linking...
>  1>   Creating library C:\TRY1\wxTRY1.lib and object
> C:\TRY1\Debug\wxTRY1.exp
>  1>TRYWXMyFrameTRY1.obj : error LNK2019: unresolved external symbol "public:
> __thiscall wxVTKRenderWindowInteractor::wxVTKRenderWindowInteractor(class
> wxWindow *,int,class wxPoint const &,class wxSize const &,long,class
> wxString const &)"
> (??0wxVTKRenderWindowInteractor@@QAE@PAVwxWindow@@HABVwxPoint@@ABVwxSize@@JABVwxString@@@Z)
> referenced in function "public: __thiscall
> TRYWXMyFrameTRY1::TRYWXMyFrameTRY1(class wxWindow *)"
> (??0TRYWXMyFrameTRY1@@QAE@PAVwxWindow@@@Z)
>  1>C:\TRY1\Debug\wxTRY1.exe : fatal error LNK1120: 1 unresolved externals
>  1>Build log was saved at "file://c:\TRY1\Debug\BuildLog.htm"
>  1>wxTRY1 - 2 error(s), 0 warning(s)
>  ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

I am not a WIN32 expert, but it seems your linker cannot find the
cstor symbol, which would make me think that wxVTKRWI cstor is not
exported properly. Are you using wxVTK in your project, are you
confident with your setting for the 'declspec( dllexport)' thingy ? If
not please read Q2 in the README shipped with wxVTK.

wxVTK is kindda tricky to build as it relies on two configiuration :
the wx one and the VTK ones. Make sure that when you compare your
wx-unicode and wx-non-unicode you are also confident there are no
other differences (VTK version, compiler flags...).

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

I do not like the word 'similar', but I'll assume you are correct, and
did not mislead two different linker errors. Again see Q2 for my
suspicion.

>  How should I solve this problem?
>  PS. I am sure that there's no "_UNICODE" in my IDE's pre-processor setting.
>
>  Environment: vc9, vista 32, wxwidgets 2.8.7, wxVTK 1.2, vtk 5.1x and all
> compiled under vc9

If anything else works, give CVS HEAD a shot:

http://sourceforge.net/cvs/?group_id=114757

->  cvs -d:pserver:ano...@wx...:/cvsroot/wxvtk login
   ->  cvs -z3 -d:pserver:ano...@wx...:/cvsroot/wxvtk
co -P wxVTK


HTH
-- 
Mathieu

[wxVTK] Next wxVTK release & cmake 2.6.0

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

Hi there,

  For the next wxVTK release I'd like to bump up the cmake version
required. I'd like to set it to cmake 2.6.0 (I know this is not out
*yet*). Is there anyone still wishing to have a support for older
2.4.x release ? If so, please explain why.

Thanks
-- 
Mathieu
Ps: I am only talking about the CMakeLists.txt shipped with wxVTK,
there are no such restriction when it comes to compiling wxVTKRWI.cxx.
Using cmake 2.6.0 would -hopefully- makes my life much easier. But
-again- you are free to use the wxVTKRWI source code directly into
your project.