thirtythreeforty / consensus Goto Github PK

Issue automatically created from support request from: [email protected]

First Attachment: http://ift.tt/19fNRe4

Date: February 03, 2016 at 02:58PM

The following message was forwarded to you because you are the developer of Consensus

Two things:

• The health complication should only redraw once per minute, rather than as the data comes in, if it has
  a heart icon and not a step count (planned feature).
• The HighlightComplication framework should not spin up an animation for every angle change -- only if the change is large enough to see and appreciate the animation.

Disable-able of course.

Issue automatically created from support request from: [email protected]

First Attachment: http://ift.tt/19fNRe4

Date: February 03, 2016 at 02:05PM

The following message was forwarded to you because you are the developer of Consensus

Hi, if you could add the option of temperature instead if weather or something like that would be much useful qhen looking at it. Thank you.

Issue automatically created from support request from: [email protected]

First Attachment: http://ift.tt/19fNRe4

Date: February 03, 2016 at 03:16PM

Hey,
Sorry you're having trouble.  Exactly what happens when you press save?
George

On Wed, Feb 3, 2016 at 2:58 PM, John Klunder wrote:

The following message was forwarded to you because you are the developer of Consensus

This was originally the goal of #10 but we aren't going to get a white background by v3.0.

I guess this should be different from themes. It's definitely low on the priority list.

😃

Issue automatically created from support request from: [email protected] First Attachment Date: February 03, 2016 at 04:27PM

The following message was forwarded to you because you are the developer of Consensus

Including opt-out

Hi there.
Great stuff here. Slight suggestion, offer different colors for the background; or at least the color grey. Overhead lights make it difficult to see with the black background. But I do like the darker color for battery conservation. I know I can shake the watch to get the background light, but im going to start looking like a crazy person everyone I want to check the time.
Just a suggestion. The overall app is great though. Keep it up. :)

Hel

In progress. Need:

• Detect user's proper unit system
• Show units (#21)
• Add config elements

first off, Great watch face! and since you asked for new complication ideas, how about: - additional time zone (digital or analog)

This will be tricky because users will complain if they can't update often enough, but they also can't overload the free weather API. Require a donation for this?

Happens on v3 -> v4 settings update and probably other places too.

Issue automatically created from support request from: [email protected]

First Attachment: http://ift.tt/19fNRe4

Date: February 03, 2016 at 02:57PM

Hello!
The complication measures against your per-day average over the past month.  "Usual" isn't displayed, although I may add it as a little yellow tick mark on the complication once Pebble allows me to get that information in a convenient way.
I could definitely look into adding a user-defined goal.  That shouldn't be too hard!

-- George

On Wed, Feb 3, 2016 at 2:05 PM, Andy Li wrote:

The following message was forwarded to you because you are the developer of Consensus

Need a small unit at the bottom of most numbers to explain their units (degF, %, etc).

Andy Li [email protected] says:

For the health complication circle, is it comparing your current steps to the actual weekly average steps or the "usual" steps by that time of day?

Also, would it be possible to add a user defined goal for the circle? Say 10,000 steps or something instead of just using the average steps.

Thanks!

This is blocking #10, #8, #9, and most other future interesting things.

When the weather refreshes, complications change, anything. Needs a proper change setup like the other complication type.

Hey

When I going too settings to change I press on save  save do nothing I can not change
My english is not very good  sorry

John

Currently nothing at all happens if the fetch fails. The watchapp needs to be informed of this and to handle it.

We already (as of v3) offer the option to disable while asleep, but this is blocked on a new API letting us read the quiet mode status.