If you want to have mouse control when using PAF, you have to run your
interactive session from ipython:
ipython -wthread
Actually ipython can deal with python/wx threading issues (whereas the
standard python console cannot).
Regards,
Thomas
2009/9/28 Simon Loic
> Ok fine, Yet I'm still annoy
Ok fine, Yet I'm still annoyed by the seg fault when quitting python, and
also the fact that I don't have mouse control on the 3D viewer wen following
the PAF tutorial. Were those fixed also? I'm at a conference in Kyoto for a
week, and I would not have access to the computer where I did the instal
Hi Loic,
I faced the same issue with Snow Leopard 64 bits (actually the same
traceback). I had to tweak the configure.ac script and rebuild
salomegeometry.
Please can you test the following operation:
First apply the attached patch (It can be easily done manually)
Then:
cd (your_salomegeomtry_pat
Hi,
There was a mistake in the first part of the PAF tutorial. I updated the
wiki.
Regards,
Thomas
2009/9/18 Thomas Paviot
> 2009/9/18 Simon Loic
>
>> Hi Thomas,
>>
>
> Hi Loïc,
>
>
>> You're a life saver ;-)
>> Seriously, after your commit, I still had the casting error, but after
>> switchi
Hi Yorik,
Do you try compile pythonocc trunk? Your Modules.py script seems to be out
of date. Please type:
cd pythonocc/src/wrapper
rm Modules.py
svn update
And rebuild. Is it the same?
Thomas
2009/9/22 Yorik van Havre
> Hi there,
> I just tried again to compile pyocc,
> I compiled/installed
Hi there,
I just tried again to compile pyocc,
I compiled/installed salomegeom first (I made a 64bit deb package of it, if
anyone is interested)
I added this line to environment.py:
*SALOME_SMESH_LIB = '/usr/lib'*
because the build process complained that SALOME_SMESH_LIB was undefined,
now I
Hi
Strrange: the two backtraces are very different, whereas the python scripts
> are quite similar. I will investigate this further in the begining of the
> next week. I just
>
The main difference between the two scripts attached before is the order of
the calls:
in PAF1.py, I add parameters heig
2009/9/19 Simon Loic
> Ok, I think we are getting closer.
> I recompiled salomegeometry with CPPFLAGS=-D_OCC64. I recompiled pythonOcc
> too even though I didn't know if it was necessary (I guess it is to avoid
> linking issues).
> Know all three unit tests are successful ;-) which is nice.
> But
Ok, I think we are getting closer.
I recompiled salomegeometry with CPPFLAGS=-D_OCC64. I recompiled pythonOcc
too even though I didn't know if it was necessary (I guess it is to avoid
linking issues).
Know all three unit tests are successful ;-) which is nice.
But running the PAF tutorial I still e
2009/9/19 Simon Loic
> Hello,
> First, thank you! You did more for me than the opposite so far.
> About, the PAF package, I don't understand exactly why, but you are right :
> no need to add PAF in __init__.py. I don't know for what reason I had to add
> it in the first place, but it totally work
Hello,
First, thank you! You did more for me than the opposite so far.
About, the PAF package, I don't understand exactly why, but you are right :
no need to add PAF in __init__.py. I don't know for what reason I had to add
it in the first place, but it totally works without it.
Concerning the back
2009/9/18 Simon Loic
> Hi again,
>
Hi Loïc,
Manu thanks for your feedback.
>
>
> The env_DRAW.sh script contains a set of environment variables that has to
>> be set up before you can use OCC. You can copy/paste the content of this
>> file to your .bash_profile. The most important one is the C
In case it can help, the bactrace I get when running python path_unittest.py
within gdb.
Loïc
On Fri, Sep 18, 2009 at 8:49 PM, Simon Loic wrote:
> Hi again,
>
>
> The env_DRAW.sh script contains a set of environment variables that has to
>> be set up before you can use OCC. You can copy/paste t
Hi again,
The env_DRAW.sh script contains a set of environment variables that has to
> be set up before you can use OCC. You can copy/paste the content of this
> file to your .bash_profile. The most important one is the CSF_GraphicShr,
> that points to the OCC OpenGL lib, and enables the 3D displ
2009/9/18 Simon Loic
> Hi Thomas,
>
Hi Loïc,
> You're a life saver ;-)
> Seriously, after your commit, I still had the casting error, but after
> switching to swig 1.3.39 (instead of 1.3.36), the error disappeared. Then
> the build step and install went well.
> I have a few remaining questions
Hi Thomas,
You're a life saver ;-)
Seriously, after your commit, I still had the casting error, but after
switching to swig 1.3.39 (instead of 1.3.36), the error disappeared. Then
the build step and install went well.
I have a few remaining questions, if you don't mind.
The two first refer to the
2009/9/18 Thomas Paviot
> 2009/9/18 Simon Loic
>
>> Hi Thomas,
>> Thanks for your blameless support.
>>
>> On Fri, Sep 18, 2009 at 12:12 PM, Thomas Paviot wrote:
>>
>>> I think it's actually better to compile pythonOCC trunk. It's compliant
>>> with the latest rev. of salomegeometry trunk.
>>>
>
2009/9/18 Simon Loic
> Hi Thomas,
> Thanks for your blameless support.
>
> On Fri, Sep 18, 2009 at 12:12 PM, Thomas Paviot wrote:
>
>> I think it's actually better to compile pythonOCC trunk. It's compliant
>> with the latest rev. of salomegeometry trunk.
>>
>>
> In that case should I use salome
Hi Thomas,
Thanks for your blameless support.
On Fri, Sep 18, 2009 at 12:12 PM, Thomas Paviot wrote:
> I think it's actually better to compile pythonOCC trunk. It's compliant
> with the latest rev. of salomegeometry trunk.
>
>
In that case should I use salometrunk instead of the rev.175?
> Ma
2009/9/18 Simon Loic
> Hi Thomas,
> Man, I'm so mad at myself!! I wish I didn't waste so much time compiling
> Salome!
>
Well, you could not guess that salomegeometry was required instead of the
whole Salomé project.
> Ok I compiled and installed salomegeometry without any problem.
> Now I am
Hi Thomas,
Man, I'm so mad at myself!! I wish I didn't waste so much time compiling
Salome!
Ok I compiled and installed salomegeometry without any problem.
Now I am trying to compile pythonOcc trunk (as you told me 0.3 doesn't
support 64 bits- yet the -march=X86_64 error remains but easy to solve).
2009/9/18 Simon Loic
> Hi,
>
Hi Simon,
> I'm new to PythonOcc, and found it very promising. Thanks for the work.
>
Welcome on board!
> However it took me more than 3 days to make it compile and I'm not finished
> yet.
>
Ouch. You should have ask a few questions on this forum earlier, this
22 matches
Mail list logo
