MacroDial

MacroDialAppIconDescription

Macro Dial is a tool to help edit and automatically change numbers from your address book according to some rules based on the way you want to call: IDD, calling card, corporate access number, without entering multiple entry in the phonebook.

Target Users

This program is intended to be useful for

  • people who travel and need to dial the same number in diverse way, for example you dial +813 5555 5555 to call japan when you are in Hong kong, but 03 5555 5555 when you are in japan.
  • People who have access to IDD prefix code, or use carrier like softbank in japan that do not process the + as expected.
  • People who have corporate access number that require processing of the number to extract the right extension.
  • People using multiple calling card from different countries.

Goal of the design of the program

  • provide a full set of rules to make any generation of numbers possible.
  • be able to share the rules via the internet. They can be downloaded without compromising personal codes or PINs.
  • have a simple way to enter rules as well as a more advanced complete mode.
  • provide the user workflow that fitted my need.

How to use it

  • Please read the main documentation page and the information how to create new macros
  • when you start the program a wizard will let you choose a few options or package of rules. Currently only for Japan Softbank or Hong Kong three, but you can download more from the web. If you have a code (from friends or from me) you can access rules specific to a company for example.
  • After you select a contact, you can choose the number and if you click on a rule (or macro) that rule will be applied to the number.
  • No number will ever be called without you pressing the call button, so you can review to make sure the number is correct.
  • To create a new rule you can simply edit the number in the Dial screen, and if a simple way to regenerate the number is detected the program will offer to save it as a new rules.
  • If you are a more advanced user you can design your rules from the edit macro function in the setting screen.

Recent Posts

Important release to correct data import problems

A new version 4.4 is now available.

This fixes the issue around missing data on import, as well as incorrect units for some fields like min or max elevation.

Bad Release Problem Solved!

As a bonus, I added support for Garmin Device Power while running, as least for the devices for which users sent me sample fit files.

Missing Data

Because of my own silly bug, ConnectStats was not trying hard enough to look for all activities on the initial download, and was stopping too early, resulting in missing older activities. This is now fixed in 4.4. But it’s hard for the app to know if it missed old activities or not. So if you think you are in that situation, the best is to force the app to reload all activities, by going to “settings”, selecting “profile” and “Force Reload Old Activities” as below. This will start a download that will try to reload everything, it will also help fix data previously imported with incorrect units.

 

Incorrect Units

Even though I have build a lot of tests over time, it is always difficult to make sure when a new API changes that the app is behaving properly. This is due to the fact that the API is undocumented and that I have limited scope for testing of new features, given that I do it on my own. I basically only test on my activities and the activities people have sent me over time in the past. Though we should not complain about the lack of documentation given as mentioned in the past, this API is not intended for external use, but just for garmin own website… So I am just grateful Garmin lets ConnectStats continue to use it, even if we just have to reverse engineer everything.

To illustrate the issue and give people a feel for the reason behind some of the bugs, the bad units were due to inconsistencies in the scale of the number depending on which data you were receiving: summary or detail for an activity.

In the summary the elapsed duration data comes as milliseconds:

While in the detail file it comes as seconds…Beside the elapsedDuration, maxElevation and minElevation everything else is consistent… Go figure… These are hard to anticipate and catch when you test on your own, so I want to thank all the users who have the patience to report details about such bugs and also the patience to wait for me to push fixes.

 

  1. Missing activities bug 2 Replies
  2. Power Hiking with @strydrunning now in @ConnectStats Leave a reply
  3. What the Alternative API mean for ConnectStats 5 Replies
  4. Activities not updating, how to fix… 6 Replies
  5. Similar Summary Stats, Different effort… 2 Replies
  6. ConnectStats now supports #RunningWithPower for @Strydrunning! 11 Replies
  7. Another turning point for ConnectStats? 22 Replies
  8. ConnectStats is now open source 1 Reply
  9. Garmin API Change: Good News Bad News 5 Replies