You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello TomSchimansky, just starting with github. So i dont know if this is the right way......
Using your nice Widget with offline tiles, i just found an mistake in offline_loading.py
In procedure save_offline_tiles at updating the section-table in the database, you defines both, position_a and position_b in the
sql-query to point at position_b.
This, i think, has to be corrected to str(position_a), str(position_b)........
Furtheron, as i uses an tile-server on localhost (using python -m http.server) for creation of the offline database,
i have to set the tile-server of the map-widget when using the pre created database to the same tile-server string as for creating.
Otherwise the tiles in the database wont be found, cause of the init of tile-server-string to openstreetmap.
Sorry, gerade erst den Github Account erstellt. Danke auf jeden Fall für das Widget.
The text was updated successfully, but these errors were encountered:
Hello TomSchimansky, just starting with github. So i dont know if this is the right way......
Using your nice Widget with offline tiles, i just found an mistake in offline_loading.py
In procedure save_offline_tiles at updating the section-table in the database, you defines both, position_a and position_b in the
sql-query to point at position_b.
insert loading section in database
This, i think, has to be corrected to str(position_a), str(position_b)........
Furtheron, as i uses an tile-server on localhost (using python -m http.server) for creation of the offline database,
i have to set the tile-server of the map-widget when using the pre created database to the same tile-server string as for creating.
Otherwise the tiles in the database wont be found, cause of the init of tile-server-string to openstreetmap.
Sorry, gerade erst den Github Account erstellt. Danke auf jeden Fall für das Widget.
The text was updated successfully, but these errors were encountered: