Project

General

Profile

Bug #1176

errors during new project creation due to renaming file extension from af3_20 to af3_23

Added by Anonymous almost 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
01/18/2013
Due date:
% Done:

100%

Estimated time:

Description

for instance, the renaming dialog (that appears when a project of same name already exists) doesn't work as expected

also import dialog still only can handle af3_20 files

History

#1 Updated by Anonymous almost 8 years ago

  • Status changed from New to Feedback
  • Assignee changed from Anonymous to Florian Hölzl
  • % Done changed from 0 to 80

implemented and tested import/export handling different kinds of af3_2x files

@FloH:
Is there any way in org.fortiss.af3.project.ui.utils.ExportProjectUtils.fileSelectionDialog(String) to get the information if the current selected project is a af3_20 or a af3_23 file? Currently, exported files are fixed set to .af3_23, even if they had the extension af3_20 before.

btw: when the AF3-Project-Directory has two files "abc.af3_20" and "abc.af3_23", you see 2 "abc" projects in AF3 without knowing which one is one. Is there any way to handle this?

#2 Updated by Florian Hölzl almost 8 years ago

  • Assignee changed from Florian Hölzl to Anonymous

A1: exporting an old file with the nw extension is all right. If the 20 model loaded correctly then its compatible, therefore it is also a valid 23 model.

A2: No.

#3 Updated by Anonymous almost 8 years ago

  • Status changed from Feedback to Resolved

#4 Updated by Anonymous almost 8 years ago

  • Assignee changed from Anonymous to Anonymous

#5 Updated by Anonymous almost 8 years ago

just test import/export and new project creation again under windows.
Now, new projects are created with *.af3_23, but it should also be possible to import old af3_20 files.
During import file selection, you should be able to select if you want to import af3_23 or af3_20 files, both should work

#6 Updated by Anonymous almost 8 years ago

  • Status changed from Resolved to Feedback
  • Assignee changed from Anonymous to Florian Hölzl

Test (Windows):
import af3_20, af3_23 is OK,
export af3_23 is OK.

@Flo: When importing af3_20 files with an invalid model, (e.g. one field is named description instead of definition), the error message still does not contain a hint on the error. It just says: File 'xxx.af3_20' is invalid. Can we provide more information here? The exception states: Feature 'description' not found...

#7 Updated by Anonymous almost 8 years ago

I did not test the library files.

#8 Updated by Florian Hölzl almost 8 years ago

  • Status changed from Feedback to Closed
  • Assignee deleted (Florian Hölzl)
  • % Done changed from 80 to 100

Also available in: Atom PDF