Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

Hmm something strange is happening here..

I'm developping an 1.1 app, but used until now the 2.1 emulator (more debugging stuffs inside) - But when i try to run my app under the 1.1, it hangs up, just a blank screen. Tried to trace the thingie, but the emulator doesn t call my code..
The funny thing is that everything works properly on the phone..

Any idea?

Greets,

/David

maybe the en folder ?

maybe the en folder ?

What do you mean?

What do you mean?

when loading the applet on the emulator you have to set the mif folder and the applet folder
in the applet folder you should have another folder with the same name that the mif file has and another folder "en"
got it ?

when loading the applet on the emulator you have to set the mif folder and the applet folder
in the applet folder you should have another folder with the same name that the mif file has and another folder "en"
got it ?

My directories settings are ok (mif/applet), i added the en directory, but that doesnt make any change :(

My directories settings are ok (mif/applet), i added the en directory, but that doesnt make any change :(

well, the en should have something inside it, try to copy the one inside the brew exemples folder

well, the en should have something inside it, try to copy the one inside the brew exemples folder

Tried it, copied my bar in every directory, but still doesn t work..
(and i reinstalled everyting, brew sdk aso..)
Weird..
/kUfa

Tried it, copied my bar in every directory, but still doesn t work..
(and i reinstalled everyting, brew sdk aso..)
Weird..
/kUfa

what do you mean? is this happenning with all app's or with just this one?

what do you mean? is this happenning with all app's or with just this one?

Just with mine.. i checked the mif alot of time, i m using the right headers.. well, dont know..
(and i don t have any spaces in the directories names)

Just with mine.. i checked the mif alot of time, i m using the right headers.. well, dont know..
(and i don t have any spaces in the directories names)

Oddly enough, I'm having a very similar problem. I've made several apps that all work fine under 1.1 and 2.0 emus, but for some reason this one specific app doesn't work on the 1.1 emu. The exact same MIF/DLL/BAR functions properly on the 2.0 emu, and the code works fine on the actual 1.1 phone (T720).
When I launch the app, it crashes the emu and it does it before ever seeing any of my code (including constructors). The only thing I can figure is that there's a link/compile problem of some kind, but so far I've been unable to figure it out. On the chance that I'd screwed up a setting, I recreated the project from scratch again and I still get the same problem.
My next step is to go through and start commenting out / removing code until the problem goes away and I can launch but this is just dang weird.
Tom

Oddly enough, I'm having a very similar problem. I've made several apps that all work fine under 1.1 and 2.0 emus, but for some reason this one specific app doesn't work on the 1.1 emu. The exact same MIF/DLL/BAR functions properly on the 2.0 emu, and the code works fine on the actual 1.1 phone (T720).
When I launch the app, it crashes the emu and it does it before ever seeing any of my code (including constructors). The only thing I can figure is that there's a link/compile problem of some kind, but so far I've been unable to figure it out. On the chance that I'd screwed up a setting, I recreated the project from scratch again and I still get the same problem.
My next step is to go through and start commenting out / removing code until the problem goes away and I can launch but this is just dang weird.
Tom

maybe you saved your .MIF file as a 2.0, so a 1.1 won´t open and 2.0 will..
try opening it and certify that you save as 1.1 mif file.

maybe you saved your .MIF file as a 2.0, so a 1.1 won´t open and 2.0 will..
try opening it and certify that you save as 1.1 mif file.

Quote:Originally posted by Marcel
maybe you saved your .MIF file as a 2.0, so a 1.1 won´t open and 2.0 will..
try opening it and certify that you save as 1.1 mif file.
I should have mentioned it .. that was the first thing I checked ;)
Tom

Quote:Originally posted by Marcel
maybe you saved your .MIF file as a 2.0, so a 1.1 won´t open and 2.0 will..
try opening it and certify that you save as 1.1 mif file.
I should have mentioned it .. that was the first thing I checked ;)
Tom

