Fixed
Status Update
Comments
mi...@puls.be <mi...@puls.be> #2
Yep, that's exactly my problem at the moment. In our app everything is red, grey and
white. Orange is not a good combination.
white. Orange is not a good combination.
gr...@google.com <gr...@google.com> #3
Thats exactly my problem is.
If any one got the solution please mail me.
If any one got the solution please mail me.
[Deleted User] <[Deleted User]> #4
Did you find a solution to customize the option menu ?
tm...@gmail.com <tm...@gmail.com> #5
To set a custom background on menu item you can use this tip:
http://pastebin.com/1QHGTMUW
call the setMenuBackground in the onCreate
call the setMenuBackground in the onCreate
sh...@gmail.com <sh...@gmail.com> #6
solution from rciov work with Android 1.6, 2.1 and 2.2 but don't work with 2.3 :
InflateException android.view.InflateException: Binary XML file line #17: Error inflating class com.android.internal.view.menu.IconMenuItemView
Unfortunately I don't see new function in 2.3 to override default behavior.
InflateException android.view.InflateException: Binary XML file line #17: Error inflating class com.android.internal.view.menu.IconMenuItemView
Unfortunately I don't see new function in 2.3 to override default behavior.
sh...@gmail.com <sh...@gmail.com> #7
Yes, unfortunatly i saw that it doesn't work on 2.3...
gr...@google.com <gr...@google.com> #8
That's what happens when you rely on APIs and class names that are not public.
Note: com.android.*INTERNAL*.view...
This problem is unrelated to this bug.
Note: com.android.*INTERNAL*.view...
This problem is unrelated to this bug.
[Deleted User] <[Deleted User]> #9
Yes, of course. You are right :)
th...@nomadgate.com <th...@nomadgate.com> #11
[Comment deleted]
ba...@gmail.com <ba...@gmail.com> #12
If this helps, here is how I've been working around limitations with the built-in options menus.
http://www.codeproject.com/KB/android/AndroidMenusMyWay.aspx
ie...@gmail.com <ie...@gmail.com> #13
Here is a less nasty, better-documented refinement of the hacks above that works on 2.1, 2.2, and 2.3 and is unlikely to do harm on 3.X (but one can never guarantee). See post from "Louis Semprini:"
Google, this is clearly a COMMON requirement from developers---PLEASE provide a documented, supported way to set Options Menu:
- background, AND
- text color
In Android 2.X there is a nearly-undocumented style android:panelFullBackground but it only works for the background color, not the text. That doesn't help if you want to change the background from white to black or v/v.
Many developers need to do this so the Options Menu matches the visual style of the rest of their app. The Android documentation and Android engineers on the dev list in multiple places consistently state that Android apps should not rely on the (manufacturer-themable) look of the stock UI since themes may vary widely on different devices. Well, this is a case where we don't have control over the look of a key interface item.
Any real solution may also need to address Action Bar buttons for >= 3.X tablet devices, though I don't have experience with those yet so I can't comment.
Some developers have resorted to completely displacing the Android Options Menu and doing their own. This seems overkill; all the developers need is to set the colors and text like one normally does for a Button or other Android-provided resource!
If you need any evidence that this is a common requirement, please check out these links:
Thanks!
Description
NOTE: This issue tracking system is for Google Analytics developer products
only.
If you are not a developer/programmer visit:
---------------------------------------------------------------------------
Name of affected component: Measurement Protocol
Issue summary:
Enhanced e-commerce transactions using the measurement protocol aren't processed when a userId is present.
Steps to reproduce issue:
1. Send POST data to
2. The event is processed, the transaction is not.
3. When removing the uid from the POST-data and sending it again, the transaction will be processed and becomes visible in Google Analytics.
Expected output:
The transaction visible in both the user-ID property and the global property.
Actual results:
Only the event becomes visible when a userId is present.
Notes:
We both activated enhanced e-commerce and userID. In all other cases, hits with a userId (events, pageviews, ...) are processed like it should be. Accept for transactions.
We use PHP to do the task:
send(array(
'v' => '1',
'tid' => 'UA-2759391-3',
'cid' => '2011248066.1366974771',
'uid' => 'ABAE123',
'dh' => '
't' => 'event',
'ea' => 'purchase',
'ec' => 'ecommerce',
'el' => 'purchase was made',
'dp' => '/purchase',
'ti' => '12',
'tr' => 2000,
'ts' => 10,
'tt' => 418,
'cu' => 'EUR',
'pa' => 'purchase',
'pr1id' => '99',
'pr1nm' => 'With User AND Payload AND Pageview',
'pr1pr' => 199,
'pr1qt' => 1
));
send with curl where the above array is the payload:
CURLOPT_POSTFIELDS => utf8_encode(http_build_query($payload))