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

2016 year review and double counted activities

It’s time again to look at the past year summary. How did I do?

2016 was a fine year, I ran 1387 km, it is 100km behind 2015. But one aspect bothered me, looking at the distance, there is a clear increase on the graph in December 2015, which put me behind in 2016. It worried me a bit. I couldn’t remember an especially good December last year. Did I have another bug in ConnectStats?

I went to check on Garmin connect and it reported the same distance as connectstats: 1478km for 2015…

Hum. Next step was to go and look at the activities in December last year. The search feature in ConnectStats made it easy, just enter december 2015  in the search box of the activity list. Sure enough, I found some duplicate activities. This started to be very worrying. ConnectStats imported the same activity twice? New bug? After some more investigation, it turned out the problem was in Garmin itself… Quite a few activities in 2015 appear twice on the website as well…

They have a different activity identification number, but they are clearly the same activity except for the altitude gain as you can see on the snapshot above.

Next steps was to add a new feature to ConnectStats to double check for such duplicate activities and ignore them… Well, my stats are now lower only 1310km but correct. And 2016 is ahead of 2015 by 50km! Yeah!

I finally decided to check what Strava reported. My account is linked to import activities automatically. I was curious: would strava have the total including the duplicate as well? It actually didn’t… The total is 5km off from my new corrected total, but I suspect it is simply due to the slightly different way Strava computes the total distance from the gps file.

The fix to search and eliminate duplicate will be included in a new release early next year.

  1. Update on development and new API issues 21 Replies
  2. Yet another change of the API 11 Replies
  3. Garmin API changed again 38 Replies
  4. Fix for Connection Issue (ConnectStats 3.2.1) 32 Replies
  5. Garmin API change (again) and Connectstats is not working at the moment 19 Replies
  6. ConnectStats Version 3.2 4 Replies
  7. Exciting Bug Reports 2 Replies
  8. ConnectStats back online v3.1 23 Replies
  9. ConnectStats broken after another Garmin API change 5 Replies