This thread is where we'll report the winners of the featured discussion board post.
The Featured Discussion Board Post for 2013 Week 18 is LWUIT-TextArea-edit-on-focus-for-non-touch-devices by lordbritishix1982.
The question asks how to set a newly focussed TextArea immediately into edit mode without the user having to set the MSK first. While this use-case is not supported, the discussion is interesting because it first explains how a TextField (single line) can have the required behaviour, and then goes on to explain the behaviour of the LWUIT TextField on different devices.
For this week and next week we're awarding an Asha 311 for the Featured Discussion Board post - we'll be sending a device to lordbritishix1982 shortly!
The Featured Discussion Board Post for 2013 Week 19 is What is the difference between local preview, cloud preview and device deployment? by imgen.
Of course this is all captured in the Series 40 Web App FAQ on the wiki. We have decided to feature this question because using local preview for all testing is a common mistake for newer web app developers, and one that can cost a lot of time and effort. We hope that developers will find this interesting!
For this week we're awarding an Asha 311 for the Featured Discussion Board post - we'll be sending a device to imgen shortly!
The Featured Discussion Board Post for 2013 Week 20 is Memory Leak when removing and adding markers by tktr.
Of course the "right" solution will be a fix to the API in a future release, but in the meantime this solution allows the developer to move forward with their application.
For this week (and the next 4 weeks) we're awarding a green Lumia 620 for the Featured Discussion Board post - we'll be sending a device to tktr as soon as the order arrives (probably in the next couple of weeks).
Last edited by hamishwillee; 2013-06-11 at 01:37.
The Featured Discussion Board Post for 2013 Week 21 is Distinguishing published app from development version by influencer.
The question was about the best way to tell the difference on your phone between the current version of a published app and a new version under development - they may both have the same name and strings so it is not obvious which version to test. A number of alternatives were proposed but rejected as either too complicated or potentially error-prone at release time.
The community proposed a number of solutions ranging from pre-build and post-build steps to rename the title in release/debug, better management of the release cycle through a checklist, using different WMAppManifest files for release and debug builds and querying for WMAppPRHeader.xml which is only present in marketplace builds. We thought this was an interesting question because it is a fairly common use case where the easy and obvious solution (renaming the app during development) is also very easy to forget to change to the correct version at release time.
For this week (and the next 3 weeks) we're awarding a green Lumia 620 for the Featured Discussion Board post - we'll be sending a device to influencer as soon as the order arrives (probably in the next couple of weeks).
Last edited by hamishwillee; 2013-06-11 at 01:32.