pythoncad-developer

Re: [Pythoncad-developer] Pushed many changes to the R38 branch

[Yagnesh D. <yn...@gm...>]

Friends;

Was testing new code pushed in R38. I found

1. The CADing area turned grey.

2. Realtime visibility of newly created entities
is poor. ie if I create a segment or a circle I need to
do some pan or change layers to see them.

3. Tried changing color of the entity it throws
error and do not select the entity. further testing
found I cannot select the entity to move or copy
either.

I use CELERON laptop with 512 RAM.

My suggestion is that python inherently would have
some speed issue. So dynamic zoom / pan may
be kept as user preference to switch on and off.
I am not good at understanding this performance
related problem and do not know if it is related
to python or gtk.

- - - - - -
Best regards

Yagnesh Desai
Save a tree...please don't print this e-mail.

Re: [Pythoncad-developer] Pushed many changes to the R38 branch

[Gertwin G. <ger...@gm...>]

Hi Yagnesh,

> Was testing new code pushed in R38. I found
>
> 1. The CADing area turned grey.
You are right, I have to change that.
I used this grey color to make a difference between the old drawing
methods and the new viewport drawing methods.

>
> 2. Realtime visibility of newly created entities
> is poor. ie if I create a segment or a circle I need to
> do some pan or change layers to see them.
I did not notice this, I think this is a bug.
Each object is drawn after it is added to the current layer.
I think a event is not send or handled in your situation.

>
> 3. Tried changing color of the entity it throws
> error and do not select the entity. further testing
> found I cannot select the entity to move or copy
> either.
We are in the middle of a huge code restructuring.
Do not expect PythonCAD to work as it should during this process.
I pushed the code back to the repository as soon as possible.
Entity drawing and creation of entities should work, all other must
still be adjusted.

In the previous version drawing and rubber banding was done anywhere
in the code.
It is now all concentrated in the viewport package.
All drawing is done by cairo and is easier to maintain.
It is not complete and I introduced a number of bugs, I am aware of that.

>
> I use CELERON laptop with 512 RAM.
>
> My suggestion is that python inherently would have
> some speed issue. So dynamic zoom / pan may
> be kept as user preference to switch on and off.
> I am not good at understanding this performance
> related problem and do not know if it is related
> to python or gtk.
I think the PythonCAD performance can be much better even with only python code.
I noticed a issue in the Generic package where a large amount of
memory is allocated even for a small drawing.
For me it is a challenge to get the best performance out of python.
The dynamic snap is very good at this point, now we have to streamline
the rest of PythonCAD before adding new functionality.

>
> - - - - - -
> Best regards
>
> Yagnesh Desai
> Save a tree...please don't print this e-mail.

Please continue posting your remarks.

Regrads,
Gertwin

Re: [Pythoncad-developer] Pushed many changes to the R38 branch

[<ger...@gm...>]

Hi Yagnesh,

There are not many changes made in the Generic part of PythonCAD.
I think you can still push your modified code into the repository.

A while ago I had a discussion with Matteo about blocks.
The idea was to create some special layers, each of the layer could contain  
a block definition.
The layers are not shown in the layer manager, they just have a block  
definition function.
This is just an idea an has not been worked out yet.

The hatch, ellipse and other entities are also on the list.

You are right it is easier to work with standard fonts.
Otherwise we can look at the *.cxf font definition files used by QCad (I  
don't know the license of this format), this is a vector format.
QCad uses dxf as its native file format so these fonts has to mimic the  
AutoCAD fonts as good as possible.

Regards,
Gertwin



On Jan 12, 2010 2:54am, Yagnesh Desai <yn...@gm...> wrote:
> I understand that you are in middle of reorganizing of

> code for better performance.



> I have started writing the code for import/export of color

> to & from dxf. I am writing it on my earlier git download

> hope should have no issue with the new organized code.



> On the loss of blocks and entities during the import if

> pythoncad can support similar blocks it would be lot

> more easier. (block is handy tool for the CAD user too)

> (Hatch, ellipse & splines are few entities currently

> not available in pythoncad)



> Issue with text is multifold :

> 1. Autocad fonts are proprietary and we will have to leave

> with some adjustment of width and height (by the way AutoCAD

> supports width-factor adjustment if that can be supported

> life becomes a lot more easier with the truetype fonts also)

> 2. Autocad formating is a bit funny since it was taken from

> older way of doing it ie %%u is a tag in text for underlining

> %%b & many more and now with newer version of dxf they

> even have tags in between to change fonts for few words

> in para.

> 3. Dimension text also has some such issues as they have

> some block like behavior. (This I have not yet gone in depth

> since I have not come on dimension).