Closed JakeSFR closed 3 years ago
I found a following commit on my fork of rox. https://github.com/jun7/literocks/commit/8f0a3e9ef6e65f3ba998bca35ae9dcfc9eda1c12 (infobox is Properties window) So I think, separate Properties window's date is good. Which is the problem came from? Both that Properties window and details view?
Hmm separating Properties window's date is complex for users. "Set time and date format for Properties window and extra details view." is good enough.
I found a following commit on my fork of rox. jun7/literocks@8f0a3e9 (infobox is Properties window)
So, if I understand correctly, that commit separates time formats for Properties and Details View? That's interesting, I wouldn't mind that in ROX. But yeah, it could confuse some users...
Which is the problem came from? Both that Properties window and details view?
The problem is that I don't like the compact time format (I prefer, e.g. '%Y-%m-%d %T'), but @step- does. :) So, the best compromise was to make it customizable.
Hmm separating Properties window's date is complex for users. "Set time and date format for Properties window and extra details view." is good enough.
Ok, so am I supposed to make a PR? The code's good?
It is good that the option is in display.c/h .
Ok, so am I supposed to make a PR? The code's good?
Good!
It is good that the option is in display.c/h .
Ok, so am I supposed to make a PR? The code's good?
Good!
I'm getting some mixed signals. ;) Correct me if I'm wrong, but you wanted me to move that option from filer.c/h to display.c/h before I make the PR? If so, I've done it. I also increased the buffer from 32 to 64, just in case somebody's gonna use some really long format. Here's the PR: https://github.com/jun7/rox-filer/pull/220
Cheers!
If so
Yes. Thank you for reporting!
I fixed the overlap. thank you!
I fixed the overlap. thank you!
Oh, that really great! Works perfect. Many thanks!
Hey Jun,
I've added an option to set custom time/date format for Properties window and extra details view:
Here's the patch:
There are 2 minor issues, though:
char time_buf[32]
in support.c,I'm not sure how to fix these (other than increasing the buffer, in the first one) and not sure if the way I did it is good enough either. Anyway, what do you think about it?