UI issues with File → Save as

Open
#2,125 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
desktop

Research direction

Reproduce the reported File → Save as workflow in version 0.30.3 using the XSECTION layout and DXF selection. Check whether the filename and selected format are preserved, whether formats appear twice, and whether warning text is clipped; also compare opening the exported DXF in Inkscape and LibreOffice. Done means the reported save-dialog issues are resolved and the DXF opens as expected.

Written by the indexing model from the issue text.

Description

Hi @klayoutmatthias

noticed some issues with the File → Save as.

  • version 0.30.3
  • made an XSECTION of a sky130A Layout and wanted to save it as a DXF:
    Image
  • next I choose the format from the popup button list and the filename xsection.dxf
    Image
  • then I get this window:
    Image

Issues observed:

  1. the chosen filename is not getting respected, instead .oas is appended (might be a side-effect of point 2)
  2. Instead of chosen format DXF, OASIS is selected
  3. Warning text is clipped vertically
  4. Warning text is clipped vertically

In addition, in the format popup button list everything is listed twice:
Image

Potentially there's also a DXF serialization problem (or Inkscape has a bug), when trying to open the DXF with Inkscape:
Image
It does open successfully in LibreOffice:
Image

Best,
Martin

Dominant language
C++
Stars
1.2k
Forks
305
Avg merge
3d 2h
Merged PRs (30d)
11

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from KLayout/klayout

All issues in KLayout/klayout

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.