Custom Query (78 matches)

'search'->'address online' does nothing. In console it prints:

Traceback (most recent call last):
  File "/opt/modrana/modules/gui_modules/gui_gtk.py", line 485, in released
    self.click(event.x, event.y,msDuration)
  File "/opt/modrana/modules/gui_modules/gui_gtk.py", line 514, in click
    m.handleClick(x,y,msDuration)
  File "/opt/modrana/modules/mod_clickHandler.py", line 68, in handleClick
    m.routeMessage(action)
  File "/opt/modrana/modules/mod_messages.py", line 104, in routeMessage
    m.handleMessage(text, None, None)
  File "/opt/modrana/modules/mod_search.py", line 239, in handleMessage
    entry.entryBox(self, 'address',description='Enter an address or location description', persistentKey="lastAddressSearchInput")
  File "/opt/modrana/modules/mod_textEntry.py", line 101, in entryBox
    entry.set_text(initialText)
TypeError: GtkEntry.set_text() argument 1 must be string, not None

Apparently the content of /home/user/.modrana/options.bin was the problem. After patching .py to recover from it options.bin got updated and the patch is no longer needed.

I guess it probably affects only users upgrading from older versions.

• logging trace is not shown on map until a color is selected
• if a tracklog detail has been visited, the logging menu "tools" goes to tracklog detail "tools"
• logging intervals seem to be ignored
• tracklogs that are created seem to be corrupted or in wrong format

• the two geocoding address lookups are slowing down re/routing
  • most user also probably don't even check out the addresses in the route detail menu

• the geocoding should be thus triggered only when the user enters the route detail menu implemented
  • or alternatively silently in the background once route lookup finishes
  • there should be also an options to completely disable the routing related address geocoding - lower priority