Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Functionality Bug: Data not saved when more than one window is open #3

Open
Jiacheng-y opened this issue Nov 11, 2022 · 1 comment
Open

Comments

@Jiacheng-y
Copy link
Owner

Jiacheng-y commented Nov 11, 2022

When more than one window of the app is open, only edits in one of the window is saved when closing the apps.

To reproduce the bug,

  1. Open two windows of PennyWise

  2. Paste the following command into the command box of one of the windows
    add t/e d/Lunch with mes amis a/15.60 da/31-08-2022 c/Food

  3. Paste the following command into the command box of the other window:
    add t/e d/Dinner1s served a/15.99 da/15-08-2022 c/Food

  4. Exit both windows

  5. Open PennyWise again

  6. Only information from the last closed window is saved.
    e.g.
    I closed the window with add t/e d/Lunch with mes amis a/15.60 da/31-08-2022 c/Food last so on restarting PennyWise, there were no information of add t/e d/Dinner1s served a/15.99 da/15-08-2022 c/Food at all.

Screen Shot 2022-11-11 at 16.53.14 PM.png

This affects users who forgot that they already have the application running in the background and opens the application again. They will then lose all the data that they had inputted from the earlier closed window.

@soc-pe-bot
Copy link

soc-pe-bot commented Nov 14, 2022

Team's Response

We feel that the behaviour of our app is very reasonable. For instance, when we open multiple documents, it is true and expected that the app will take the latest one as the final changes. In addition, it is very rare for users to open the app twice.

Also, we feel that this bug would apply to almost all tP projects and getting penalised for a bug like this would be a little unfair.

We have posted an issue in the focus, issue number #442 and is waiting Prof's response on the matter.

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

  • I disagree

Reason for disagreement: [replace this with your explanation]


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants