Load store logs

[ilang-flytrex]

1. Increment the version to 1.2.29
2. Add Load/Store buttons to store/load the table logs
3. Add .vscode configurations

[joshanne]

I'm requesting changes because this should work for linux/windows/macos users alike. It's unclear that it will in this current state.

I've never pushed my launch.json, but the configuration I use is:

        {
            "name": "Python Debugger: DroneCAN GUI Tool",
            "type": "debugpy",
            "request": "launch",
            "program": "${workspaceFolder}/bin/dronecan_gui_tool",
            "cwd": "${workspaceFolder}/dronecan_gui_tool",
            "console": "integratedTerminal",
            "justMyCode": true,
            "args": [
                "--debug"
            ]
        }

[joshanne]

This shouldn't be specific to windows - if you're using vscode to launch it, it should be up to vscode to provide the environment you're using.

[ilang-flytrex]

Sure...The reason I wanted to add this was to simplify it for the programmer. It took me several iterations until I made it run. I come from the bare metal embedded world, and usually when you have a project then you also add the IDE configuration files (there can be more than one), so anyone can just run it without any complications. I'll remove it

[joshanne]

What are you trying to achieve by executing the main module?

With debug enabled, this simply outputs all the dsdl parser information as it is processed at startup. There is no usable application context run.

[ilang-flytrex]

Those are left overs from my attempts to make it run. I'll remove it

[joshanne]

Historically, the version isn't bumped until the immediately before the release.

[ilang-flytrex]

Sure

[ilang-flytrex]

@joshanne ,can you tell me where I can find instructions to how to distribute my code? I tried creating a task in vscode that does it (in windows). I was able to make it work, but for some reason when I start the Jupyter console it appears empty and It's not interactive. I would expect the repo to contain at least a .sh script for performing the distribution.

[joshanne]

can you tell me where I can find instructions to how to distribute my code?

Do you mean distributing the installer to install your version of the tool? Windows? or Linux?

README.md points you to winbuild.bat which is the windows build tool which generates you an MSI at the end. Looks like you might need to update it to ensure your python executable is on the path, but it looks like it should be as simple as running winbuild.bat from the root directory of the repository.

On linux, judging by the github build tasks, you should be able to run the following to generate a wheel file for distribution. The wheel file will be in the dist folder.

python -m pip install --upgrade pip
pip install build
python -m pip install -U flake8 pytest wheel
python -m pip install -U .
python -m build

As for the interactive console not working, I'm unsure - I've not run into that problem. Whenever I launch the program, it seems to work as I expect.

[joshanne]

Windows?

Other thing to note is winbuild.bat says:

rem NOTE: you need visual studio installed, with the C++ build tools

So make sure you have visual studio build tools installed, otherwise you can't build the msi file.

[ilang-flytrex]

@joshanne ,I was sure that winbuild.bat is for building, not creating an msi file, but as you mentioned, it was written in the README file. Thanks a lot. I tried it and it worked