Save project from tcl takes forever

Issue #395 closed
Leandro Heck created an issue

I am running this save_project project.Flatprj

Using 8.991 on Linux (Ubuntu 19.04)

And after so much time, it gives up.

ERROR: Unknown error: Operation timed outed! Consider increasing option '-timeout <miliseconds>' for command or 'set_sys global_background_timeout <miliseconds>'.
while executing
"save_project project.Flatprj"

Comments (7)

  1. Marius Stanciu

    That’s because you need to specify the absolute path (like everywhere in FlatCAM) where you are going to save the project. Which you did not as I can see from the example you offered.

    E.g:

    save_project D:\project.FlatPrj
    

    In the next version of FlatCAM beta (8.992) all the Tcl commands will have a more clear (but concise) explanation included in the text displayed after issuing the command:

    help tcl_command_name
    

    I’ve done it a few days ago.

  2. Leandro Heck reporter
    • changed status to open

    So, this is a bug the tool help, since it does not show anything saying absolute path there.

    See:

    Saves the FlatCAM project to file.

    save_project filename filename <str>: Path to file. [-timeout <int>: Max wait for job timeout before error.]

  3. Marius Stanciu

    The Tcl help output created by issuing the command:

    help save_project
    

    is:

    > help save_project 
    Saves the FlatCAM project to file.
    > save_project filename
        filename <str>: Path to file.
        [-timeout <int>: Max wait for job timeout before error.]
    

    FlatCAM do not use absolute paths. I hope you understand that and understand that this is not a bug as the help clearly says that the filename parameter is of type string and a "path to file".
    Please don’t reopen an issue unless there is a valid reason for that.

  4. Leandro Heck reporter

    First you said:

    “That’s because you need to specify the absolute path (like everywhere in FlatCAM”

    And then now you said:

    “FlatCAM do not use absolute paths. “

    You’ve said conflicting things. If I am misunderstanding something as you state, it is because of the lack of the information. Which is ok, but it will be nice to have this improved. And also others can benefit from it.

    I was using:

    save_project project_name

    Which is a path. A file name is a path to the place where it is installed. But it worked only when I changed to:

    save_project ./project_name

    But both are the same. So it is a bug even if you disagree. But I understand that you don’t want to fix it.

    Please don’t reopen an issue unless there is a valid reason for that.

    I totally agree with thay, but when I reopened it was a valid reason.

  5. Leandro Heck reporter

    Oh, you are so dedicated dude. It is 1:50 AM here in the South of Brazil. Thanks by the way.

  6. Log in to comment