• Replies 5 replies
  • Subscribers 20 subscribers
  • Views 868 views
  • Users 0 members are here
Options
Related

Different mc files for devices with more memory

hundsmiachn
over 4 years ago

Hi

I saw that it is possible, do include different source files for different devices with the jungle file. But I could find a "option" to select devices with "much" memory vs devices with "less" memory.

I want to add some features for devices > 32kb. How could I seperate the .mc files for such devices?

thanks

regards

Erich

  • over 4 years ago

    Jungles is the way to do this.  Here's part of a jungles file I use to handle devices with and without native maps:

    project.manifest = manifest.xml
srcBase=source
resBase=resources

#maps Stuff - default is no maps
base.sourcePath=$(srcBase);source-nomaps
base.resourcePath=$(resBase)

#devices with maps
fenix5x.sourcePath = $(srcBase);source-maps
fenix5x.resourcePath = $(resBase);resources-maps

    I have a source and resources directory with common code, and source-nomaps and source-maps for the unique code, and resources-maps for the extra resources for maps.

    For some things, you can also use excludeAnnotaions in the jungles file:

    base.excludeAnnotations=useScreenButton
oregon7xx.excludeAnnotations=noScreenButton

    In this case, I have screen buttons but only on an Oregon

  • over 4 years ago in reply to jim_m_58

    Yeah - unfortunately there is no family to apply a source tree to all devices with less than 30kb of data field memory, or all devices with touch screens, or all devices with 4 bits of color depth, etc. the memory family would be particularly helpful. So my jungle file hard codes the list of all 33 devices with < 30kb and don’t load my custom fonts and a few other features.

  • over 4 years ago in reply to DaveBrillhart

    Thanks for your replies. So, I did it the other way around, I defined the "high" memory devices with 64k or more.

    Wasn't that much effort as I thought it would be.

    Thanks for the help!

    project.manifest = manifest.xml

base.sourcePath = source;source-low

fr245m.sourcePath = source;source-hig
fr645m.sourcePath = source;source-hig
d2charlie.sourcePath = source;source-hig
d2delta.sourcePath = source;source-hig
d2deltapx.sourcePath = source;source-hig
d2deltas.sourcePath = source;source-hig
descentmk1.sourcePath = source;source-hig
edge1030.sourcePath = source;source-hig
edge1030bontrager.sourcePath = source;source-hig
edge520plus.sourcePath = source;source-hig
edge530.sourcePath = source;source-hig
edge820.sourcePath = source;source-hig
edge830.sourcePath = source;source-hig
edgeexplore.sourcePath = source;source-hig
edge_1000.sourcePath = source;source-hig
fenix5plus.sourcePath = source;source-hig
fenix5splus.sourcePath = source;source-hig
fenix5x.sourcePath = source;source-hig
fenix5xplus.sourcePath = source;source-hig
fenix6pro.sourcePath = source;source-hig
fenix6spro.sourcePath = source;source-hig
fenix6xpro.sourcePath = source;source-hig
fr945.sourcePath = source;source-hig
gpsmap66.sourcePath = source;source-hig
gpsmap86.sourcePath = source;source-hig
marqadventurer.sourcePath = source;source-hig
marqathlete.sourcePath = source;source-hig
marqaviator.sourcePath = source;source-hig
marqcaptain.sourcePath = source;source-hig
marqcommander.sourcePath = source;source-hig
marqdriver.sourcePath = source;source-hig
marqexpedition.sourcePath = source;source-hig
oregon7xx.sourcePath = source;source-hig
rino7xx.sourcePath = source;source-hig
epix.sourcePath = source;source-hig

  • over 4 years ago in reply to DaveBrillhart

    families could get kind of crazy as you'd want multiples for 16k, 32k, 64k etc just for DFs, but you'd also need the same for widgets, watch faces, device apps etc.