Skip to content
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

Known Issue in 3.16.0: Unable to open Diagram files #1313

Closed
mlonsk opened this issue Jun 14, 2024 · 1 comment
Closed

Known Issue in 3.16.0: Unable to open Diagram files #1313

mlonsk opened this issue Jun 14, 2024 · 1 comment
Assignees
Labels
issue: bug Confirmed as a bug in TE3 issue: critical issue that has severe impact on the core functionality with no workaround
Milestone

Comments

@mlonsk
Copy link
Collaborator

mlonsk commented Jun 14, 2024

Description

Tabular Editor 3.16.0 has a known bug that it is not possible to open saved diagram files (.te3diag)

As shown in the screenshot below, a dialog box will appear, claiming it is an unknown file type.

We are treating this as a critical bug and will provide a few as soon as possible, most likely during the week starting Monday, the 17th of June.

Tabular Editor 3 Version

3.16.0

Screenshots

image

Steps to Reproduce

Go to File -> Open -> File
Choose a .te3diag file to open
Error message appears

Expected behavior

No response

Crash Report

No response

Windows Version

11

@mlonsk mlonsk added issue: bug Confirmed as a bug in TE3 issue: critical issue that has severe impact on the core functionality with no workaround labels Jun 14, 2024
@mlonsk mlonsk added this to the 3.16.1 milestone Jun 14, 2024
@mlonsk mlonsk self-assigned this Jun 14, 2024
@mlonsk mlonsk pinned this issue Jun 14, 2024
@otykier
Copy link
Collaborator

otykier commented Jun 18, 2024

This issue has now been fixed in 3.16.1.

@otykier otykier closed this as completed Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: bug Confirmed as a bug in TE3 issue: critical issue that has severe impact on the core functionality with no workaround
Development

No branches or pull requests

2 participants