Notices


Reply
Thread Tools
Posts: 23 | Thanked: 94 times | Joined on Apr 2017
#11
Originally Posted by hias View Post
What are your main itches? Bigger letters are not a big problem.


The major problem is that I might not be able to do things on that dialog because it is no longer my code. I have a lot of ideas for it and I would have to work through your code to implement them.

If you really want to we can use your design although I really liked mine. But we have to make a few adjustments.

Here are my points:
  • the heartrate field with the bar graph is much to small. We can keep that but heartrate needs to be a selectable value for one of the bigger fields
  • current day time (clock), must always be visible
  • battery level of heartrate device

By the way, how is it looking in map mode?
 

The Following 3 Users Say Thank You to jdrescher For This Useful Post:
Posts: 3 | Thanked: 17 times | Joined on Nov 2017
#12
Originally Posted by jdrescher View Post
The major problem is that I might not be able to do things on that dialog because it is no longer my code. I have a lot of ideas for it and I would have to work through your code to implement them.
Well, I have no objection if you change my code, in the end you are the maintainer
I would just try to keep the code simple, though powerful enough for the user to change it to their preferences.

Originally Posted by jdrescher View Post
f you really want to we can use your design although I really liked mine. But we have to make a few adjustments.
The plan is to make the view configurable, so that the user decides which item to display where and how many columns are occupied by an item.

Originally Posted by jdrescher View Post
Here are my points:
  • the heartrate field with the bar graph is much to small. We can keep that but heartrate needs to be a selectable value for one of the bigger fields
  • current day time (clock), must always be visible
  • battery level of heartrate device
There are several options for this. One is a status bar at the top, which would contain the current clock and GPS signal strength. I think this information do not need as much space as the field with the other information. The battery level of the heart rate device could also went to this status bar.

Alternatively, the heart rate field could contain a bar with the percentage of the battery.

At the moment all fields have the same QML element, but this is not necessary, it would also be possible to have a custom element for some/all fields.

What do you think?

Originally Posted by jdrescher View Post
By the way, how is it looking in map mode?
At the moment it would occupy two rows and would be on top of the grid. First I had in within the grid and reduced the fields to three rows, but I thought it might be better on top of the grid with the possibility to slide it to the top.

I would keep the button at their position, because it's easier to reach and you do not need to look for the buttons because the map moved them up. I don't have strong feelings about this though.
Attached Images
 

Last edited by hias; 2017-11-15 at 20:44. Reason: screenshot
 

The Following 3 Users Say Thank You to hias For This Useful Post:
Posts: 23 | Thanked: 94 times | Joined on Apr 2017
#13
So new release 0.9.6-7 is out now.

Next release will be Pebble integration and maybe some small other things.
Then I am planning to integrate OSMScoutServer for the map.

By the way, the map plugin seems to be buggy, has anyone seen those horizontal lines on the map while recording? At the moment I have no idea what to do about them. The track points added to the mappolyline are OK. They mostly appear when the map is in small mode. Maybe it is some scaling issue

 

The Following User Says Thank You to jdrescher For This Useful Post:
Community Council | Posts: 4,142 | Thanked: 9,968 times | Joined on May 2012 @ Southerrn Finland
#14
Originally Posted by jdrescher View Post
By the way, the map plugin seems to be buggy, has anyone seen those horizontal lines on the map while recording? At the moment I have no idea what to do about them. The track points added to the mappolyline are OK. They mostly appear when the map is in small mode. Maybe it is some scaling issue
Yeah, the same thing happens with Rena too. Since it does not affect the actual stored data and after recording the tracks are clean I just have learned to live with it.
 
Posts: 168 | Thanked: 729 times | Joined on Dec 2014 @ Earth
#15
So weird "off by 1" in the display code ?

(e.g.: trying to link one more point on the spline than there are data points, and thus having something with weird coordinates)

(that could typically happen in bicubic smoothing routine : to draw a spline between "point(0)" and "point(1)", you also need "point(-1)" and "point(2)" for the bicubic computations. Those might not even exist in the data array).
 

The Following 2 Users Say Thank You to DrYak For This Useful Post:
Posts: 93 | Thanked: 186 times | Joined on Oct 2010
#16
Originally Posted by jdrescher View Post

By the way, the map plugin seems to be buggy, has anyone seen those horizontal lines on the map while recording?
the same happens on Meerun regularly, too.
As others wrote, stored data is fine and closing and re-opening map view gets everything straight again.
 

The Following 2 Users Say Thank You to Casanunda For This Useful Post:
Reply

Tags
heart rate, running, sport, sport tracker

Thread Tools

 
Forum Jump


All times are GMT. The time now is 19:48.