cqtu-log issueshttps://git.dk0tu.de/cqtu/cqtu-log/-/issues2017-04-10T23:40:57Zhttps://git.dk0tu.de/cqtu/cqtu-log/-/issues/2No-R not saved2017-04-10T23:40:57ZLars Weilerdc4lw@darc.deNo-R not savedThe running number can be entered, it will be displayed, but it is not saved in the Cabrillo file. After closing the App and loading a Cabrillo file, the No-R column is empty.The running number can be entered, it will be displayed, but it is not saved in the Cabrillo file. After closing the App and loading a Cabrillo file, the No-R column is empty.Sebastian Lange (DL7BST)Sebastian Lange (DL7BST)https://git.dk0tu.de/cqtu/cqtu-log/-/issues/1Autosave log on edit2017-04-10T23:40:57ZAlexander Maaß (DF4NEN)Autosave log on editAutosave when logging a new QSO works like a charme.
Can we achieve the same behaviour when editing an already-logged QSO in the table?Autosave when logging a new QSO works like a charme.
Can we achieve the same behaviour when editing an already-logged QSO in the table?Sebastian Lange (DL7BST)Sebastian Lange (DL7BST)