It is not possible to mark 2 vocabularies in 2 different lesson as synonyms. Reproducible: Always Steps to Reproduce: 1. Create 2 different vocabularies in 2 different lessons. 2. Activate in View menu Synonyms 3. Try to choose one of the above vocabulary and then the other one in another lesson. Actual Results: The Synonym view does not offer the two vocabularies as synonyms. Expected Results: The Synonym view does should offer the two vocabularies as synonyms. It is Parley 0.9.5 on KDE 4.9.5 on Ubuntu 12.10 which I couldn't not choose in the menu above
I confirm the behaviour described above. What does not work (how to reproduce the bug): 1. Select a lesson. Select an item in that lesson. At the bottom of the synonyms view, you see "Select Synonyms" (in grey, unclickable). 2. Select a different lesson from the Lessons view. Select an item from that lesson. The Select Synonyms view does not become updated. What works (how to assign synonyms from different lessons if you really need to): 1. In the Lessons view, select "Collection" (the root of the lesson tree). You may even use the Search area for finding the first synonym, or for specifying a search which covers both synonyms. 2. Select first item. If you have used search such that the second synonym now is not visible, click the cross in the Search area to return to the view of the full Collection. 3. Select the second synonym without using the search again. At the bottom of the Synonyms view, you can now click on "word1 and word2 are synonyms". Using search for finding the second synonym does not work because the Synonyms view will either offer to set synonyms with some other word that matches (the beginning of) the second search, or none at all, and sometimes even the correct word you searched for. I have not been able to exactly determine what influences which of these options comes up. Ubuntu 12.04.4 LTS Qt: 4.8.2 KDE Development Platform: 4.12.3 Parley 0.9.4
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Justin, all these issues have been reported 10 years or so ago and are obsolate. Please close them. I have moved on with my life and don't use Parley at the moment. Thank you and have a nice day Juergen Justin Zobel wrote on 12/01/2023 07:27: > https://bugs.kde.org/show_bug.cgi?id=317993 > > Justin Zobel <justin.zobel@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #4 from Justin Zobel <justin.zobel@gmail.com> --- > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! >
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!