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

History CSV filename defaults to using zero-based month #205

Closed
happyconcepts opened this issue Jul 24, 2017 · 8 comments
Closed

History CSV filename defaults to using zero-based month #205

happyconcepts opened this issue Jul 24, 2017 · 8 comments
Labels
[3] Enhancement Classification indicating a change to the functionality of the existing imlementation

Comments

@happyconcepts
Copy link
Contributor

When exporting history as csv from the GUI, the filename defaults to using zero-based month which may be confusing to end users.

Example: btshist-2017-6-22.csv is generated for a history exported on July 22.

@wmbutler
Copy link
Contributor

I'd agree that if you export a file on July 22, it should probably be named appropriately. I'd also advocate a time on the filename down to the second to differentiate it from other files downloaded on the same day. Maybe this:

accountname-YYYYMMDD-HH:MM:SS.csv

@wmbutler wmbutler added the [3] Enhancement Classification indicating a change to the functionality of the existing imlementation label Jul 24, 2017
@happyconcepts
Copy link
Contributor Author

Is this why the Bitshares GUI is so poor? This is a simple fix to an obvious (minor) bug. Yet here it gets stalled to a feature request because you want to add a time stamp.

@landry314
Copy link

I agree that this should be fixed immediately but they don't have enough programmers working to get things done quickly. This is actually the fault of the shareholders of BTS for not voting worker proposals in. We need development money asap!

I am frustrated too.

@happyconcepts
Copy link
Contributor Author

Landry instead of changing your username and deleting your earlier disparaging comment .... why not be supportive or even friendly? Is there some way you might even contribute toward helping solve this issue?

@landry314
Copy link

i deleted my earlier comment because i researched and realized it was technically wrong, that is all. i have not changed my username, i dont know why you think that. could you please stop using this forum for anything other than improving the software? thank you.

Ashaman- added a commit to Ashaman-/bitshares-ui that referenced this issue Jul 27, 2017
Fix Issue bitshares#205. Added timestamp to exported file as well.
@happyconcepts
Copy link
Contributor Author

Closed thx Ash

svk31 pushed a commit that referenced this issue Jul 30, 2017
Fix Issue #205. Added timestamp to exported file as well.
@wmbutler
Copy link
Contributor

It's important that we have constructive comments here. If you choose to conduct your family or business in a disrespectful manner, that is your prerogative, but kindly refrain from gross generalizations about people's perceived capabilities or character.

@wmbutler
Copy link
Contributor

@happyconcepts a time stamp doesn't stall a feature. There are many things playing into the current ui state of affairs. The time stamp suggestion plus the account name was just a suggestion designed to add more clarity to the file. This would also prevent overwriting a previous file of more than one export was pulled in a day. Also, it was a suggestion designed to be discussed on its own merits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[3] Enhancement Classification indicating a change to the functionality of the existing imlementation
Projects
None yet
Development

No branches or pull requests

3 participants