Hehe do not worry, my mif is a 1.1 mif (checked alot of times, and otherwise it would not run on the phone..)
The strange thing: i copied the mif, made a new app (kept the same startup routine etc), modified the bid and the app name.. the new app works properly... weird..

Hehe do not worry, my mif is a 1.1 mif (checked alot of times, and otherwise it would not run on the phone..)
The strange thing: i copied the mif, made a new app (kept the same startup routine etc), modified the bid and the app name.. the new app works properly... weird..

Brew == weird
The same thing happend to me. I created a new project for the 1.1 version (from the scratch) with a different mif and bid and I worked, just like you. Do not ask me why.
Chocksmith

Brew == weird
The same thing happend to me. I created a new project for the 1.1 version (from the scratch) with a different mif and bid and I worked, just like you. Do not ask me why.
Chocksmith

Lol yeah probably :P

Lol yeah probably :P

Add me to the list of people this has happened to.
My app was working fine, but in the midst of some restructuring, I moved the app to a new directory. Same code, for the most part, same bids, same bars, same mif, same dll location relative to the mif, and all I get is a blank screen on the emulator. It doesn't even have the little Configure applet.
The only thing I can think of is that maybe it gets stuck loading the dll, which did change slightly in the restructuring. Works fine with the other emulators, though.

Add me to the list of people this has happened to.
My app was working fine, but in the midst of some restructuring, I moved the app to a new directory. Same code, for the most part, same bids, same bars, same mif, same dll location relative to the mif, and all I get is a blank screen on the emulator. It doesn't even have the little Configure applet.
The only thing I can think of is that maybe it gets stuck loading the dll, which did change slightly in the restructuring. Works fine with the other emulators, though.

I wonder if it could be some trouble in the way the dll is constructed, and then loaded.. maybe a bug in emulator 1.1 ?

I wonder if it could be some trouble in the way the dll is constructed, and then loaded.. maybe a bug in emulator 1.1 ?

That's what I'm thinking. I have no idea what sets it off, though.

That's what I'm thinking. I have no idea what sets it off, though.

Couple o suggestions.
Try compiling w/ the 1.1 sdk.
Check the Mif, and save it as 1.1 (Some ppl did)
Make sure your not using any 2.0 calls (STRTOWSTR is 2.0, STR_TO_WSTR is 1.0)

Couple o suggestions.
Try compiling w/ the 1.1 sdk.
Check the Mif, and save it as 1.1 (Some ppl did)
Make sure your not using any 2.0 calls (STRTOWSTR is 2.0, STR_TO_WSTR is 1.0)

Of course i compile with the 1.1 SDK, my mif is 1.1, and i do not make ANY 2.0 calls (well, without the 2.0 headers.. and it would nt run on the phone!)

Of course i compile with the 1.1 SDK, my mif is 1.1, and i do not make ANY 2.0 calls (well, without the 2.0 headers.. and it would nt run on the phone!)

Precisely the same here; all we're doing is taking 1.1 code, mif, what have you and running it in the 2.x emulator. It's not a code version issue.

Precisely the same here; all we're doing is taking 1.1 code, mif, what have you and running it in the 2.x emulator. It's not a code version issue.

