Warning during packaging and application icon is not displayed if 2 icons are specified in config.xml #125

Closed
ishneur opened this Issue May 3, 2012 · 8 comments

Projects

None yet

5 participants

@ishneur
ishneur commented May 3, 2012

Description:

  1. Specify 2 icons in config.xml, e.g.:
    <icon src="img/state/default_i_off.png" />
    <icon src="img/state/default_i_on.png" rim:hover="true" />
  2. Build the app

The following warning is displayed twice during packaging:
[WARN] Warning: Cannot find application or default icon

Also, after the application is installed, its icon does not appear.

This issue could be resolved once the following user story is implemented: #110

Attachment: https://github.com/downloads/blackberry-webworks/BB10-Webworks-Packager/GHI125.zip

Build: \CI0000000094259.rim.net\Share\SCM Builds\BlackBerry Webworks SDK for BB10 1.0.0 Bundle 7

@nukulb
nukulb commented May 4, 2012

@ishneur instead of putting links to issues you should refer to them using this syntax - blackberry/BB10-Webworks-Packager#110.
This creates a link in the issue you refering to so, when someone looks at the User Story they will know that you are expecting this bug to fixed with it. Let me know if you have questions regarding this.

@astanley
astanley commented May 7, 2012

Thanks for filing this.

Workaround:
Remove the second <icon> element from the config.xml file:

<icon src="img/state/default_i_on.png" rim:hover="true" />

Note: Any developer trying to build the bbUI.js sample application will currently encounter this issue.

@kwallis
Member
kwallis commented Jul 12, 2012

I assume this is no longer an issue with this release?
@rwmtse

@ishneur
ishneur commented Jul 12, 2012

It doesn't happen anymore in SCM build 1.0.1.4.

I my config.xml I specified this:
<icon src="tire.png" />
<icon src="bulbon.gif" rim:hover="true" />

There were no warnings during packaging.

At runtime, it shows the second icon (bulbon.gif) and not the first one. These icons differ in size - tire.png is 64x64 and bulbon.gif is 100x180, maybe that's the reason.

@astanley

Curious if bulbon.gif would still be selected if the ordering of the elements was reversed? If it is bigger, then I kind of hope it will continue to be chosen (means the packager is doing its thing and picking the best fit for the BB10 home screen).

@ishneur
ishneur commented Jul 12, 2012

It still selects bulbon.gif after I reversed the order, with or without rim:hover="true".

@kwallis
Member
kwallis commented Jul 12, 2012

This is not packager logic. This is OS level. We don't control it. The OS will choose the best fit regardless of order specified in config.xml

Ken Wallis

Product Manager – BlackBerry WebWorks

Research In Motion

(905) 629-4746 x14369


From: Igor Shneur [reply@reply.github.com]
Sent: Thursday, July 12, 2012 1:25 PM
To: Ken Wallis
Subject: Re: [BB10-Webworks-Packager] Warning during packaging and application icon is not displayed if 2 icons are specified in config.xml (#125)

It still selects bulbon.gif after I reversed the order, with or without rim:hover="true".


Reply to this email directly or view it on GitHub:
#125 (comment)


This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

@rwmtse
rwmtse commented Jul 12, 2012

BB10 packager totally ignores the rim:hover attribute, it doesn't care whether it's true or false or unspecified. And it's the BB10 OS that selects which icon to display. The packager just specifies all the icons (in the bar-descriptor.xml).

@kwallis kwallis closed this Sep 17, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment