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

Prevent save on any saving workflow #46

Open
NekoJonez opened this issue Nov 4, 2021 · 8 comments
Open

Prevent save on any saving workflow #46

NekoJonez opened this issue Nov 4, 2021 · 8 comments
Labels
bug Something isn't working

Comments

@NekoJonez
Copy link
Contributor

I have everything on "Warn & prevent save" in the options menu... Yet, if I save a string that doesn't have a . , ? , ! at the end and I save it with one... The tool doesn't stop me anymore. It does give a warning after saving, but it doesn't prevent.

@NekoJonez
Copy link
Contributor Author

Update: it might be a conflict with GlotDict. Disabling that, it stops me when I add an "." at the end. But not when I add any other punctuation marks.
Gonna test further.

@NekoJonez
Copy link
Contributor Author

https://youtu.be/reuWu4beIdI -> GlotDict is the culprint....

@NekoJonez
Copy link
Contributor Author

In testing, it's the shortcut CTRL+Enter that is skipping the check. @vlad-timotei and I confirmed this in Slack DM's.

@vlad-timotei
Copy link
Owner

vlad-timotei commented Nov 4, 2021

GlotDict is not the culpirt, but it introduces a new saving shortcut that WPGPT doesn't catch: Ctrl+Enter

@vlad-timotei vlad-timotei changed the title Punctuation marks prevention bug Prevent save on any saving workflow Nov 4, 2021
@vlad-timotei vlad-timotei added the bug Something isn't working label Nov 4, 2021
@vlad-timotei vlad-timotei added this to the future release milestone Feb 6, 2022
@NekoJonez
Copy link
Contributor Author

NekoJonez commented Feb 7, 2022

-snip-

But, I noticed something else. When you approve the string using WP Translation Filler, the string gets accepted (goes green) but doesn't go current since I assume it gets blocked by this add-on?

@NekoJonez
Copy link
Contributor Author

I just tried it again, and I can still reproduce the issue.

@vlad-timotei
Copy link
Owner

Thanks for investigating.
So, on one hand, we have GD that can save despite WPGPT warning using the keyboard shortcut flow and that should not happen - it's a problem on WPGPT's side. Currently investigating possible technical solutions.

On the other hand we have TF that is not able to save strings with WPGPT warnings using its custom buttons, and I find that correct. Users of WPGPT should be prevented to save strings with warnings in any scenario.

However if TF needs to overrule WPGPT warnings, it can - calling GP native functions directly, not by triggring the Save button that is guarded by WPGPT checks.

So, the main issue stands. Work in progress. :)

@psmits1567
Copy link

psmits1567 commented Feb 7, 2022

TF becomes green if it does not find problems regarding the usage of Glossary verbs. The fact that WPGPT blocks saving, has a different reason. I do not think overuling WPGPT would be wyse. TF does not block bad translations, it only signals that fact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants