Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Native Development

Reply
Developer
MikePembo951
Posts: 107
Registered: ‎02-15-2012
My Device: Blackberry Playbook 32GB

Frustrated

Really frustrated.

Spent about an hour wondering why my obj (wavefront) parser wasnt working properly, going over my code, reading through each source file various times only to find that the IDE isnt uploading a new version of my code. I must have rebuilt and run/debugged my app on the playbook about 6 times until I realised it was no longer uploading a new build of my app, but an old one.

 

These bugs are really annoying and debugging is really kinda slow.

 

Will any of this change to make native development easier to debug and faster to debug with the next update?

 

 

Developer
MikePembo951
Posts: 107
Registered: ‎02-15-2012
My Device: Blackberry Playbook 32GB

Re: Frustrated

[ Edited ]

* it still isnt uploading the latest build of my app, even after manual removal from playbook, clean install from IDE debug options etc.

 

All I want to do is debug my app... :/

Developer
MikePembo951
Posts: 107
Registered: ‎02-15-2012
My Device: Blackberry Playbook 32GB

Re: Frustrated

Found the problem. even though when building the IDE reported 0 problems I found that in one class I was giving a string instead of a char array...... still doesnt explain why building returned 0 problems

Developer
BGmot
Posts: 1,068
Registered: ‎11-24-2011
My Device: PlayBook

Re: Frustrated

That's impossible.

Developer
MikePembo951
Posts: 107
Registered: ‎02-15-2012
My Device: Blackberry Playbook 32GB

Re: Frustrated

well it happened. :smileyfrustrated: 

Restarted Playbook and IDE and its working now

Visitor
samarmadeh
Posts: 1
Registered: ‎08-01-2012
My Device: Bold 9790

Re: Frustrated

Hi Mike,

 

I haven't been able to reproduce the issue you're describing here on the SDK IDE version 543 now available on developer.blackberry.com. I added the below code to the main.cpp file in the  "LightningCrossfadeCPP" sample app and received a compilation error as expected. 

 

Below is a copy/paste of the code sample and the compilation error...

 

Samar

 

Code added:

int testFunction(char** testInput)

{

       return 1;

}

 

int main(int argc, char **argv)

{

    .

    .

    .

    string tests = "test";

    int result = testFunction(tests);

 

    .

    .

    .

}

 

Error received:

../src/main.cpp:39:36: error: cannot convert 'std::string {aka std::basic_string<char, std::char_traits<char>, std::allocator<char> >}' to 'char**' for argument '1' to 'int testFunction(char**)'

Developer
BGmot
Posts: 1,068
Registered: ‎11-24-2011
My Device: PlayBook

Re: Frustrated

it's legitimate error.

change

string tests = "test";

to

char *tests = "test";

 

and change

int testFunction(char** testInput)

to

int testFunction(char* testInput)

Developer
MikePembo951
Posts: 107
Registered: ‎02-15-2012
My Device: Blackberry Playbook 32GB

Re: Frustrated

I get other intermittent, problems too:

E.g.

“unable to determine returned pid from launch” when debugging. It only happens occasionally.

I think i may need to reinstall the ide.

I remember earlier in my project i was getting similar problems when compiling as in it wasnt showing me errors when there clearly were problems. I think it happens when there are quite a few problems and it just stops compiling, but even then it was only 4 problems

Developer
BGmot
Posts: 1,068
Registered: ‎11-24-2011
My Device: PlayBook

Re: Frustrated

I don't know Mike. I've never reinstalled any version of IDE to fix a problem. Seems like you iether too impatient to track down real problem and fix it or just having bad luck (it happnes). :-(
Just remember: compiling/linking problems have nothing to do with debugging. 

Developer
MikePembo951
Posts: 107
Registered: ‎02-15-2012
My Device: Blackberry Playbook 32GB

Re: Frustrated

Thanks :smileyhappy:

I think it was just bad luck, it hasnt happened since.

Hopefully can get a game out by the end of the summer.