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

Select time of logs #5736

Open
Natureshadow opened this Issue May 12, 2016 · 5 comments

Comments

Projects
None yet
6 participants
@Natureshadow

Natureshadow commented May 12, 2016

[The issue template is somewhat useless for this issue]

The OC platform has an additional time field for logs (in addition to date).

The calendar widget used in LogActivity always sets the time component of its result to the current time.

Logging with the current time is often correct when logging "today", but never when logging a cache found on another day.

c:geo should do one of these, in descending order of preference:

  1. Add a time selector for OC caches.
  2. Use current time when logging "today"; set time to 00:00:00 (and timezone to UTC!) when using another date.
  3. Always set time to 00:00:00 (and timezone to UTC).

-nik

@SammysHP SammysHP changed the title from Logging on OC always uses current time to Select time of logs May 12, 2016

@SammysHP

This comment has been minimized.

Show comment
Hide comment
@SammysHP

SammysHP May 12, 2016

Member

I'd like to make this more generic: The time is also used in fieldnotes and cannot be set manually.

Member

SammysHP commented May 12, 2016

I'd like to make this more generic: The time is also used in fieldnotes and cannot be set manually.

@Bananeweizen

This comment has been minimized.

Show comment
Hide comment
@Bananeweizen

Bananeweizen May 12, 2016

Member

I'm against alternative 1. My assumption is that the far majority of users doesn't care about time found (except maybe for logging a FTF or so). Therefore we shouldn't introduce the burden of an additional input field (and a more complex UI and mental model) for this small use case. I therefore prefer alternative 2 (especially since I also doubt that someone will remember the time of day when logging some found of last week).

Member

Bananeweizen commented May 12, 2016

I'm against alternative 1. My assumption is that the far majority of users doesn't care about time found (except maybe for logging a FTF or so). Therefore we shouldn't introduce the burden of an additional input field (and a more complex UI and mental model) for this small use case. I therefore prefer alternative 2 (especially since I also doubt that someone will remember the time of day when logging some found of last week).

@SammysHP

This comment has been minimized.

Show comment
Hide comment
@SammysHP

SammysHP May 12, 2016

Member

Other apps allow to set the time manually. I don't think that this would make the UI more complex (e.g. small button with clock symbol next to the date selector which opens a time selection popup).

Member

SammysHP commented May 12, 2016

Other apps allow to set the time manually. I don't think that this would make the UI more complex (e.g. small button with clock symbol next to the date selector which opens a time selection popup).

@kumy

This comment has been minimized.

Show comment
Hide comment
@kumy

kumy May 12, 2016

Member

This issue seems related only to OC services, but this remind me #5182.

Member

kumy commented May 12, 2016

This issue seems related only to OC services, but this remind me #5182.

@Natureshadow

This comment has been minimized.

Show comment
Hide comment
@Natureshadow

Natureshadow May 17, 2016

Many cachers care about the order of cache finds, and OC uses the time for that.

In any case, setting the current time is a bug, not a feature request.

Natureshadow commented May 17, 2016

Many cachers care about the order of cache finds, and OC uses the time for that.

In any case, setting the current time is a bug, not a feature request.

@Lineflyer Lineflyer added OC GK and removed GK labels Jun 14, 2016

@samueltardieu samueltardieu added the Bug label Jul 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment