New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

painting slow with many layers with width > 1 #174

Closed
klayoutmatthias opened this Issue Sep 28, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@klayoutmatthias
Owner

klayoutmatthias commented Sep 28, 2018

Even if the layers are empty, screen update is slow. There seem to be low hanging fruits for performance improvement.

@klayoutmatthias

This comment has been minimized.

Owner

klayoutmatthias commented Sep 30, 2018

Fixed with 0026b89

netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this issue Dec 9, 2018

mef
Updated cad/klayout 0.25.4 to 0.25.6
0.25.6          (2018-11-23):

* Enhancement: klayoutmatthias/klayout#199
       Added an option to export DXF polygons as LINE objects
* Bugfix: klayoutmatthias/klayout#198
       Stitching of DXF contours wasn't taking nearest neighbours
* Bugfix: klayoutmatthias/klayout#191
       MainWindow/PluginRoot classes got mixed up
       As a side effect of this fix, layout views can now
       be configured individually. This wasn't working
       consistently before.

0.25.5          (2018-10-20):

* Bugfix: klayoutmatthias/klayout#162
       GDS2 LIBNAME was not maintained on "File/Save".
* Bugfix: klayoutmatthias/klayout#166
       Internal error when writing GDS files (breaking of polygons)
* Bugfix: klayoutmatthias/klayout#172
       DEF reader did not pull vias from LEF
* Bugfix: klayoutmatthias/klayout#174
       Performance issue with many layers with width >1
* Bugfix: klayoutmatthias/klayout#176
       Painting issue with texts
* Bugfix: klayoutmatthias/klayout#185
       Hash values available as __hash__ standard method now
       for Python
* Bugfix: some potential memory corruption issues fixed
       During the efforts for making the code base compatible
       with MSVC, some potential candidates for memory corruption
       have been identified and fixed.
       These fixes are included in this release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment