wxvtk-users Mailing List for wxVTKRenderWindowInteractor (Page 7)
Brought to you by:
malat
Menu
▾
▴
wxvtk-users — wxVTK users
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(7) |
Feb
|
Mar
(2) |
Apr
(12) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(13) |
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
(6) |
Jul
(3) |
Aug
(11) |
Sep
|
Oct
(10) |
Nov
(2) |
Dec
(1) |
| 2007 |
Jan
(16) |
Feb
(9) |
Mar
(13) |
Apr
|
May
(7) |
Jun
(8) |
Jul
|
Aug
(14) |
Sep
|
Oct
(6) |
Nov
|
Dec
(1) |
| 2008 |
Jan
(20) |
Feb
(1) |
Mar
|
Apr
(20) |
May
(5) |
Jun
(11) |
Jul
|
Aug
(52) |
Sep
(2) |
Oct
(35) |
Nov
(7) |
Dec
(14) |
| 2009 |
Jan
(4) |
Feb
(5) |
Mar
(9) |
Apr
(19) |
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(5) |
Dec
|
| 2010 |
Jan
(1) |
Feb
(5) |
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
(13) |
| 2012 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(9) |
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
|
From: Quoc C. P. <quo...@ce...> - 2008-08-25 13:45:43
|
Here is the valgrind output :
Gdk-ERROR **: The program 'auidemo' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 7 error_code 3 request_code 2 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
/usr/libexec/auidemo: No such file or directory.
145 m_syswrap/syscall-amd64-linux.S: No such file or directory.
Asked for position 0 of stack, stack only has 0 elements on it.
Asked for position 0 of stack, stack only has 0 elements on it.
Asked for position 0 of stack, stack only has 0 elements on it.
--10071-- Discarding syms at 0x10243000-0x10446000 in
/usr/lib64/gconv/ISO8859-1.so due to munmap()
--10071-- Discarding syms at 0xF2FE000-0xF501000 in
/usr/lib64/gconv/UTF-32.so due to munmap()
--10071-- Discarding syms at 0xF519000-0xF724000 in
/lib64/libnss_files-2.7.so due to munmap()
==10071==
==10071== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 5 from 1)
==10071==
==10071== 1 errors in context 1 of 1:
==10071== Syscall param writev(vector[...]) points to uninitialised byte(s)
==10071== at 0x39EACCD89C: writev (in /lib64/libc-2.7.so)
==10071== by 0x39EC408A81: (within /usr/lib64/libxcb.so.1.0.0)
==10071== by 0x39EC408F9A: (within /usr/lib64/libxcb.so.1.0.0)
==10071== by 0x39EC4090CA: (within /usr/lib64/libxcb.so.1.0.0)
==10071== by 0x39EC40919E: xcb_flush (in /usr/lib64/libxcb.so.1.0.0)
==10071== by 0x39EC84AE26: _XSend (in /usr/lib64/libX11.so.6.2.0)
==10071== by 0x39F5822244: (within /usr/lib64/libGL.so.1.2)
==10071== by 0x39F58261A5: (within /usr/lib64/libGL.so.1.2)
==10071== by 0x39F582714E: (within /usr/lib64/libGL.so.1.2)
==10071== by 0x89787FF:
vtkOpenGLPolyDataMapper::RenderPiece(vtkRenderer*, vtkActor*) (in
/usr/local/share/CEA/lcviExtern/vtk50/lib/libvtkRendering.so.5.0.4)
==10071== by 0x88EE851: vtkPolyDataMapper::Render(vtkRenderer*,
vtkActor*) (in
/usr/local/share/CEA/lcviExtern/vtk50/lib/libvtkRendering.so.5.0.4)
==10071== by 0x8959F43: vtkOpenGLActor::Render(vtkRenderer*,
vtkMapper*) (in
/usr/local/share/CEA/lcviExtern/vtk50/lib/libvtkRendering.so.5.0.4)
==10071== Address 0x1164C361 is 5,417 bytes inside a block of size
8,680 alloc'd
==10071== at 0x4A04D1F: calloc (vg_replace_malloc.c:279)
==10071== by 0x39EC408C4E: xcb_connect_to_fd (in
/usr/lib64/libxcb.so.1.0.0)
==10071== by 0x39EC40B002: xcb_connect (in /usr/lib64/libxcb.so.1.0.0)
==10071== by 0x39EC84A3EB: _XConnectXCB (in /usr/lib64/libX11.so.6.2.0)
==10071== by 0x39EC8335B5: XOpenDisplay (in /usr/lib64/libX11.so.6.2.0)
==10071== by 0x899FEF4: vtkXOpenGLRenderWindow::WindowInitialize()
(in /usr/local/share/CEA/lcviExtern/vtk50/lib/libvtkRendering.so.5.0.4)
==10071== by 0x899CD1C: vtkXOpenGLRenderWindow::Initialize() (in
/usr/local/share/CEA/lcviExtern/vtk50/lib/libvtkRendering.so.5.0.4)
==10071== by 0x899CE42: vtkXOpenGLRenderWindow::Start() (in
/usr/local/share/CEA/lcviExtern/vtk50/lib/libvtkRendering.so.5.0.4)
==10071== by 0x890102F: vtkRenderWindow::DoStereoRender() (in
/usr/local/share/CEA/lcviExtern/vtk50/lib/libvtkRendering.so.5.0.4)
==10071== by 0x8901622: vtkRenderWindow::DoFDRender() (in
/usr/local/share/CEA/lcviExtern/vtk50/lib/libvtkRendering.so.5.0.4)
==10071== by 0x8901DFE: vtkRenderWindow::DoAARender() (in
/usr/local/share/CEA/lcviExtern/vtk50/lib/libvtkRendering.so.5.0.4)
==10071== by 0x89025EE: vtkRenderWindow::Render() (in
/usr/local/share/CEA/lcviExtern/vtk50/lib/libvtkRendering.so.5.0.4)
--10071--
--10071-- supp: 5 dl-hack3
==10071==
==10071== IN SUMMARY: 1 errors from 1 contexts (suppressed: 5 from 1)
==10071==
==10071== malloc/free: in use at exit: 3,349,298 bytes in 22,782 blocks.
==10071== malloc/free: 106,158 allocs, 83,376 frees, 34,453,538 bytes
allocated.
==10071==
==10071== searching for pointers to 22,782 not-freed blocks.
==10071== checked 5,689,632 bytes.
==10071==
==10071== LEAK SUMMARY:
==10071== definitely lost: 92,830 bytes in 1,830 blocks.
==10071== possibly lost: 145,620 bytes in 253 blocks.
==10071== still reachable: 3,110,848 bytes in 20,699 blocks.
==10071== suppressed: 0 bytes in 0 blocks.
==10071== Rerun with --leak-check=full to see details of leaked memory.
--10071-- memcheck: sanity checks: 444 cheap, 18 expensive
--10071-- memcheck: auxmaps: 1773 auxmap entries (113472k, 110M) in use
--10071-- memcheck: auxmaps: 48127738 searches, 338798389 comparisons
--10071-- memcheck: SMs: n_issued = 325 (5200k, 5M)
--10071-- memcheck: SMs: n_deissued = 2 (32k, 0M)
--10071-- memcheck: SMs: max_noaccess = 524287 (8388592k, 8191M)
--10071-- memcheck: SMs: max_undefined = 6 (96k, 0M)
--10071-- memcheck: SMs: max_defined = 4763 (76208k, 74M)
--10071-- memcheck: SMs: max_non_DSM = 324 (5184k, 5M)
--10071-- memcheck: max sec V bit nodes: 3051 (262k, 0M)
--10071-- memcheck: set_sec_vbits8 calls: 13006 (new: 3051, updates: 9955)
--10071-- memcheck: max shadow mem size: 9590k, 9M
--10071-- translate: fast SP updates identified: 95,864 ( 86.4%)
--10071-- translate: generic_known SP updates identified: 9,261 ( 8.3%)
--10071-- translate: generic_unknown SP updates identified: 5,719 ( 5.1%)
--10071-- tt/tc: 382,485 tt lookups requiring 1,427,979 probes
--10071-- tt/tc: 382,485 fast-cache updates, 9 flushes
--10071-- transtab: new 82,506 (2,106,703 -> 38,234,918; ratio
181:10) [0 scs]
--10071-- transtab: dumped 0 (0 -> ??)
--10071-- transtab: discarded 188 (3,842 -> ??)
--10071-- scheduler: 44,512,761 jumps (bb entries).
--10071-- scheduler: 444/458,730 major/minor sched events.
--10071-- sanity: 445 cheap, 18 expensive checks.
--10071-- exectx: 30,011 lists, 18,200 contexts (avg 0 per list)
--10071-- exectx: 187,711 searches, 175,866 full compares (936 per 1000)
--10071-- exectx: 0 cmp2, 10 cmp4, 0 cmpAll
I am sorry I am not very familiar with valgrind, it seems that the error
is related to a call to vtkRenderWindow::Render()
but I don't know how to interpret this output...
Quoc Cuong
Mathieu Malaterre a écrit :
> Hi Quoc Cuong,
>
> On Mon, Aug 25, 2008 at 1:48 PM, Quoc Cuong PHAM <quo...@ce...> wrote:
>
>> this->Hide();
>>
>> before the line:
>> m_pVTKWindow = new wxVTKRenderWindowInteractor(this, MY_VTK_WINDOW, pos,
>> size)
>>
>> because I use wxGLCanvas
>>
>
> wow ! I do not know how I can patch wxVTK to support that ...
>
>
>> - a second error occurs when the wxVTKRenderWindowInteractor::UpdateSize()
>> is called with the same size as the initial size (at the creation
>> wxVTKRenderWindowInteractor)
>> if I do
>> void FrameGL::OnSize(wxSizeEvent& event)
>> {
>> cout<<"FrameGL::OnSize()"<<endl;
>> wxSize size = event.GetSize();
>> // cout<<"change size = "<< size.GetWidth() <<" "<< size.GetHeight() <<
>> endl;
>> if (size!= this->initialSize)
>>
>
> That seems a resonable patch. Thanks.
>
>
>
>> - then the application does not crash in UpdateSize() anymore but further,
>> in the reparent section of the Render() as I mentioned in my first email
>>
>> else if(GetHandleHack())
>> {
>> //this means the user has reparented us; let's adapt to the
>> //new situation by doing the WindowRemap dance
>> //store the new situation
>> Handle = GetHandleHack();
>> cout<<"Handle (reparent)= "<< Handle << endl;
>> RenderWindow->SetNextWindowId(reinterpret_cast<void *>(Handle)); //
>> CRASH HERE !!!!
>>
>
>
> no the crash cannot happen here.
>
> RenderWindow is a valid pointer and Handle is simply an integer, on
> linux you can always cast an integer to a void* pointer. So the bug
> must appear somewhere before.
>
> On your linux station, please install valgrind, and start you
> application this ways:
>
> $ valgrind -v ./aui-sample
>
> (replace aui-sample with whatever the name of your app is). Then send
> us back the valgrind output, or study it, it is fairly easy to read.
>
> HTH
>
--
Quoc Cuong PHAM
==
CEA LIST
Laboratoire Systèmes de Vision Embarqués
DRT/LIST/DTSI/SARC/LSVE
Centre de Saclay Bat 528
91191 Gif-sur-Yvette France
Phone : +33 1 69 08 82 98
Fax : +33 1 69 08 83 95
e-mail : quo...@ce...
|
|
From: Mathieu M. <mat...@gm...> - 2008-08-25 12:03:11
|
Hi Quoc Cuong,
On Mon, Aug 25, 2008 at 1:48 PM, Quoc Cuong PHAM <quo...@ce...> wrote:
> this->Hide();
>
> before the line:
> m_pVTKWindow = new wxVTKRenderWindowInteractor(this, MY_VTK_WINDOW, pos,
> size)
>
> because I use wxGLCanvas
wow ! I do not know how I can patch wxVTK to support that ...
> - a second error occurs when the wxVTKRenderWindowInteractor::UpdateSize()
> is called with the same size as the initial size (at the creation
> wxVTKRenderWindowInteractor)
> if I do
> void FrameGL::OnSize(wxSizeEvent& event)
> {
> cout<<"FrameGL::OnSize()"<<endl;
> wxSize size = event.GetSize();
> // cout<<"change size = "<< size.GetWidth() <<" "<< size.GetHeight() <<
> endl;
> if (size!= this->initialSize)
That seems a resonable patch. Thanks.
> - then the application does not crash in UpdateSize() anymore but further,
> in the reparent section of the Render() as I mentioned in my first email
>
> else if(GetHandleHack())
> {
> //this means the user has reparented us; let's adapt to the
> //new situation by doing the WindowRemap dance
> //store the new situation
> Handle = GetHandleHack();
> cout<<"Handle (reparent)= "<< Handle << endl;
> RenderWindow->SetNextWindowId(reinterpret_cast<void *>(Handle)); //
> CRASH HERE !!!!
no the crash cannot happen here.
RenderWindow is a valid pointer and Handle is simply an integer, on
linux you can always cast an integer to a void* pointer. So the bug
must appear somewhere before.
On your linux station, please install valgrind, and start you
application this ways:
$ valgrind -v ./aui-sample
(replace aui-sample with whatever the name of your app is). Then send
us back the valgrind output, or study it, it is fairly easy to read.
HTH
--
Mathieu
|
|
From: Mathieu M. <mat...@gm...> - 2008-08-25 09:32:20
|
On Mon, Aug 25, 2008 at 2:46 AM, Doug McCorkle <mc...@ia...> wrote: > > On Aug 24, 2008, at 6:53 PM, Mathieu Malaterre wrote: > >> Doug, >> >> I am getting lost with all the emails. I do not have access to a >> MacOSX system, so please bare with me a little more :) >> >> So far we have: >> 1. You have properly configured / build installed wxCocoa port (please >> send the cmd line you used to configure wx) > > I built wxMac which I believe uses Carbon. > >> >> 2. the wxGLCanvas examples seems to be working for you for Cocoa > > I believe this is using Carbon. > >> >> 3. Even setting both the view and window for Cocoa to display in is >> not enough (send your copy of wxVTK, or type 'cvs di' and send the >> diff). > > I would like to figure out if I am building what is needed for wxVTK > properly. A couple of people are using VTK Carbon + wxVTK on MacOSX, AFAIK it should work out of the box. Build VTK with carbon on, and wx with carbon on. HTH -- Mathieu |
|
From: Mathieu M. <mat...@gm...> - 2008-08-25 09:30:49
|
On Mon, Aug 25, 2008 at 2:42 AM, Doug McCorkle <mc...@ia...> wrote: > OK. What are the instructions for building wxVTK on Mac OS? Since wxWidgets > does not have a stable cocoa build yet does VTK have to be compiled to use > Carbon? yes -- Mathieu |
|
From: Doug M. <mc...@ia...> - 2008-08-25 00:46:37
|
On Aug 24, 2008, at 6:53 PM, Mathieu Malaterre wrote: > Doug, > > I am getting lost with all the emails. I do not have access to a > MacOSX system, so please bare with me a little more :) > > So far we have: > 1. You have properly configured / build installed wxCocoa port (please > send the cmd line you used to configure wx) I built wxMac which I believe uses Carbon. > > 2. the wxGLCanvas examples seems to be working for you for Cocoa I believe this is using Carbon. > > 3. Even setting both the view and window for Cocoa to display in is > not enough (send your copy of wxVTK, or type 'cvs di' and send the > diff). I would like to figure out if I am building what is needed for wxVTK properly. Doug |
|
From: Doug M. <mc...@ia...> - 2008-08-25 00:42:53
|
On Aug 24, 2008, at 7:04 PM, Mathieu Malaterre wrote: > On Fri, Aug 15, 2008 at 12:04 AM, Doug McCorkle <mc...@ia...> > wrote: >> And I see two windows which does not seem correct. > > I mean it's not too bad, at least for the second one. That means we > are very close to something working. > > For window #1, I would try to interact with the screen anyway to see > if we are missing a refresh or something (OnSize maybe?) > > For window#2 you can simply not see the data, since you do not have > VTKData and/or setup VTK_DATA_ROOT properly. OK. What are the instructions for building wxVTK on Mac OS? Since wxWidgets does not have a stable cocoa build yet does VTK have to be compiled to use Carbon? Doug |
|
From: Mathieu M. <mat...@gm...> - 2008-08-25 00:28:08
|
Applied:
$ cvs di
Index: wxVTKRenderWindowInteractor.cxx
===================================================================
RCS file: /cvsroot/wxvtk/wxVTK/src/wxVTKRenderWindowInteractor.cxx,v
retrieving revision 1.41
diff -u -r1.41 wxVTKRenderWindowInteractor.cxx
--- wxVTKRenderWindowInteractor.cxx 13 Aug 2008 08:22:58 -0000 1.41
+++ wxVTKRenderWindowInteractor.cxx 25 Aug 2008 00:26:11 -0000
@@ -639,6 +639,9 @@
return;
}
+ // See report by Shang Mu / Keery Lu on wxVTK mailing list
+ this->SetFocus();
+
#if VTK_MAJOR_VERSION > 4 || (VTK_MAJOR_VERSION == 4 && VTK_MINOR_VERSION > 0)
SetEventInformationFlipY(event.GetX(), event.GetY(),
event.ControlDown(), event.ShiftDown(), '\0', 0, NULL);
$ cvs ci -m"ENH: Add SetFocus on OnButtonUp. Thanks to Shang Mu for
patch, Kerry Loux for report."
Checking in wxVTKRenderWindowInteractor.cxx;
/cvsroot/wxvtk/wxVTK/src/wxVTKRenderWindowInteractor.cxx,v <--
wxVTKRenderWindowInteractor.cxx
new revision: 1.42; previous revision: 1.41
done
Thanks !
On Mon, Aug 4, 2008 at 2:58 AM, Kerry Loux <lo...@gm...> wrote:
> I should have waited to try this before sending my previous message because
> it was easy and took < 30 seconds. Shang, your suggestion fixed the problem
> - I added SetFocus(); to the top of the OnButtonUp() function in wxVTK and
> the problem went away. Thanks for the help!
>
> -Kerry
>
> On Sun, Aug 3, 2008 at 8:55 PM, Kerry Loux <lo...@gm...> wrote:
>>
>> I think I'm using wxVTK 1.30 (.cxx file is rev 1.30, .h file is rev 1.16).
>>
>> I have discovered the cause of the middle mouse button not working - it
>> was my fault - the mouse's software configuration does not treat the middle
>> mouse button as a middle mouse button by default. It was set to "zoom"
>> (whatever that is...), but I put it to "middle mouse button" and all is well
>> with the button events.
>>
>> The scroll events, however - this is what I've learned:
>>
>> The OnMouseWheel function in wxVTK is being called when I start the
>> program and move the scroll wheel. I can zoom in and out just fine. After
>> clicking on another control and then back on the wxVTK, the OnMouseWheel
>> function is never called, no matter what direction I scroll the mouse of
>> what combination of key presses and mouse clicks I try.
>>
>> Mathieu, I did implement the bug fix, but since the function isn't being
>> called, it didn't help. I do like the changes it made to the scroll wheel
>> functionality, though. It seems that the "/ event.GetWheelDelta()" was
>> responsible for limiting the "zooming" capability.
>>
>> Shang, I'll try the SetFocus() fix and report back...
>>
>> Thanks for your help!
>>
>> -Kerry
>>
>> On Sun, Aug 3, 2008 at 6:21 PM, Mathieu Malaterre
>> <mat...@gm...> wrote:
>>>
>>> What version of wxVTK are you using ? I cannot remember but I thought
>>> at some point we had an issue with mouse wheel. Anyway, if you can get
>>> wx to recognize mouse wheel event, there would be no reason why we
>>> could not forward them to VTK.
>>>
>>> On a different subject a bug was recently submited:
>>>
>>>
>>> https://sourceforge.net/tracker/?func=detail&atid=669338&aid=2025027&group_id=114757
>>>
>>> donno if this help or not...
>>>
>>> HTH
>>> -Mathieu
>>>
>>> On Sat, Aug 2, 2008 at 1:39 PM, Kerry Loux <lo...@gm...> wrote:
>>> > Hello All,
>>> >
>>> > I've come across a couple of curious bugs that I can't seem to track
>>> > down,
>>> > and they're both related to my middle mouse button. My middle mouse
>>> > button
>>> > up/down events don't fire. I set a breakpoint at the
>>> > wxVTKRenderWindowInteractor OnButtonDown() function and both the right
>>> > and
>>> > left mouse buttons cause the breakpoint to be reached, but I get
>>> > nothing
>>> > from the middle button. Is there something else I need to do to set
>>> > this
>>> > up?
>>> >
>>> > Also, I am having a similar problem with the scroll wheel. When I
>>> > first
>>> > start my app, I can use the scroll wheel just fine, but if I click on
>>> > another control, then click back into the RenderWindow, the scroll
>>> > wheel no
>>> > longer functions. Same deal with the breakpoints - the event handler
>>> > is
>>> > never called.
>>> >
>>> > Any ideas on these? Has anyone else noticed this behavior?
>>> >
>>> > Thanks for your help!
>>> >
>>> > -Kerry
>>> >
>>> >
>>> > -------------------------------------------------------------------------
>>> > 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
>>
>
>
--
Mathieu
|
|
From: Mathieu M. <mat...@gm...> - 2008-08-25 00:04:46
|
On Fri, Aug 15, 2008 at 12:04 AM, Doug McCorkle <mc...@ia...> wrote: > And I see two windows which does not seem correct. I mean it's not too bad, at least for the second one. That means we are very close to something working. For window #1, I would try to interact with the screen anyway to see if we are missing a refresh or something (OnSize maybe?) For window#2 you can simply not see the data, since you do not have VTKData and/or setup VTK_DATA_ROOT properly. -- Mathieu |
|
From: Mathieu M. <mat...@gm...> - 2008-08-24 23:53:46
|
Doug, I am getting lost with all the emails. I do not have access to a MacOSX system, so please bare with me a little more :) So far we have: 1. You have properly configured / build installed wxCocoa port (please send the cmd line you used to configure wx) 2. the wxGLCanvas examples seems to be working for you for Cocoa 3. Even setting both the view and window for Cocoa to display in is not enough (send your copy of wxVTK, or type 'cvs di' and send the diff). Thanks, -- Mathieu |
|
From: Mathieu M. <mat...@gm...> - 2008-08-24 23:32:47
|
Hi Quoc Cuong On Sat, Aug 23, 2008 at 10:27 PM, PHAM Quoc-Cuong 203899 <Quo...@ce...> wrote: > Hi > I use a wxVTKRenderWindowInteractor (1.3 and VTK 5.0.4) in a wxAuiManager pane (wxWidgets 2.8.7) (like in thread http://sourceforge.net/mailarchive/forum.php?thread_name=ba0d923e0804211200o65a12c6dtce4ccbf846bdd8ea%40mail.gmail.com&forum_name=wxvtk-users) Link does not work for me :( > The pane is dockable and when moving the pane, the application crashes with the following error: > > > Gdk-ERROR **: The program 'BaliseDAM' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadWindow (invalid Window parameter)'. > (Details: serial 7 error_code 3 request_code 2 minor_code 0) > (Note to programmers: normally, X errors are reported asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the --sync command line > option to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() function.) > aborting... Yup, I got that one quite a few time when developing wxVTK :) > It appears that the error occurs in the function Render() in the case of reparenting (indeed, wxAuiManager creates a floating frame that becomes the new parent) If I understand what you are syaing we are entering wxVTKRWI::Render() function, then goes to the second if: if ( GetHandleHack() ) But for some reason the value return by GetHandleHack is not a valid window anymore, right ? Can you print the value of those handles ? If you are not making any progress, please send a small example to reproduce the issue. Thanks, -- Mathieu |
|
From: PHAM Quoc-C. 2. <Quo...@ce...> - 2008-08-23 20:27:24
|
Hi I use a wxVTKRenderWindowInteractor (1.3 and VTK 5.0.4) in a wxAuiManager pane (wxWidgets 2.8.7) (like in thread http://sourceforge.net/mailarchive/forum.php?thread_name=ba0d923e0804211200o65a12c6dtce4ccbf846bdd8ea%40mail.gmail.com&forum_name=wxvtk-users) The pane is dockable and when moving the pane, the application crashes with the following error: Gdk-ERROR **: The program 'BaliseDAM' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 7 error_code 3 request_code 2 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... It appears that the error occurs in the function Render() in the case of reparenting (indeed, wxAuiManager creates a floating frame that becomes the new parent) Any idea ? Quoc Cuong |
|
From: Mathieu M. <mat...@gm...> - 2008-08-20 18:21:11
|
Hi vasilis, Yes I got it to work. But as I said in my post, this is a ugly hack. Look at the internal function: GetHandleHack in the wxVTK project: http://wxvtk.sourceforge.net/ There is a mailing list. You should post your question there. HTH 2008/8/20 basOS G <no...@gm...>: > Hello, i realize it's been a long time but a just read a conversation you > had 3 years ago about the internal handle of a GTL window. > (http://thread.gmane.org/gmane.comp.lib.wxwidgets.devel/50669/focus=50693). > Apparenty no functionality is implemented in wxWidgets. SO i ask, if you > have a working code to go from a wxWidget Handle to the XID bellow it. > Just tried > GdkWindow* win = GTK_PIZZA(wxwindow->m_wxwindow)->bin_window; > wxLogDebug(_T("wxVLCBackend::InitGTK Gtkwid=%x, GDKwin=%x, XID=%x"), > output->m_wxwindow, win, GDK_WINDOW_XID(win) ); > > and got [Debug] 08:04:57 μμ: wxVLCBackend::InitGTK Gtkwid=80d1d70, GDKwin=0, > XID=0 > > regards > vasilis > -- Mathieu |
|
From: Doug M. <mc...@ia...> - 2008-08-16 01:47:11
|
On Aug 15, 2008, at 3:11 PM, Mathieu Malaterre wrote: > On Fri, Aug 15, 2008 at 10:08 PM, Nigel Nunn <Nig...@au... > > wrote: >> Mathieu wrote: >> >>> Doug is using the Cocoa port. >> >> As I had hoped. So why the "raised inside Carbon event dispatch"? >> Is Doug's Cocoa port tangled with Carbon? Does Cocoa call Carbon? > > =O > > did not even realized that ! I do know where is thing is coming > from...maybe using something like ktrace would help knowing why carbon > get in the way. I have built wxMac and wxVTK. Not sure what else is needed to debug this. Doug |
|
From: Doug M. <mc...@ia...> - 2008-08-15 20:47:01
|
On Aug 15, 2008, at 2:23 PM, Nigel Nunn wrote: > Hi Doug, > > I've noticed mention of both Carbon and Cocoa. > Which Mac.Mode are you aiming for? > I am only using Cocoa as far as I can tell. Doug |
|
From: Doug M. <mc...@ia...> - 2008-08-15 20:46:07
|
On Aug 15, 2008, at 1:43 PM, Mathieu Malaterre wrote: > Doug, > > On Fri, Aug 15, 2008 at 8:36 PM, Doug McCorkle <mc...@ia...> > wrote: >> >> On Aug 15, 2008, at 12:59 PM, Mathieu Malaterre wrote: >> >>> On Fri, Aug 15, 2008 at 7:49 PM, Doug McCorkle <mc...@ia...> >>> wrote: >>>> >>>> It is aborting before OnPaint is being called: >>> >>> where exactly ? Can you run gdb and send me the backtrace (bt >>> command). >>> >> No need to do that since the abort is in the Render function as >> noted below. > > Ok this means there is something wrong going on. You need to send me > the value returned by GetHandleHack() it is not entering the first > if() but entering the else if() and it does not make sense... > >>> Try wxSample and tell me if you can see the Cone. As shown in the >>> picture (scroll down): >> >> No cone: >> >> leonidas:build mccdo$ ./wxSample.app/Contents/MacOS/wxSample >> 2008-08-15 13:35:20.399 wxSample[50085:10b] *** -[NSHIObject >> userSpaceScaleFactor]: unrecognized selector sent to instance >> 0x3560300 >> 2008-08-15 13:35:20.401 wxSample[50085:10b] HIToolbox: ignoring >> exception >> '*** -[NSHIObject userSpaceScaleFactor]: unrecognized selector sent >> to >> instance 0x3560300' that raised inside Carbon event dispatch > > I remember that wx comes with 3 simple toy examples: cube, penguin and > isosurf. There are OpenGL based app using wx. Do they work on your OS > ? Yes. Doug |
|
From: Mathieu M. <mat...@gm...> - 2008-08-15 20:11:31
|
On Fri, Aug 15, 2008 at 10:08 PM, Nigel Nunn <Nig...@au...> wrote: > Mathieu wrote: > >> Doug is using the Cocoa port. > > As I had hoped. So why the "raised inside Carbon event dispatch"? > Is Doug's Cocoa port tangled with Carbon? Does Cocoa call Carbon? =O did not even realized that ! I do know where is thing is coming from...maybe using something like ktrace would help knowing why carbon get in the way. Nice catch, -- Mathieu |
|
From: Nigel N. <Nig...@au...> - 2008-08-15 20:09:05
|
Mathieu wrote: > Doug is using the Cocoa port. As I had hoped. So why the "raised inside Carbon event dispatch"? Is Doug's Cocoa port tangled with Carbon? Does Cocoa call Carbon? Nigel On Fri, Aug 15, 2008 at 9:23 PM, Nigel Nunn <Nig...@au...> wrote: > Hi Doug, > > I've noticed mention of both Carbon and Cocoa. > Which Mac.Mode are you aiming for? > > Nigel > > > > -----Original Message----- > From: wxv...@li... > [mailto:wxv...@li...]On Behalf Of Doug > McCorkle > Sent: Saturday, 16 August 2008 4:36 AM > To: Mathieu Malaterre > Cc: wxVTK Mail List > Subject: Re: [wxVTK] WindowRemap not implemented (was Re: Problems on > Mac OS 10.5 and wxWidgets 2.8.7) > > > > On Aug 15, 2008, at 12:59 PM, Mathieu Malaterre wrote: > >> On Fri, Aug 15, 2008 at 7:49 PM, Doug McCorkle <mc...@ia...> >> wrote: >>> It is aborting before OnPaint is being called: >> >> where exactly ? Can you run gdb and send me the backtrace (bt >> command). >> > No need to do that since the abort is in the Render function as noted > below. > >>> leonidas:build mccdo$ ./wxImagePlaneWidget.app/Contents/MacOS/ >>> wxImagePlaneWidget >>> ERROR: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/IO/ >>> vtkVolume16Reader.cxx, line 355 >>> vtkVolume16Reader (0x356ffb0): Can't find file: ../../../../VTKData/ >>> Data/headsq/quarter.1 >>> >>> going to abort >>> >>> I am not worried about the VTK data stuff for now. I can download and >>> get that working later. >> >> sure. Then do not use an example that required VTKData. Instead use >> wxSample. >> >>> What would you like to try next? >> >> Try wxSample and tell me if you can see the Cone. As shown in the >> picture (scroll down): > > No cone: > > leonidas:build mccdo$ ./wxSample.app/Contents/MacOS/wxSample > 2008-08-15 13:35:20.399 wxSample[50085:10b] *** -[NSHIObject > userSpaceScaleFactor]: unrecognized selector sent to instance 0x3560300 > 2008-08-15 13:35:20.401 wxSample[50085:10b] HIToolbox: ignoring > exception '*** -[NSHIObject userSpaceScaleFactor]: unrecognized > selector sent to instance 0x3560300' that raised inside Carbon event > dispatch > > Doug > > ------------------------------------------------------------------------- ------------------------------------------------------------------------------------- Follow our Beijing success - www.ausport.gov.au/media 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. ------------------------------------------------------------------------------------- |
|
From: Mathieu M. <mat...@gm...> - 2008-08-15 19:58:21
|
Doug is using the Cocoa port. On Fri, Aug 15, 2008 at 9:23 PM, Nigel Nunn <Nig...@au...> wrote: > Hi Doug, > > I've noticed mention of both Carbon and Cocoa. > Which Mac.Mode are you aiming for? > > Nigel > > > > -----Original Message----- > From: wxv...@li... > [mailto:wxv...@li...]On Behalf Of Doug > McCorkle > Sent: Saturday, 16 August 2008 4:36 AM > To: Mathieu Malaterre > Cc: wxVTK Mail List > Subject: Re: [wxVTK] WindowRemap not implemented (was Re: Problems on > Mac OS 10.5 and wxWidgets 2.8.7) > > > > On Aug 15, 2008, at 12:59 PM, Mathieu Malaterre wrote: > >> On Fri, Aug 15, 2008 at 7:49 PM, Doug McCorkle <mc...@ia...> >> wrote: >>> It is aborting before OnPaint is being called: >> >> where exactly ? Can you run gdb and send me the backtrace (bt >> command). >> > No need to do that since the abort is in the Render function as noted > below. > >>> leonidas:build mccdo$ ./wxImagePlaneWidget.app/Contents/MacOS/ >>> wxImagePlaneWidget >>> ERROR: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/IO/ >>> vtkVolume16Reader.cxx, line 355 >>> vtkVolume16Reader (0x356ffb0): Can't find file: ../../../../VTKData/ >>> Data/headsq/quarter.1 >>> >>> going to abort >>> >>> I am not worried about the VTK data stuff for now. I can download and >>> get that working later. >> >> sure. Then do not use an example that required VTKData. Instead use >> wxSample. >> >>> What would you like to try next? >> >> Try wxSample and tell me if you can see the Cone. As shown in the >> picture (scroll down): > > No cone: > > leonidas:build mccdo$ ./wxSample.app/Contents/MacOS/wxSample > 2008-08-15 13:35:20.399 wxSample[50085:10b] *** -[NSHIObject > userSpaceScaleFactor]: unrecognized selector sent to instance 0x3560300 > 2008-08-15 13:35:20.401 wxSample[50085:10b] HIToolbox: ignoring > exception '*** -[NSHIObject userSpaceScaleFactor]: unrecognized > selector sent to instance 0x3560300' that raised inside Carbon event > dispatch > > Doug > > ------------------------------------------------------------------------- > 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 > > ------------------------------------------------------------------------------------- > Follow our Beijing success - www.ausport.gov.au/media > > 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 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 |
|
From: Nigel N. <Nig...@au...> - 2008-08-15 19:23:45
|
Hi Doug, I've noticed mention of both Carbon and Cocoa. Which Mac.Mode are you aiming for? Nigel -----Original Message----- From: wxv...@li... [mailto:wxv...@li...]On Behalf Of Doug McCorkle Sent: Saturday, 16 August 2008 4:36 AM To: Mathieu Malaterre Cc: wxVTK Mail List Subject: Re: [wxVTK] WindowRemap not implemented (was Re: Problems on Mac OS 10.5 and wxWidgets 2.8.7) On Aug 15, 2008, at 12:59 PM, Mathieu Malaterre wrote: > On Fri, Aug 15, 2008 at 7:49 PM, Doug McCorkle <mc...@ia...> > wrote: >> It is aborting before OnPaint is being called: > > where exactly ? Can you run gdb and send me the backtrace (bt > command). > No need to do that since the abort is in the Render function as noted below. >> leonidas:build mccdo$ ./wxImagePlaneWidget.app/Contents/MacOS/ >> wxImagePlaneWidget >> ERROR: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/IO/ >> vtkVolume16Reader.cxx, line 355 >> vtkVolume16Reader (0x356ffb0): Can't find file: ../../../../VTKData/ >> Data/headsq/quarter.1 >> >> going to abort >> >> I am not worried about the VTK data stuff for now. I can download and >> get that working later. > > sure. Then do not use an example that required VTKData. Instead use > wxSample. > >> What would you like to try next? > > Try wxSample and tell me if you can see the Cone. As shown in the > picture (scroll down): No cone: leonidas:build mccdo$ ./wxSample.app/Contents/MacOS/wxSample 2008-08-15 13:35:20.399 wxSample[50085:10b] *** -[NSHIObject userSpaceScaleFactor]: unrecognized selector sent to instance 0x3560300 2008-08-15 13:35:20.401 wxSample[50085:10b] HIToolbox: ignoring exception '*** -[NSHIObject userSpaceScaleFactor]: unrecognized selector sent to instance 0x3560300' that raised inside Carbon event dispatch Doug ------------------------------------------------------------------------- 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 ------------------------------------------------------------------------------------- Follow our Beijing success - www.ausport.gov.au/media 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. ------------------------------------------------------------------------------------- |
|
From: Mathieu M. <mat...@gm...> - 2008-08-15 18:43:53
|
Doug, On Fri, Aug 15, 2008 at 8:36 PM, Doug McCorkle <mc...@ia...> wrote: > > On Aug 15, 2008, at 12:59 PM, Mathieu Malaterre wrote: > >> On Fri, Aug 15, 2008 at 7:49 PM, Doug McCorkle <mc...@ia...> wrote: >>> >>> It is aborting before OnPaint is being called: >> >> where exactly ? Can you run gdb and send me the backtrace (bt command). >> > No need to do that since the abort is in the Render function as noted below. Ok this means there is something wrong going on. You need to send me the value returned by GetHandleHack() it is not entering the first if() but entering the else if() and it does not make sense... >> Try wxSample and tell me if you can see the Cone. As shown in the >> picture (scroll down): > > No cone: > > leonidas:build mccdo$ ./wxSample.app/Contents/MacOS/wxSample > 2008-08-15 13:35:20.399 wxSample[50085:10b] *** -[NSHIObject > userSpaceScaleFactor]: unrecognized selector sent to instance 0x3560300 > 2008-08-15 13:35:20.401 wxSample[50085:10b] HIToolbox: ignoring exception > '*** -[NSHIObject userSpaceScaleFactor]: unrecognized selector sent to > instance 0x3560300' that raised inside Carbon event dispatch I remember that wx comes with 3 simple toy examples: cube, penguin and isosurf. There are OpenGL based app using wx. Do they work on your OS ? Thanks, -- Mathieu |
|
From: Doug M. <mc...@ia...> - 2008-08-15 18:36:29
|
On Aug 15, 2008, at 12:59 PM, Mathieu Malaterre wrote: > On Fri, Aug 15, 2008 at 7:49 PM, Doug McCorkle <mc...@ia...> > wrote: >> It is aborting before OnPaint is being called: > > where exactly ? Can you run gdb and send me the backtrace (bt > command). > No need to do that since the abort is in the Render function as noted below. >> leonidas:build mccdo$ ./wxImagePlaneWidget.app/Contents/MacOS/ >> wxImagePlaneWidget >> ERROR: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/IO/ >> vtkVolume16Reader.cxx, line 355 >> vtkVolume16Reader (0x356ffb0): Can't find file: ../../../../VTKData/ >> Data/headsq/quarter.1 >> >> going to abort >> >> I am not worried about the VTK data stuff for now. I can download and >> get that working later. > > sure. Then do not use an example that required VTKData. Instead use > wxSample. > >> What would you like to try next? > > Try wxSample and tell me if you can see the Cone. As shown in the > picture (scroll down): No cone: leonidas:build mccdo$ ./wxSample.app/Contents/MacOS/wxSample 2008-08-15 13:35:20.399 wxSample[50085:10b] *** -[NSHIObject userSpaceScaleFactor]: unrecognized selector sent to instance 0x3560300 2008-08-15 13:35:20.401 wxSample[50085:10b] HIToolbox: ignoring exception '*** -[NSHIObject userSpaceScaleFactor]: unrecognized selector sent to instance 0x3560300' that raised inside Carbon event dispatch Doug |
|
From: Mathieu M. <mat...@gm...> - 2008-08-15 17:59:05
|
On Fri, Aug 15, 2008 at 7:49 PM, Doug McCorkle <mc...@ia...> wrote: > It is aborting before OnPaint is being called: where exactly ? Can you run gdb and send me the backtrace (bt command). > leonidas:build mccdo$ ./wxImagePlaneWidget.app/Contents/MacOS/ > wxImagePlaneWidget > ERROR: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/IO/ > vtkVolume16Reader.cxx, line 355 > vtkVolume16Reader (0x356ffb0): Can't find file: ../../../../VTKData/ > Data/headsq/quarter.1 > > going to abort > > I am not worried about the VTK data stuff for now. I can download and > get that working later. sure. Then do not use an example that required VTKData. Instead use wxSample. > What would you like to try next? Try wxSample and tell me if you can see the Cone. As shown in the picture (scroll down): http://wxvtk.sourceforge.net/ Thanks -- Mathieu |
|
From: Doug M. <mc...@ia...> - 2008-08-15 17:50:01
|
On Aug 15, 2008, at 3:41 AM, Mathieu Malaterre wrote: > Hi Doug, > > Alright finally some progress ! Don't forget to send me the patch in > the end :) > > On Fri, Aug 15, 2008 at 12:04 AM, Doug McCorkle <mc...@ia...> > wrote: >> I got everything built now. I just told cmake to use the 10.5 sdk >> not the >> 10.4. Anyway, I now get this when running a sample: >> >> leonidas:build mccdo$ >> ./wxImagePlaneWidget.app/Contents/MacOS/wxImagePlaneWidget >> ERROR: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/IO/ >> vtkVolume16Reader.cxx, >> line 355 >> vtkVolume16Reader (0x3571a00): Can't find file: >> ../../../../VTKData/Data/headsq/quarter.1 > > I do not think I implemented the -D command line option, so you have > to do: > > export VTK_DATA_ROOT=/Volumes/data/VE_Suite_Deps/VTK_new/VTKData > > If you do not have VTKData, download it from the vtk.org page (you > can do it from CVS command line by replace VTK with VTKData) > > >> Warning: In >> /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/ >> vtkCocoaRenderWindow.h, >> line 138 >> vtkCocoaRenderWindow (0x35716c0): SetNextWindowId not implemented >> (WindowRemap not implemented). > > ouch ! > >> Warning: In >> /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/ >> vtkCocoaRenderWindow.mm, >> line 813 >> vtkCocoaRenderWindow (0x35716c0): Can't remap the window. > > ouch 2 ! > >> 2008-08-14 17:01:02.903 wxImagePlaneWidget[47823:10b] invalid >> drawable >> 2008-08-14 17:01:02.938 wxImagePlaneWidget[47823:10b] invalid >> drawable >> ERROR: In >> /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/ >> vtkInteractorStyle.cxx, >> line 392 >> vtkInteractorStyleJoystickCamera (0x3567600): Timer start failed > > I think David Cole fixed this 2 year old bug yesterday. One way to > know would be to update your copy of VTK and rebuild. If you are using > VTK 5.2 the patch will be merged in a couple of day. > I will update my 5.2 branch next week sometime to get this fix. > <...> > >> And I see two windows which does not seem correct. > > Alright so this leave us with one issue the WindowRemap not > implemented for Cocoa. But technically this is not required. So I am > not sure how this is happening. > > If you add let say an 'abort()' call on line 742: > > //this means the user has reparented us; let's adapt to the > abort(); > > If you recompile+rerun, if you hit this abort, this is bad news, it > means the wxVTK did not work as expected. The way it was designed is > that the function GetHandleHack() cannot be called too early, but only > after the first OnPaint event. Check wxVTK::OnPaint and print the > value of Handle at the end of the function. It is aborting before OnPaint is being called: leonidas:build mccdo$ ./wxImagePlaneWidget.app/Contents/MacOS/ wxImagePlaneWidget ERROR: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/IO/ vtkVolume16Reader.cxx, line 355 vtkVolume16Reader (0x356ffb0): Can't find file: ../../../../VTKData/ Data/headsq/quarter.1 going to abort I am not worried about the VTK data stuff for now. I can download and get that working later. What would you like to try next? Doug |
|
From: Mathieu M. <mat...@gm...> - 2008-08-15 08:41:26
|
Hi Doug, Alright finally some progress ! Don't forget to send me the patch in the end :) On Fri, Aug 15, 2008 at 12:04 AM, Doug McCorkle <mc...@ia...> wrote: > I got everything built now. I just told cmake to use the 10.5 sdk not the > 10.4. Anyway, I now get this when running a sample: > > leonidas:build mccdo$ > ./wxImagePlaneWidget.app/Contents/MacOS/wxImagePlaneWidget > ERROR: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/IO/vtkVolume16Reader.cxx, > line 355 > vtkVolume16Reader (0x3571a00): Can't find file: > ../../../../VTKData/Data/headsq/quarter.1 I do not think I implemented the -D command line option, so you have to do: export VTK_DATA_ROOT=/Volumes/data/VE_Suite_Deps/VTK_new/VTKData If you do not have VTKData, download it from the vtk.org page (you can do it from CVS command line by replace VTK with VTKData) > Warning: In > /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/vtkCocoaRenderWindow.h, > line 138 > vtkCocoaRenderWindow (0x35716c0): SetNextWindowId not implemented > (WindowRemap not implemented). ouch ! > Warning: In > /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/vtkCocoaRenderWindow.mm, > line 813 > vtkCocoaRenderWindow (0x35716c0): Can't remap the window. ouch 2 ! > 2008-08-14 17:01:02.903 wxImagePlaneWidget[47823:10b] invalid drawable > 2008-08-14 17:01:02.938 wxImagePlaneWidget[47823:10b] invalid drawable > ERROR: In > /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/vtkInteractorStyle.cxx, > line 392 > vtkInteractorStyleJoystickCamera (0x3567600): Timer start failed I think David Cole fixed this 2 year old bug yesterday. One way to know would be to update your copy of VTK and rebuild. If you are using VTK 5.2 the patch will be merged in a couple of day. <...> > And I see two windows which does not seem correct. Alright so this leave us with one issue the WindowRemap not implemented for Cocoa. But technically this is not required. So I am not sure how this is happening. If you add let say an 'abort()' call on line 742: //this means the user has reparented us; let's adapt to the abort(); If you recompile+rerun, if you hit this abort, this is bad news, it means the wxVTK did not work as expected. The way it was designed is that the function GetHandleHack() cannot be called too early, but only after the first OnPaint event. Check wxVTK::OnPaint and print the value of Handle at the end of the function. As usual send me the output. -- Mathieu |
|
From: Doug M. <mc...@ia...> - 2008-08-14 22:04:31
|
On Aug 14, 2008, at 9:54 AM, Mathieu Malaterre wrote: > On Thu, Aug 14, 2008 at 4:52 PM, Mathieu Malaterre > <mat...@gm...> wrote: >> On Thu, Aug 14, 2008 at 4:42 PM, Doug McCorkle <mc...@ia...> >> wrote: >>> I know get: >> >> s/know/now/ >> >>> eonidas:build mccdo$ make >>> [ 10%] Building CXX object >>> CMakeFiles/wxImagePlaneWidget.dir/Volumes/data/Volumes/data/ >>> Volumes/data/stuff/data/VE_Suite_Deps/wxVTK/wxVTK/src/ >>> wxVTKRenderWindowInteractor.cxx.o >>> /Volumes/data/Volumes/data/Volumes/data/stuff/data/VE_Suite_Deps/ >>> wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:39:35: >>> error: vtkCarbonRenderWindow.h: No such file or directory >>> /Volumes/data/Volumes/data/Volumes/data/stuff/data/VE_Suite_Deps/ >>> wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx: >>> In member function 'void >>> wxVTKRenderWindowInteractor::OnPaint(wxPaintEvent&)': >>> /Volumes/data/Volumes/data/Volumes/data/stuff/data/VE_Suite_Deps/ >>> wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:390: >>> error: 'vtkCarbonRenderWindow' was not declared in this scope >>> /Volumes/data/Volumes/data/Volumes/data/stuff/data/VE_Suite_Deps/ >>> wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:390: >>> error: 'rwin' was not declared in this scope >>> /Volumes/data/Volumes/data/Volumes/data/stuff/data/VE_Suite_Deps/ >>> wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:390: >>> error: 'vtkCarbonRenderWindow' is not a class or namespace >>> make[2]: *** >>> [CMakeFiles/wxImagePlaneWidget.dir/Volumes/data/Volumes/data/ >>> Volumes/data/stuff/data/VE_Suite_Deps/wxVTK/wxVTK/src/ >>> wxVTKRenderWindowInteractor.cxx.o] >>> Error 1 >>> make[1]: *** [CMakeFiles/wxImagePlaneWidget.dir/all] Error 2 >>> make: *** [all] Error 2 >>> leonidas:build mccdo$ >> >> How is that even possible ? Why isn't __WXCOCOA__ defined in your wx >> build ? How did you built wx ? >> >> According to documentation in wx/platform.h I can read: >> >> /* >> WXMAC variants >> __WXMAC_CLASSIC__ means ppc non-carbon builds, __WXMAC_CARBON__ >> means >> carbon API available (mach or cfm builds) , __WXMAC_OSX__ means >> mach-o >> builds, running under 10.2 + only >> */ >> >> which one of those #define is set in your build ? >> >> Thanks >> -- >> Mathieu >> > > Ah, I see, I misread the doc it should have been '__WXMAC_CLASSIC__' > right ? > > http://wxvtk.cvs.sourceforge.net/wxvtk/wxVTK/src/wxVTKRenderWindowInteractor.cxx?r1=1.40&r2=1.41 I got everything built now. I just told cmake to use the 10.5 sdk not the 10.4. Anyway, I now get this when running a sample: leonidas:build mccdo$ ./wxImagePlaneWidget.app/Contents/MacOS/ wxImagePlaneWidget ERROR: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/IO/ vtkVolume16Reader.cxx, line 355 vtkVolume16Reader (0x3571a00): Can't find file: ../../../../VTKData/ Data/headsq/quarter.1 Warning: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/ vtkCocoaRenderWindow.h, line 138 vtkCocoaRenderWindow (0x35716c0): SetNextWindowId not implemented (WindowRemap not implemented). Warning: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/ vtkCocoaRenderWindow.mm, line 813 vtkCocoaRenderWindow (0x35716c0): Can't remap the window. 2008-08-14 17:01:02.903 wxImagePlaneWidget[47823:10b] invalid drawable 2008-08-14 17:01:02.938 wxImagePlaneWidget[47823:10b] invalid drawable ERROR: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/ vtkInteractorStyle.cxx, line 392 vtkInteractorStyleJoystickCamera (0x3567600): Timer start failed leonidas:build mccdo$ ./wxImagePlaneWidget.app/Contents/MacOS/ wxImagePlaneWidget ERROR: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/IO/ vtkVolume16Reader.cxx, line 355 vtkVolume16Reader (0x356ffa0): Can't find file: ../../../../VTKData/ Data/headsq/quarter.1 Warning: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/ vtkCocoaRenderWindow.h, line 138 vtkCocoaRenderWindow (0x356fc60): SetNextWindowId not implemented (WindowRemap not implemented). Warning: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/ vtkCocoaRenderWindow.mm, line 813 vtkCocoaRenderWindow (0x356fc60): Can't remap the window. 2008-08-14 17:02:08.366 wxImagePlaneWidget[47828:10b] invalid drawable 2008-08-14 17:02:08.371 wxImagePlaneWidget[47828:10b] invalid drawable And I see two windows which does not seem correct. Doug |
4 messages has been excluded from this view by a project administrator.
