-
Notifications
You must be signed in to change notification settings - Fork 278
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
Crowdin v2 fixes #641
Crowdin v2 fixes #641
Conversation
from cache or PO downloaded in browser via Crowdin UI
- At least on VS2019. Due the copy of `projects` `vector` is captured by lambda while the original `projId` belongs to - is destroyed after upper function returns, while lambda is was called asynchroneously later and attemted to use captured `projId` (which already belonged/pointed to non-existent `vector`) - Arrange/refactor variables captures/scopes to only where they actually used (to decrease chance to use some variable in not proper place/lambda or just simplify reading of code so it clearly which variable where really used thanks to limiting it scope)
Sorry for having introduced that; it is fixed as a side-effect of c53547e. |
Finally this part is outdated based on #633 (comment), as we can just remove that code, no? |
in PO instead of `X-Crowdin-Project` (project `identitifier`) and `X-Crowdin-File` (full path to file in Crowdin)
Done using of |
Yep, pls feel free to remove that outdated commit from this branch/PR or let me know so I would remote it on my own |
I don't think that's true - this was the only AttachCloudSync use
|
Non-conflicting commit as 79e1f92 — thanks! |
It worked same way in v2.3
Yep I checked, it really does not upload if to `Save` files opened from
local cache (from recent files) bu does if opened via `Open from Crowdin`
or when downloaded in browser via Crowdin UI. Sorry for confusion, but
isn't it inconsistent behaviour for `Save` that in one case it just saves
locally while in another still uploads to Crowdin?
the linked bug you discovered
Which one bug?
failure to sync presents as failure to save
1. Why is the same failure ok if `Open from Crowdin` and then `Save` but
not ok if `Save` opened from local cache or downloaded in browser via
Crowdin UI?
2. Why not just to first Save locally and then to upload?
confusing UI with two buttons doing the same (see the bug)
1. Then why `Save` of the file opened via `Open from Crowdin` still
uploads to Crowdin while `Save` of file opened from local cache or
downloaded in browser via Crowdin UI does not? Isn't it confusing even
more? At least for me it is. So IMO then it should not upload on `Save` in
none case to avoid confusions and keep same logic/behaviour for `Save` in
all cases - i.e. just to save file locally on the disk without any upload.
2. Which one bug?
inconsistent behavior between opening-from-crowdin and
opening-from-recent-files
Inconsistent when `Save` of opened from local cache (from recent files)
uploads to Crowdin or when not? And the same for `Save` downloaded in
browser from Crowdin UI. Because I am confused here since in 2.3 `Save` of
opened via `Open from Crowdin` saves locally and uploads to Crowdin while
`Save` of downloaded in browser from Crowdin UI does not but just saves
locally? Isn't exactly such behaviour/logic inconsistent, while IMO it
would be consistent if `Save` either would not upload in all cases or
opposite would upload in all cases?
…On Thu, Jul 2, 2020 at 4:57 PM Václav Slavík ***@***.***> wrote:
It worked same way in v2.3
I don't think that's true - this was the only AttachCloudSync use
<https://github.com/vslavik/poedit/blob/7a0e93fff167ae5aa786d7b74f7e16b78464c88c/src/edframe.cpp#L1102>
IMO it's properly/useful (why not? what disadvantages it might cause for
users?)
- the linked bug you discovered
- failure to sync presents as failure to save
- confusing UI with two buttons doing the same (see the bug)
- inconsistent behavior between opening-from-crowdin and
opening-from-recent-files
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#641 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEWRVUT3W6YJC2LM5KKG7BTRZSG55ANCNFSM4ONTDQ6A>
.
|
#638 repeatedly referenced above.
Yes, as I said, the UI is confusing and I need to figure out what to do. Which is why I won't be introducing any new inconsistent behaviors until I figure it out. The current state is no worse than 2.3. Changes here can wait until after 2.4. |
I got you now completely. Then since it affects user experience with
Crowdin integration (and only it, nothing else for which I am responsible for that is why trying to focus my efforts to fixing it in 2.4) - why not just to never upload on `Save` regardless it's opened via
`Open from Crowdin`, downloaded in browser via Crowdin UI or from local
cache (resen files)? It would be a quick simple fix while would make
behaviour of `Save` related to Crowdin consistent? While later you/we would
come with some better solution if found? I see that what you propose to
keep the same as in 2.3 is not worse than 2.3. :), but it's definitely not
good as well so making `Save` just save locally (and never upload) would
make it quite consistent IMO and would solve this problem quite quickly and
easily for a while for 2.4 I think. Unless I miss something here.
…On Thu, Jul 2, 2020 at 6:19 PM Václav Slavík ***@***.***> wrote:
Which one bug?
#638 <#638> repeatedly referenced
above.
Isn't it confusing even more?
Yes, as I said, the UI is confusing and I need to figure out what to do.
Which is why I won't be introducing any new inconsistent behaviors until I
figure it out.
The current state is no worse than 2.3. Changes here can wait until after
2.4.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#641 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEWRVURAV5JN6AXRLJKGY4DRZSQRJANCNFSM4ONTDQ6A>
.
|
Yep. There are actually four cases and I failed to consider them all:
Case 4 is e.g. when opening Poedit's own PO files — they are downloaded from Crowdin, they report as being sync-capable. But I absolutely do not want my changes when playing with the files to sync. They happen to be sync friendly, but I didn't download them from Crowdin manually for that purpose. So Save behavior in these cases is:
And then there are 4 more cases, same as above with "...but while being offline" appended. So I don't see any other safe and consistent way to do it in 2.4 other than not syncing on Save at all, as you suggest. What I am worried about is that it is non-obvious for previous users, or even for new ones, that Save is local-only. There should be some indicator of # of not-yet-uploaded changes, or a prompt telling to sync on closing (or saving) the file, or something. |
You definitely better then me know expectations of Poedit customers, but just sharing my own expirience with Poedit about what I tried to guess intuitively when used Poedit and tried to figure out So it's just IMO the best quickest fix for 2.4. would be either
|
Expectations are best learned and clarified through conversations like this, which I deeply appreciate...
I think you're right! That indeed seems to be where we should draw the line. I'll make a separate PR for this (together with addressing #638 as this is all related) and ask you to look it over if you don't mind. |
I think this one is outdated now, right? |
Yep, if you mean this branch/PR |
- If file opened via `Open from Crowdin` or from cache - Also as side effect to the case 3/4 of vslavik#641 (comment) (but IMO it's really very useful feature/addition) if `Sync` button was pressed at least once in above case - it means that customer intetned to sync that file with Crowdin so all futher `Save` will upload that file to Crowdin
- If file opened via `Open from Crowdin` or from cache - Also as side effect to the case 3/4 of vslavik#641 (comment) (but IMO it's really very useful feature/addition) if `Sync` button was pressed at least once in above case - it means that customer intetned to sync that file with Crowdin so all futher `Save` will upload that file to Crowdin
- If file opened via `Open from Crowdin` or from cache - Also as side effect to the case 3/4 of vslavik#641 (comment) (but IMO it's really very useful feature/addition) if `Sync` button was pressed at least once in above case - it means that customer intetned to sync that file with Crowdin so all futher `Save` will upload that file to Crowdin
Fixed some problems/bugs found during testing on all platforms as well as reported by @vslavik by email