App
DIY Data Field (public beta)
開発者 easuvorov · v0.82 public beta
評価
4.9
レビュー
111
ダウンロード
1,000
価格
無料
説明
Namely 'Design It Yourself' data field. You can access Data Field Designer by clicking "Get the hardware" button, This is a matter of convenience as pasting link in description caused wrong redirect. To transfer settings from designer to watch app, press Import/Export button and sequentially copy/paste definition lines into Garmin Express/Mobile settings for DIY Data Field (please, let me know whether this process is ambiguous, I'll make a short clip to explain how to do that). Disclaimer: Application has hundreds of use-cases due to fully user-configurable setup, therefore it is prone to bugs. This project is not sponsored and I'm the only developer working on it in my own free time. Although I'd gladly accept reasonable criticism and improvement suggestions, I do not guarantee that bugs will be fixed and new features added in a timely manner/at all due to the fact, that I do not work on this project full time. If this approach is not acceptable for you, then, please, do not leave bad reviews just because I didn't resolve your specific case. Thanks for understanding. The data field layout is completely configurable via web app, watch application serves as a receptacle for the configuration string. Settings are transferred via any applicable method: using Garmin Express for PC or Garmin Mobile for the specific mobile device platform. If you experience crashes, then it's enough to send me definition along with watch model and, if possible, contents of /GARMIN/APPS/LOGS/CIQ_LOG.TXT. User can design his own data field layout using three types of basic elements: data values, data graphs and graphical elements. Layout setup uses device-specific absolute coordinates and specific font sizes, therefore layout designed for semi-round watch won't look the same on the round or square watch with different fonts/resolutions. Most memory-hungry elements are data graphs and data fields with additional samples. Decreasing the graph bar width increases memory consumption significantly which may lead to "out of memory" crashes. Also this increases data field redraw time since each data graph bar needs to be drawn on screen each second. Outline option for text values helps to increase readability greatly, but GarminIQ SDK at this time doesn't provide means to draw text outline in a single pass. Current implementation draws each data value with outline nine times instead of one, therefore, please, do not abuse this feature to improve drawing routine performance or test it before using in important events to check whether resulting performance is acceptable. The bundled layout setup is the absolute maximum users of the older devices (FR23x, FR630, Fenix3 etc) can get out of this app, since in some simulator tests I got "out of memory" crashes even after sending new settings. That's also why field doesn't change layout after sending settings right away and restart of recording app is necessary. Therefore, I suggest that you consider default setup being a feature showcase and design something less memory intensive (less elements, wider graph bar widths, less samples for data values etc), although users of the newer devices have much more options to play with due to increased memory limit. I plan to add some kind of estimated memory consumption metric in designer app, but I'm yet to find out how to calculate it. Default setup tested on physical FR230 consists of 26 mixed type elements and seems to be rather stable despite peak memory consumption reported in simulator is 15.9/16kb of available memory. Forum thread for the discussions, questions and suggestions: https://forums.garmin.com/showthread.php?377430-DIY-Data-Field&p=992103#post992103 Application is free since I do not want to spoil precious watch memory for some kind of authorization system implementation, but if you like my work and are willing to help this project evolve, then don't hesitate to visit paypal.me/EASuvorov or Paypal to twssupp0rt@gmail.com.
新機能
v.082 Designer app (please, clear your browser cache or press Ctrl+F5 in Google Chrome on app page) and modern devices: - added support for Fenix 5 Plus family; - added "Positioning" permission request to use GPS coordinates in calculations. v.081 Designer app and modern devices: - added value type categories for list readability; - added checks and parsing errors to expression builder. Cutting edge devices (Edge 820, 1000, 1030, Fenix 5x, Descent Mk1): - fixed unary minus operator processing. v.080 Designer app: - removed support of Data Graphs for legacy devices in DIY Clone B, but added lap values instead; - added separate template for Edge 820; - added basic expressions for cutting edge devices (see list below), these are the limits of this implementation: -- expression is based on existing data value of any complexity and must start with it; -- expression can be extended using simple data values (which do not require additional samples or parameters, this is current watch app design choice but can be changed in future) and math operators "+-*/"; -- expression is entered using infix notation and converted to reverse polish notation for better parsing performance on watch, it is converted back to infix notation in web app, therefore it's not guaranteed that expression displayed after save will be an exact replica of expression previously entered. -- as this functionality adds another dimension to application complexity, I suggest to send me definition and formulas as separate entities for analysis if something goes wrong. Cutting edge devices (Edge 820, 1000, 1030, Fenix 5x, Descent Mk1): - added expression parser. Modern devices: - equalized code with main app version Legacy Devices: - added support for Lap Values and Vertical Speed instead of Data Graphs for DIY Clone B. v.0782 Modern devices: - possible fix for application crash on Edge 1000. v.0781 Modern devices: - changed zero zone number/time calculation, now zero HR zone is counted starting from resting heart rate defined in watch settings (inclusive) to lower range of first HR zone (exclusive), this calculation is executed in the same block as for power zones, therefore power values should now be entered similar to HR zone range values - starting from lower range of first power zone.
レビュー
レビュー記事は近日公開予定です。