Ticket Created
over 3 years ago

CIQSTORE-2960

new settings are not visible after downloading new version for couple of days

Why the settings are not visible after updating the application?

Even changes to the labels are not updated immediately - I had to wait 2 days to new settings.

Settings are handled online (device's settings is available from 3.2.0 cost code/memory).

- new app + new settings

- upload to store

- accepting new vesrion for downloading  - FROM THIS MOMENT NEW SETTINGS SHOULD BE READY

- users can download new app

- for couple of days users cant' use new settings or they see old labels...

It means users have to use default values hardcoded (if developer doesn't forget to handle it and it's additional waste of time/memory because default values should be always returned as defined in properties.xml but they don't or rather they are after couple of days).

_psx_
Parents
  • over 3 years ago

    "#define is important because makes code clear and save memory"

    My point was:

    - Most modern languages do not have a C-style preprocessor

    - C# only has a very limited preprocessor (no macros, just simple conditional compilation)

    - It's pretty obvious that languages have moved away from the concept of a preprocessor (and especially macro) because it can make it much harder to understand and reason about the code

    - You can easily use the C/C++ preprocessor in your own project; the downside is you have to create your own script / build system

    "save memory"

    Obviously Garmin doesn't care too much about devs saving memory, otherwise they wouldn't put application setting strings in the same resource pool as resources that the app actually needs at runtime.

Comment
  • over 3 years ago

    "#define is important because makes code clear and save memory"

    My point was:

    - Most modern languages do not have a C-style preprocessor

    - C# only has a very limited preprocessor (no macros, just simple conditional compilation)

    - It's pretty obvious that languages have moved away from the concept of a preprocessor (and especially macro) because it can make it much harder to understand and reason about the code

    - You can easily use the C/C++ preprocessor in your own project; the downside is you have to create your own script / build system

    "save memory"

    Obviously Garmin doesn't care too much about devs saving memory, otherwise they wouldn't put application setting strings in the same resource pool as resources that the app actually needs at runtime.

Children
  • over 3 years ago in reply to flowstate

    Most current software environment doesn't has limit 92kb. Disappointed

    The simplest app showing nothing takes megabytes so they don't have to think about each bytes...

    Garmin should care because

    - API is one and applications on watch many - so  each takes memory

    - loading bigger app consumes more energy