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

When Tweet fails and retry option is set tweet text is lost #1276

Open
EpicLPer opened this issue Jan 20, 2016 · 3 comments
Open

When Tweet fails and retry option is set tweet text is lost #1276

EpicLPer opened this issue Jan 20, 2016 · 3 comments

Comments

@EpicLPer
Copy link

As the title says, when making a screenshot and trying to tweet said picture it sometimes fails for me (weird internal DNS issue I have, probably nothing that's related to ShareX).

However when it fails I've set ShareX to try again, but when it tries again it'll delete the Tweet text when the box comes up again which is a bit annoying. Ctrl + A doesn't work on the box, neither does Ctrl + C really well. You'd have to manually select all text with the mouse, right-click it and copy it before tweeting so you have a "backup" in case it fails.

Can this please be fixed? As said it's only annoying but not a "breaking bug" here now.

@Jaex
Copy link
Member

Jaex commented Jan 20, 2016

That would be very difficult to fix because that retry option works with all uploaders so it can't remember specific uploader settings which was entered in first try. If this were only Twitter uploader app then it would be very easy to fix.

@EpicLPer
Copy link
Author

Just a thought here now but you could make a temporary file which gets written when you click on "Send". The Tweet box should then always look if a temporary file exists prior to opening and if so opens the content of this into the text box.

If the tweet was sent successfully the temporary file gets deleted.

It's just a thought, I'm not aware of the limitations tho.

@Jaex
Copy link
Member

Jaex commented Jan 20, 2016

Of course it is fixable but I just don't want ugly codes/workarounds.

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