When moving a TODO with the mouse the change is not saved to disc when using a directory resource (file resource works) #35

Aberto
aberto por ugemkow 5 anos atrás · 6 comentários

When moving a TODO with the mouse (dragging) to another day the change is not saved to disc when the TODO is handled by a local directory resource. When using a file resource, this works.

Also it works when the TODOs date is changed in the dialog box.

  • TDE version: R14.0.6, self compiled
  • Distribution: Ubuntu 18.04
  • Hardware: amd64

Steps to reproduce

  1. Create a TODO in a directory resource
  2. Move the TODO in the calendar view i.e. to another day
  3. Leave Kontact, the change is not saved

See also Issue #34 which may be related.

When moving a TODO with the mouse (dragging) to another day the change is not saved to disc when the TODO is handled by a local directory resource. When using a file resource, this works. Also it works when the TODOs date is changed in the dialog box. - TDE version: R14.0.6, self compiled - Distribution: Ubuntu 18.04 - Hardware: amd64 ## Steps to reproduce 1. Create a TODO in a directory resource 2. Move the TODO in the calendar view i.e. to another day 3. Leave Kontact, the change is not saved See also Issue #34 which may be related.
Proprietário

Hi Ulrich, a few questions to help my understanding.

  1. is this related to kontact, korganizer or both? I assume Kontact given your comment in 3.
  2. I don't understand exactly the difference between a TODO on a file resource and on a directory resource. How to create them? Sorry for my ignorance.
  3. Can you add more details to your list of steps to reproduce the problem so that I can try the same here?

Thanks

Hi Ulrich, a few questions to help my understanding. 1. is this related to kontact, korganizer or both? I assume Kontact given your comment in 3. 2. I don't understand exactly the difference between a TODO on a file resource and on a directory resource. How to create them? Sorry for my ignorance. 3. Can you add more details to your list of steps to reproduce the problem so that I can try the same here? Thanks
Autor

Sorry for being too short and thanks for asking!

  1. Kontact is only a container for the PIM Apps kmail, korganizer, ... and gives a common GUI to switch between them. This bug is related to korganizer but will also show in kontact.

  2. korganizer saves its content (calendar entries, TODOs, ...) in a standard text format in so-called resources. There are local resources (saved on the local disc) and remote resources (maintained on a remote server). Local resources may be either file resources (all entries are held in one big file) or directory resources (one separate file for each entry). korganizer can handle more than one resource. They are created in the lower left window (called "Calendar"). When pressing the green "+" the user can select type and location of a (additional) resource.

  3. Sure, I assume you have no resources defined

Steps

  1. Start korganizer
  2. Add a file resource by pressing the green "+", selecting "Calendar in local file" and defining a localtion for the file resource
  3. Be sure that the new resource is selected (check box on the left side of the resource)
  4. Create a new TODO by using the menu Actions->"New Todo", give the TODO a title and the current date in the dialog box (The TODO should be visible in the calendar at the given date)
  5. Now drag the TODO with the mouse to another date (in the future or korganizer refuses to change the TODOs date)
  6. Leave korganizer and start it again. The TODO is on the new date, all is fine

When doing exactly the same sequence but using a resource of type "Calendar in local directory" (using a newly created folder) the new date of the TODO is not saved on disc but remains on the date for which is was created.

Directory resources a much better than file resources for a number of reasons.

Issue #34 is related, the same kind of resources are used there.

Thanks again!

Sorry for being too short and thanks for asking! 1. Kontact is only a container for the PIM Apps kmail, korganizer, ... and gives a common GUI to switch between them. This bug is related to korganizer but will also show in kontact. 2. korganizer saves its content (calendar entries, TODOs, ...) in a standard text format in so-called resources. There are local resources (saved on the local disc) and remote resources (maintained on a remote server). Local resources may be either file resources (all entries are held in one big file) or directory resources (one separate file for each entry). korganizer can handle more than one resource. They are created in the lower left window (called "Calendar"). When pressing the green "+" the user can select type and location of a (additional) resource. 3. Sure, I assume you have no resources defined Steps 1. Start korganizer 2. Add a file resource by pressing the green "+", selecting "Calendar in local file" and defining a localtion for the file resource 3. Be sure that the new resource is selected (check box on the left side of the resource) 4. Create a new TODO by using the menu Actions->"New Todo", give the TODO a title and the current date in the dialog box (The TODO should be visible in the calendar at the given date) 5. Now drag the TODO with the mouse to another date (in the future or korganizer refuses to change the TODOs date) 6. Leave korganizer and start it again. The TODO is on the new date, all is fine When doing exactly the same sequence but using a resource of type "Calendar in local directory" (using a newly created folder) the new date of the TODO is not saved on disc but remains on the date for which is was created. Directory resources a much better than file resources for a number of reasons. Issue #34 is related, the same kind of resources are used there. Thanks again!
Proprietário

Hi Ulrich,

thanks for the detailed explanation. I followed exactly the steps you have described, but I cannot reproduce the problem. Using either "Calendar in local file" and "Calendar in local directory" seems to work fine. The only difference is that I have tested R14.1.0-dev version rather than R14.0.6. Distro is Debian bullseye.

Anything else come to mind?

Hi Ulrich,<br> thanks for the detailed explanation. I followed exactly the steps you have described, but I cannot reproduce the problem. Using either "Calendar in local file" and "Calendar in local directory" seems to work fine. The only difference is that I have tested R14.1.0-dev version rather than R14.0.6. Distro is Debian bullseye. Anything else come to mind?
Proprietário

Hi Ulrich,

I did further testing in slax+TDE using R14.0.6 and again I am not able to reproduce the problem.

Could you download slax from here and try on your computer (or inside a VM) to see if you see the same issue there? At least we would be testing using the same liveCD, so if we still see different behavior it means I am doing something different from you.

Hi Ulrich,<br> I did further testing in slax+TDE using R14.0.6 and again I am not able to reproduce the problem.<br> Could you download slax from [here](http://mirror.ppa.trinitydesktop.org/trinity-sb/cdimages/slax) and try on your computer (or inside a VM) to see if you see the same issue there? At least we would be testing using the same liveCD, so if we still see different behavior it means I am doing something different from you.
Autor

Hi Michele,

thank you very much for looking!

I have done further investigations and maybe the problem is related to the fact that our homes are NFS-mounted. I have not tried when the home is on a local disc and will do this ASAP and report back. Thanks again!!

Hi Michele, thank you very much for looking! I have done further investigations and maybe the problem is related to the fact that our homes are NFS-mounted. I have not tried when the home is on a local disc and will do this ASAP and report back. Thanks again!!
Proprietário

No problem Ulrich. Will be waiting for further feedback. If you still see the problem, please trying testing using slax as explained before, so we can test using the same base environment.

No problem Ulrich. Will be waiting for further feedback. If you still see the problem, please trying testing using slax as explained before, so we can test using the same base environment.
Acesse para participar desta conversação.
Sem marco
Sem responsável
2 participante(s)
Notificações
Data limite

Data limite não informada.

Dependências

Nenhuma dependência definida.

Referência: TDE/tdepim#35
Carregando…
Ainda não há conteúdo.