howdy, AngelOD!

Heya :)

how can I help you today?

Lemme find it. I wrote down the question. :)

I'm having a problem with menus and their IDs when I inflate them using the MenuInflater. It used to work like it should, but after I converted my project so that it uses fragments (and thus supports Honeycomb devices as well) it no longer seems to work. I inflate my menu using: getMenuInflater().inflate(R.menu.main, menu); -- This is called from the activity. I noticed some problems whenever I was trying to make changes to the menu in onPrepareOptionsMenu(), so I added some code to onCreateOptionsMenu() to see the various IDs. Here's the code along with the output I get from it: http://pastebin.com/PjuFkikU -- Obviously something is wrong, and I assume it's something I've done wrong, but I can't figure out what that would be.

I've checked the main.xml file to make sure I'm using the correct IDs and everything, of course.

whenever you run into resource ID issues, the first thing to do is clean the project

that's Project | Clean from the Eclipse main menu

or ant clean from the command line

I deleted the R-file.. But I'll try the other one. Hold on. :)

deleting the R file isn't sufficient

hello

howdy, fitz!

so opinion on Google/Moto?

AngelOD: the problem is that R.id.foo actually gets inlined in the bytecode

good | Bad | Ugly ...

cleaning the project removes the precompiled classes

fitz: what was that one Magic 8-Ball value? "Future appears murky"?

Thanks! That did the trick. Sheesh.. One would think I would have figured that one out on my own. I wonder what went wrong, but as long as it works, I'm happy. :)

I think it is a good thing - best to have patents and maybe G-TV will happen

yeah, when I did my development at the command line, I'd always do ant clean install, just to be sure

I think I'll do a routine clean as well from now on, just to be sure. :)

fitz: what's unclear is how other device manufacturers will react (beyond the sound-bite press quotes)

so is it true that next version of android will make the cell and tablet transparent - one code works for all or is it still going to be device unique

Ice Cream Sandwich is supposed to unify tablets and phones

akin to how iOS 3.0 was for phones, iOS 3.2 was for tablets, and iOS 4.0 was for both

Ice Cream Sandwich sound like magic - don't know how they plan on doing that

well, it won't all be the same

for example, a comment from Dianne Hackborn suggests that ICS phones will still have dedicated off-screen buttons/soft keys for HOME, BACK, etc.

so is it best to wait on dev for tablets for now

I'm assuming developers will have to use fragments for different screen sizes just as they do now. :)

so there will be no system bar and will retain the Gingerbread status bar

AngelOD: in all likelihood, yes

fitz: if you're designing around fragments, it should all "just work" when ICS comes around

then again, I've been wrong before with projections of new Android releases

ok will keep in mind thanks

so now they start to take out the carriers one at a time?

they who they?

Apple/Google?MS

define "take out", then

Apple/Google/MS take out ATT, Verizon etc.

buy them

oh, probably not

I;d think the carriers' market caps are a little steep for that

ya but with Apple cash hord ....

though perhaps not

Sprint is around $14.5 billion

Anyway, I'll get going. It was the only problem I had, and I'm otherwise quite engrossed in programming these days, so I'll get back to that. :)

ok, see you later!

ya jetting as well thanks cya

Thanks once again. Both for the help as well as for the awesome books. :)

your out next week?

you are very welcome!

next week I'm in Oslo

sleep may be in short supply

so I do not have any chats scheduled

sorry

nice va-ca or work

Oooh. Not too far from where I live then (but still too far to just pop by). I live in Denmark. :)

work, teaching an Android course

AngelOD: when I taught in the Malmo/Lund area, I used to fly into Copenhagen

nice have some fun then

Cool! :) I live in the opposite end of Denmark, though, but the country -is- quite small. Can get from here to Copenhagen in 5-6 hours, after all. :)