Ticket Created
over 3 years ago

WERETECH-12194

It's impossible to change settings order or hide properties

If I want to disable such properties for some devices I can change it to read only or have to modify list and put settings in device's resource directory.

But position is the same like in default settings.xml.

It'd useful to:

- add flag hide for all types of properties (I don't know what is a problem to add read only to lists) or

- add functionality to define order of settings - the simplest order should be defined by properties.xml not settings.xml so I can add files to device's resource directory and in

-- properties.xml is order and vdef values

-- settings.xml only change view

Now, user have to see and scroll for settings that are not for him (if there will be no hiding I want to move properties to the end pf settings).

_psx_
  • over 2 years ago

    I've also noticed this: I thought that if I have resources/settings.xml and resources-memory32K/settings.xml and the latter is added to the resources for the devices that have at least 32K DF memory, and then the 2nd file overrides the 1st one. However this is not the case, the filename is not taken into account, and all the settings in the 2nd file that are not in the 1st file are added at the end of the settings page.

    However I found a workaround:
    I moved resources/settings.xml to resources-memory16K/settings.xml and set in monkey.jungle:

    base.resourcePath = $(base.resourcePath);resources-memory32K

    and for all the devices with only 16K DF memory:
    fenix3.resourcePath = resources;resources-memory16K/resources

    This way every devise only loads exactly one settings.xml, and in that I can have the exact things in the exact order I prefer.