As a workaround for your situation, you can download the same assets and sheet info (link to Dropbox below) and basically use them to set a custom theme, similar to how you’d do a custom theme with your own assets, except that these are the “official” iOS7 assets.
If you do this, make sure to use a unique theme name like “widget_theme_ios7_newsuffix”, so it doesn’t attempt to load the default from the core.
I think that did the trick … i’ll do a bit more testing to make sure but i added
package.preload.widget_theme_ios7 = nil
package.preload.widget_theme_ios7_sheet = nil
to my main and then dropped the ios7 files in without changing their names. They appear to be picking up the @2x images in the simulator … a good sign.
Thanks
Will report back if i uncover something not working.
I was going to suggest that as well, but I wasn’t sure you wanted to tinker with the “package.preload” thing. Let me know if anything goes awry with this.
As a workaround for your situation, you can download the same assets and sheet info (link to Dropbox below) and basically use them to set a custom theme, similar to how you’d do a custom theme with your own assets, except that these are the “official” iOS7 assets.
If you do this, make sure to use a unique theme name like “widget_theme_ios7_newsuffix”, so it doesn’t attempt to load the default from the core.
I think that did the trick … i’ll do a bit more testing to make sure but i added
package.preload.widget_theme_ios7 = nil
package.preload.widget_theme_ios7_sheet = nil
to my main and then dropped the ios7 files in without changing their names. They appear to be picking up the @2x images in the simulator … a good sign.
Thanks
Will report back if i uncover something not working.
I was going to suggest that as well, but I wasn’t sure you wanted to tinker with the “package.preload” thing. Let me know if anything goes awry with this.
Just curious, is the workaround not doing what it should? I haven’t brought this up to the engineers recently, but I think a true fix (as in, adding some kind of way to specify the custom suffix) isn’t a high priority among other issues at this point. However, if the workaround isn’t functioning, then it would become a higher priority.
Yes, I know it would be ideal to have this properly addressed, and I can attempt to bump it with the engineers. By the way, where do we document that a custom suffix is allowed? If we do, I’d like to add some clarification or even highlight this workaround as a potential solution at this time.
Just curious, is the workaround not doing what it should? I haven’t brought this up to the engineers recently, but I think a true fix (as in, adding some kind of way to specify the custom suffix) isn’t a high priority among other issues at this point. However, if the workaround isn’t functioning, then it would become a higher priority.
Yes, I know it would be ideal to have this properly addressed, and I can attempt to bump it with the engineers. By the way, where do we document that a custom suffix is allowed? If we do, I’d like to add some clarification or even highlight this workaround as a potential solution at this time.
Let me know if anything goes awry with this.