Project

General

Profile

Bug #353

In macOS version, I can no longer import .amos applications from Resources folder. Causes Import error.

Added by Brian Flanagan almost 4 years ago. Updated over 3 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
Francois Lionet
Target version:
-
Start date:
04/19/2020
Due date:
% Done:

0%

Estimated time:
Affected version:
0.9.9.3

Description

It doesn't matter which disc archive it's from. I've tried importing code from:

AMOSPro_Examples
AMOSPro_Accessories
AMOSPro_Tutorial
AMOSPro_Productivity1
AMOSPro_Productivity2

All produce the same " Problem during importation... " error. (See attachment.)

An empty folder structure for the imported application is created, then it crashes with the attached error.

For Example, for AMOSPro_Examples/Help_1.AMOS, I get the following folder structure:

AMAL_1
  resources
    filesystem
      application

...and then the import fails.

@Dave_B tried this in the PC version - which does work, so apparently, this is specific to the Mac version.

Files

AMOS_Import_Error.png (24.4 KB) AMOS_Import_Error.png Error when importing any .AMOS program from the resources folder. Brian Flanagan, 04/19/2020 08:37 PM
#1

Updated by Francois Lionet almost 4 years ago

  • Status changed from New to In Progress
  • Assignee set to Francois Lionet

On the task list! For the moment, AMOS import is done via external Windows-only applications. javascript conversion to be done. Certainly for version 0.9.9 or something like that: for the moment, please use a PC, or boot your mac in Windows if you can. If not, then please ask someone to do it for you... ;)

#2

Updated by Brian Flanagan almost 4 years ago

  • Affected version changed from 0.9.8.1 to 0.9.9.3

Re-tested in 0.9.9.3. Problem still exists.

#3

Updated by Brian Flanagan over 3 years ago

  • Status changed from In Progress to Resolved

This appears to be working now!

#4

Updated by Brian Flanagan over 3 years ago

  • Status changed from Resolved to Feedback

This isn't resolved yet... but probably won't be corrected until after the initial release.
It has, however, been disabled in the macOS version, until it can be added to the macOS version.

Also available in: Atom PDF