Thanks Thomas for the feed-back. I will try this tomorrow. (This e-mail is send from another machine).
Regards and have a nice evening! Marco On Sat, Mar 21, 2009 at 5:42 AM, Thomas Paviot <thomas.pav...@free.fr> wrote: > > > M. Nawijn a écrit : >> >> On Fri, Mar 20, 2009 at 4:18 PM, <thomas.pav...@free.fr> wrote: >> >>>>>> >>>>>> Objet: Re: [Pythonocc-users] Scons script update >>>>>> >>>>>> Hi Guys, >>>>>> >>>>>> It is me again. With the new added compile options, the SWIG >>>>>> generation and compilation succeeded >>>>>> without any problem. >>>>>> >>>>>> Than it started to get exciting. Would the bottle fail me again? >>>>>> NO.... It worked!!! >>>>>> >>>>> >>>>> What an excellent news! >>>>> >>>>> >>>>>> >>>>>> This effectively means that the -D_OCC64 and possible -m64 compilation >>>>>> options should be enabled >>>>>> on 64 bit platforms. >>>>>> >>>>> >>>>> I'll add this to the SConstruct file. I have to detect, from Python, >>>>> that your processor is 64 bits. >>>>> >>>>> >>>>>> >>>>>> One final problem to solve. It seems like the viewer part is not >>>>>> working correctly for my system. If I try to execute >>>>>> the wxDisplay script on Windows it provides me with a viewer showing a >>>>>> brick/box. On my Linux machine, >>>>>> a short flash is seen, than the script terminates. >>>>>> >>>>>> The only output I get is: >>>>>> >>>>>> >>>>>>>> >>>>>>>> python wxDisplay.py >>>>>>>> >>>>>> >>>>>> Display3d class initialization starting ... >>>>>> >>>>>> Any suggestions? >>>>>> >>>>> >>>>> No more error message? It certainly means that it does not come from >>>>> OCC. What wxPython version do you use? >>>>> >>>> >>>> Name : wxPython >>>> Arch : x86_64 >>>> Version : 2.8.9.1 >>>> Release : 1.fc9 >>>> >>> >>> I think I got it: check the __init__.py script in your /site-packages >>> directory. >>> >>> You may have a line like: >>> export['CSF_GraphicShr']='/usr/local/lib/libTKOpenGL.so' >>> This overwrites the one you defined. >>> >>> Just comment out this line ansd everything should be ok. >>> >> >> Hmmm.... this is not the case. The variable is set to the correct >> value. I checked this by printing the value prior to >> driver initialisation. I tracked the error down to the following call >> in OCCViewer.BaseDriver >> >> self.Init(self._window_handle) >> >> This one fails. I checked if I have a correct window handle and it >> looks reasonable.This call is directly forward to the C++ side, so I >> probably have to dig in this. >> >> Another option could be to first try it with an ordinary X Window >> instead of going through the wx stuff. >> >> Bye, >> >> Marco >> >> >> > > Hi Marco, > > In order to check whether it comes from OCC or wxPython, here is the > following test case (it's not necessary to run wxDisplay.py): > > Type "help", "copyright", "credits" or "license" for more information. > >>>> from OCC.Visualization import * >>>> d = Display3d() >>>> d.Init(0) #pass a 'fake' widnow handler > > Display3d class initialization starting ... > Graphic device created. > *Xw_Error_4/1*code 3/'BadWindow (invalid Window parameter)' > from Xw_error_handler routine > *Xw_Error_3/2*Bad Window 0 Attributes from Xw_get_window_position routine > Xw_Window created. > Viewer created. > *Xw_Error_3/1*Bad EXT_WINDOW Address 0 from Xw_get_window_size routine > Segmentation fault > > I ran this on Ubuntu. If the line "Graphic Device Created" is not displayed, > then it may come from: > - an OpenGL issue, > - the CSF_GraphicShr env var is not properly set > > Cheers, > > Thomas > > > > > > _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
