03-07-2013 04:45 AM
In another case(where I am using Picker in actual app), the problem occours when I add the Picker item in the container with GridLayout(). If I remove the GridLayout() for the container, the Picker can be added, even though does not work when clicked.
However in both the cases, I am getting the same error message!
The day is turning to be useless with this problem and can't move forward :-(
03-07-2013 04:57 AM
Unless you have the source code for the BB10 components you can't be sure which of them do or don't call the ANE. Maybe the picker is the only one in your example app that calls the ANE.
Try running on the simulator.
03-07-2013 05:08 AM
I am doubtful about this!
But as in another case, I am not even able to compile the app if I add the Picker in container with Gridlayout! This gives me the same error.
I am surprised at the error as it refers to some workplace of 'hudson' on E drive, which I am not. May be some issue with the component itself!
03-07-2013 05:16 AM
That reference to hudson is probably a path to a CI server in BlackBerry
but I don't know why the production ANE needs to keep these references, since we don't get to have
the source code and the line numbers in the stack traces are therefore practically meaningless to us.
Suggest you take whatever variation of your app that compiles correctly with a Picker but fails to
run on your desktop, and generate the bar correctly (include the ANE) and run it on the simulator.
03-07-2013 05:28 AM
Major issue, can't get the Simulator working at first place due to Graphics card and can't do much due to some other environment contraints at work place!
So always developed apps in Flash and tested in desktop and then on Dev Aplha, every time is worked perfectly till this Picker issue.
And I am so lucky() that I returned my Dev Alpha just yesterday!
03-07-2013 05:43 AM
Sounds like getting your simulator issue resolved should be top priority.
My understanding is that there's no desktop implementation in the ANE's supplied with the BB10 AIR SDK.
Which would mean you can't iterate on your UI in the desktop Flash player.
Anyone who knows for sure who happens to read this - please chime in.
03-07-2013 05:49 AM
Thanks for the continus follow up, regarding the components and UI, I will add another post which would be quite interesting again!
But I still feels, there might be some issue with the component, I may be wrong though!
03-07-2013 01:02 PM