Open ax006ho opened 4 months ago
thanks for the report. which version is this? could it be that you edited the cfg with a more recent git version than vkdt on this other machine? there is some compatibility issue with the config files, because they now explicitly write disconnection events (this is needed for edit history/undo). i can probably look into not writing these when writing condensed history to .cfg instead of undo history.
I've just cloned the github repository, so all .cfg files are at their original state, and I get the appended log for compiling and executing vkdt. At the beginning of the log you find the information concerning the vkdt version and the system, the associated screenshot is the same as above.
.. you sure your cfg files are in the same state? these aren't managed by the vkdt git repo, the unsuccessful loading might have overwritten them last time (by deleting some module definitions or connections for instance).
On Tue, Jul 9, 2024 at 11:27 AM ax006ho @.***> wrote:
I've just cloned the github repository, so all .cfg files are at their original state, and I get the appended log for compiling and executing vkdt. At the beginning of the log you find the information concerning the vkdt version and the system, the associated screenshot is the same as above.
pce_stdout_master.log https://github.com/user-attachments/files/16141248/pce_stdout_master.log
— Reply to this email directly, view it on GitHub https://github.com/hanatos/vkdt/issues/132#issuecomment-2217147012, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMAKKISJXQQXOKV3UVGUJTZLOUH3AVCNFSM6AAAAABKPTUJMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJXGE2DOMBRGI . You are receiving this because you commented.Message ID: @.***>
If you mean the .cfg-files below the vkdt directory, they were created new, as I've used an empty vkdt directory.
Now also removed ~/.config/vkdt with the same result as above mentioned.
Testing vkdt on another system ends in the attached screenshot and produces the attached .log file.
pce_stdout_master.log
Is the initialization missing something?