I've had this problem before too, just can't remember what we did to solve it...
FYI: I do all my stuff in the 2.0 emulator, dosen't matter if it's a 1.0/1.1/2.0 phone.
:(
If I rembere what it was i'll post back.

I've had this problem before too, just can't remember what we did to solve it...
FYI: I do all my stuff in the 2.0 emulator, dosen't matter if it's a 1.0/1.1/2.0 phone.
:(
If I rembere what it was i'll post back.

Quote:My app was working fine, but in the midst of some restructuring, I moved the app to a new directory. Same code, for the most part, same bids, same bars, **same mif**,
Here's a shot in the dark. I'm thinking it has something to do with the same class ID being used twice. Do you have two uniquely-named mif's sharing a class ID and residing in the .mif directory? Are the old and new versions both in the same applet directory and using identical .bids? When switching Emulator versions, I assume that different mif and applet directories are used and the problem does not recur as a result.
Like I said, it's a shot in the dark!

Quote:My app was working fine, but in the midst of some restructuring, I moved the app to a new directory. Same code, for the most part, same bids, same bars, **same mif**,
Here's a shot in the dark. I'm thinking it has something to do with the same class ID being used twice. Do you have two uniquely-named mif's sharing a class ID and residing in the .mif directory? Are the old and new versions both in the same applet directory and using identical .bids? When switching Emulator versions, I assume that different mif and applet directories are used and the problem does not recur as a result.
Like I said, it's a shot in the dark!

I haven't tried this, this is a Santiago Nasar style shot in the dark...
Maybe there's some mif or directory state hiding in the emulator's prefs.dat file. Try wiping it out, er, I mean backing it up somewhere and moving it out from where the emulator expects it.
-Jesse

I haven't tried this, this is a Santiago Nasar style shot in the dark...
Maybe there's some mif or directory state hiding in the emulator's prefs.dat file. Try wiping it out, er, I mean backing it up somewhere and moving it out from where the emulator expects it.
-Jesse

Quote:Originally posted by Murray Bonner
Here's a shot in the dark. I'm thinking it has something to do with the same class ID being used twice.
Nope, that ain't it. There's only one .mif in my directory, and that one uses three class IDs in three .bids, all retrieved from the web site. No clash there.
Quote:Are the old and new versions both in the same applet directory and using identical .bids?
There's only one version, developed for 1.1, tested in multiple emulators.
Quote:When switching Emulator versions, I assume that different mif and applet directories are used and the problem does not recur as a result.
Nope; each emulator uses exactly the same mif and applet directories. The problem lies elsewhere.
Quote:Originally posted by jhw
Maybe there's some mif or directory state hiding in the emulator's prefs.dat file. Try wiping it out, er, I mean backing it up somewhere and moving it out from where the emulator expects it.
Just tried it, didn't work.
Ah, well; it doesn't much matter, anyway, so long as the applet works in the other emulators and on the phone itself.

Quote:Originally posted by Murray Bonner
Here's a shot in the dark. I'm thinking it has something to do with the same class ID being used twice.
Nope, that ain't it. There's only one .mif in my directory, and that one uses three class IDs in three .bids, all retrieved from the web site. No clash there.
Quote:Are the old and new versions both in the same applet directory and using identical .bids?
There's only one version, developed for 1.1, tested in multiple emulators.
Quote:When switching Emulator versions, I assume that different mif and applet directories are used and the problem does not recur as a result.
Nope; each emulator uses exactly the same mif and applet directories. The problem lies elsewhere.
Quote:Originally posted by jhw
Maybe there's some mif or directory state hiding in the emulator's prefs.dat file. Try wiping it out, er, I mean backing it up somewhere and moving it out from where the emulator expects it.
Just tried it, didn't work.
Ah, well; it doesn't much matter, anyway, so long as the applet works in the other emulators and on the phone itself.

there are programmers who are creating wonders ...and you guys r mulling over bugs introduced by yourselves :) ...
dont blame brew :))
post your code ...put your app as attachment, i will b more than happy to debug it for you :D

there are programmers who are creating wonders ...and you guys r mulling over bugs introduced by yourselves :) ...
dont blame brew :))
post your code ...put your app as attachment, i will b more than happy to debug it for you :D

Quote:and you guys r mulling over bugs introduced by yourselves
Well you can find the code, it's the HelloWorld in the SDK...
Quote:put your app as attachment, i will b more than happy to debug it for you
Hehe code ripping is bad :P
/kUfa

Quote:and you guys r mulling over bugs introduced by yourselves
Well you can find the code, it's the HelloWorld in the SDK...
Quote:put your app as attachment, i will b more than happy to debug it for you
Hehe code ripping is bad :P
/kUfa