viking --latitude Y --longitude X should take priority over Startup Method preference

[jidanni]

$ viking --latitude 14.649843 --longitude 121.074174

indeed starts in that location. But then we are quickly flown back to our local town.

$ Viking file.kmz

works flawlessly though.

$ viking --version
viking 1.10

The Edit > Set Default Location item: doesn't help.

What helps, it turns out, is choosing Edit > Preferences > Startup > Startup Method > Last Location!

But that shouldn't be necessary, as the command line should take priority.

[rnorris]

I believe this is fixed in the latest source code by commit: c6308c5b604632e2e2da224b2594162e01ffa2de However this is not in a formal release yet.