BREW UI Widgets 2.0 abnormal behaviour | developer.brewmp.com BREW UI Widgets 2.0 abnormal behaviour | developer.brewmp.com

Developer

BREW UI Widgets 2.0 abnormal behaviour

:) Hey guys,

Facing some probs for quite sometime now, I have UI Widgets 2.0.0 & 1.2.3 installed on my machine. BUITDIR set to 2.0.0.

Issues go as :-

1. CreateInstance returns ECLASSNOTSUPPORT when I try to create an instance of Widgets, XYContainer. Then when I use the classIDs AEECLSID_WIDGET_1, ie say, AEECLSID_XYCONTAINER_1, it works, but has random behaviour on the form. At times, it gets displayed, while there are times when the application crashes when I try to push the associated form on the rootform. Moreover, in 2.0 we need to include the bid files as well for the predefined widgets. Below are some of them included as:-

#include "AEECLSID_ROOTFORM.bid"
#include "AEECLSID_LISTFORM.bid"
#include "AEECLSID_IMAGESTATICWIDGET_1.bid"
#include "AEECLSID_XYCONTAINER_1.bid"
#include "AEECLSID_PROPCONTAINER_1.bid"
#include "AEECLSID_MENUMODEL_1.bid"
#include "AEECLSID_LISTFORM.bid"
#include "AEECLSID_IMAGESTATICWIDGET_1.bid"
#include "AEECLSID_STATICWIDGET_1.bid"
#include "AEECLSID_FORM.bid"
#include "AEECLSID_XYCONTAINER_1.bid"
#include "AEECLSID_LISTWIDGET_1.bid"
#include "AEECLSID_IMAGEWIDGET.bid"
#include "AEECLSID_IMAGEWIDGET_1.bid"
#include "AEECLSID_STATICWIDGET.bid"
#include "AEECLSID_XYCONTAINER.bid"
#include "AEECLSID_POPUPMENUFORM_SCROLL.bid"

What exactly is the significance of two class IDs correspoding to a single widget. Or is it that we have two types of XYContainers over here?

2. A compiled DLL on one machine runs fine with the same SDK & UI Widgets version (3.1.5/2.0) while, on other machines, the create instances for some widgets fail.

3. When I place the application in the "examples" folder in BUITDIR, the frequency of random behaviour reduces. ie most of the times, it works fine, but on my mate's machine, it fails every time.

Any pointers would be appreciated.

-Best Regards
Robin

Are you sure Widgets works with SDK 2.0 ?

Are you sure Widgets works with SDK 2.0 ?

Hi Robin,,
I faced the same problem.. It seems the qualcomm guys kindof re-desinged the ClassIDs architecture.. and also changed the class ids for most of the classes.
In order to provide backward compatibility have had to renamed the old class ids with _1 postfix. If some of the classes are not able to get created or if you get an Error of EClassNotsupported.. it means you class id is not found in the .mif file. Make sure all the class ids are included in the .mif file.
And yaa.. the major difference in BUIW200 is the exclusion of class ids from the AEE_xxx files and adding them into the widgets header files.. From now on.. we have to manually include both AEE_XX and .bid files for accessing the class ids..
By the way.. are you using BUIW 201 or BUIW 200.. i hear the BUIW 200 is very unstable or something i am not sure thou..

Hi Robin,,
I faced the same problem.. It seems the qualcomm guys kindof re-desinged the ClassIDs architecture.. and also changed the class ids for most of the classes.
In order to provide backward compatibility have had to renamed the old class ids with _1 postfix. If some of the classes are not able to get created or if you get an Error of EClassNotsupported.. it means you class id is not found in the .mif file. Make sure all the class ids are included in the .mif file.
And yaa.. the major difference in BUIW200 is the exclusion of class ids from the AEE_xxx files and adding them into the widgets header files.. From now on.. we have to manually include both AEE_XX and .bid files for accessing the class ids..
By the way.. are you using BUIW 201 or BUIW 200.. i hear the BUIW 200 is very unstable or something i am not sure thou..

I am completely new to Brew.
Can anyone please guide me how to create Forms in Brew?like creating 2 textfield and entering some data into it.Also,put a command action into that.

I am completely new to Brew.
Can anyone please guide me how to create Forms in Brew?like creating 2 textfield and entering some data into it.Also,put a command action into that.