SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and now iOS Charting & Android Chart Components
Please use the forums below to ask questions about SciChart. Take a moment to read our Question asking guidelines on how to ask a good question and our support policy. We also have a tag=SciChart on Stackoverflow.com where you can earn rep for your questions!
Please note: SciChart team will only answer questions from customers with active support subscriptions. Expired support questions will be ignored. If your support status shows incorrectly, contact us and we will be glad to help.
I am building an iOS framework that sits on top of SciChart for app developers within our company. I’d like to provide my own default SCIThemeColorProvider object for charts in my framework. Easiest way to do that is to include my own theme plist in my framework’s bundle, but I cannot currently do that (as of 22.214.171.1243) because the SCIThemeColorProvider initializer assumes it’s either in the “Charting.SciChart” bundle or the main bundle.
I’d like to propose modifying SCIThemeColorProvider to add another initializer that takes a bundle ID, like this:
/** * Creates theme provider based on specified style * * @param themeKey The key of style which should be used as base for this theme provider * * @param bundleIdentifier The identifier of the bundle containing the theme plist identified by * themeKey; if nil, the main bundle is used. */ - (nullable instancetype)initWithThemeKey:(nonnull NSString*)themeKey bundleIdentifier:(nullable NSString*)bundleIdentifier;
The existing -initWithThemeKey: initializer would call through to this initializer with a nil bundle ID.
I have attached a patch file with this proposed change. Could this be added to an upcoming build?
I’m assuming you’re a customer of SciChart iOS with source code as you’ve patched our code!
The best way to do this is to submit a pull request via Github. So on the SciChart iOS repository, fork (branch) our code, make your change, and commit it and submit a pull request.
For info see Submit a Pull Request in Github.
From there we can integrate changes quite easily into the iOS Framework – if it doesn’t break the build or break functionality of course!
Please login first to submit.