I have a project in the play store created with version 3.2 at end of October. Today I rebuilt the project to add new features. When I deployed it to Android I noticed the following 4 issues.
1. The push notification icon is a solid white square. It was my icon in the past.
2. The initial screen form is incorrect as it goes into the android soft buttons at the bottom of the page.
3. The theme for my combo box is not showing. Just see thru to background.
4. The text field background is also just using the background instead of the white.
I tried building in latest, 3.2 and 3.1 with no differences. I reverted all code to the release in October with no help.
I submitted the IOS build and everything is fine.
The simulator shows everything is fine.
I tried many times to figure out why this is happening and have not been able to.
I need 10 reputation points to post more than 2 links so, I'm only showing 2 screen shots. Let me know if you want the others.
Please see the following:
This image shows the edit and dropdown issue
This is the current play store version of the edit and dropdown
Any ideas on how can I fix these issues? For the text field I use my own style (it does get the boarder but not the background). The notification icon, I don't see how anything I can do would affect this.
Thank you
Sam
-- Edited --
I did manage to get these working again.
I was setting the background color using the theme background tab and setting a gradient with upper and lower the same color. I changed this to NONE, then in the color tab set the background color.
Notification needed a new icon as specified by Chen. In my case the app icon is basically a square and doesn't transfer well to a notification icon.
The last was the nexus 9 initial screen painting into the bottom navigation control. This is still happening and is easily reproduced by making a new hello world codename one app with no changes.
Are you using the android.asyncPaint=false build hint?
I understand some issues occurred with it although I doubt you would see them if you are using the versioned build.
Setting the background color using the theme background tab and setting a gradient with upper and lower the same color didn't work.
Change this to NONE, then in the color tab set the background color.
Related
I'm building a form as a menu, because the demand is a menu that come from the top. So I've build my form with a BoxLayout Y, set the backgroud transparency of to 0 with the theme and added a container with my menuItems inside. A Cover-Uncover transition to add some menu feeling and the form is complete.
On Ipad (cropped):
The result is pretty good, but I have a big problem on Android : the transparency work during the transitions, but when the in transition is over, all the transparency turn to black. I've tried on Android 4.4.2 (old archos tablet) and on Android 8.0 (brand new P20 lite smartphone).
On Android while transition is active :
On Android after transition
Is it a way to show the previous form on Android ? Or even a sidemenu swipable from the top ?
Forms can't have transparency. There is nothing behind them. If there was we'd need to keep in memory every form you ever showed because you could reference forms in code and set them to transparent on the fly. Form is a special case top level component when you show it, it's the end of the line.
You can accomplish this with a Dialog or an InteractionDialog both of which work similarly. In fact the side menu bar code is just an InteractionDialog.
Looking to my first steps with WPF on Windows 7 I was very pleased. Seeing it on Windows 10 I was very surprised. The buttons didn`t looks like expected. Trying it with WinForms results in the expected look an feel.
Here my problem:
So my question:
How can I get the "normal" style of the default button (OK has IsDefault=true) with the expanded blue border for the button even when it has focus, without defining the button-style myself?
This is very important in case of setting the focus to the Cancel-button programmatically, because in this case the dotted border will not be displayed, so on Win 10 the user can not know witch button will be pressed by enter.
You can get similar button styles using Windows UWP.
In WPF, you can check out the Modern UI(MUI) in MSDN site.
It can produce similar results. I have been working with mui for a couple of months and it really helped me to satisfy my client who wanted to have a Windows 10 like UI experience. I had to create tiles like in start menu also. MUI did a great job for me.
Get the MUI from Github. Modern UI for WPF
Also I had tried devexpress and telerik controls. Have a look at them too.
I had my app working just fine a few days ago and then I noticed the first problem. I had to tap twice in order to make a button go to the next screen. Also happened to the checkBoxes. Had to tap twice to make them change.
But now it got serious. Since yesterday when I tap on a TextField the app freezes and then crashes.
The only significant changes I remember I did were 2: I uploaded an image for the App Icon and I edited the TitleArea UIID. I removed the TOP and BOTTOM margins. It also affected some of my label and button UIID, because now they don't show on the device
When I run the simulator, the doble tap also occurs, but the TextFields work fine and the Button and Label UIID look the way they should.
Any ideas why this happens?
I am right now working with old versions to try to determine the reason, but no luck so far. Thanks
Use a solid color rather than a gradient with the same colors. Gradients are slow and problematic across platforms so you are paying a lot for something that you aren't even using.
We'll need a better test case to reproduce crashing, I think that what you initially saw when you submitted the issue was a regression in the text input that we since resolved in the build servers.
I am developing a WPF application. My customers want to use it on Windows 8 and it's working correctly. But they are complaining me about the background color of the app's icon on Start Screen.
So can you please show me how to change it in Visual Studio or some tricks? I found some tuts on Google to customize it but using tools and I want to make it happen in Installer or Property of project...
Thanks
Change app icon color from the App Manifest file.
Heres the app manifest portion where you can change in the image
In My case the bacground color is #464646 you can change it to any thing you want and update to the users :)
Because of this reason it is always advised by Microsoft to use Transparent Png logo and a uniform background color for app tile.
That background colot of app's icon on Windows 8 is the default behavior of Windows 8. It will display the background color of the app's icon using the "dominant" color of the app's icon. If your icon has dominant color of brown, it will display brown background.
This is also the similar default behavior when hovering mouse on running application's icons on Windows 7's taskbar. To enhance the look, try change the application icon to use neutral colors or light colors instead of dark colors.
Or you can change the icon of your app to use single color's icon (such as white) on transparent background to reflect the flat theme icons of Windows Store apps in Windows 8, or use full rectangle icons as those games in Windows 8.
Example:
There is a similar question and answer: UWP Tile Background Color Not Working by Kasper, but is not specific to Windows 8, for anyone looking for a UWP solution.
As the answer by Anobik states, set the colour in the app manifest page. However, as it was found by Kasper, the value must be set in HEX for it to work as expected.
I have the problem that whenever I use the Page Transitions from Windows Phone 7 Toolkit, the transitions are very slow and the whole app seems to have framed drops. The animations are "stuttering".
Is anyone else experiencing this?
I'm using the TransitionFrame class as RootFrame and in the .xaml pages I'm using code like
<toolkit:TransitionService.NavigationInTransition>
<toolkit:NavigationInTransition>
<toolkit:NavigationInTransition.Backward>
<toolkit:TurnstileTransition Mode="BackwardIn"/>
</toolkit:NavigationInTransition.Backward>
<toolkit:NavigationInTransition.Forward>
<toolkit:SlideTransition Mode="SlideDownFadeOut" />
</toolkit:NavigationInTransition.Forward>
</toolkit:NavigationInTransition>
</toolkit:TransitionService.NavigationInTransition>
I'd recommend against using the WP7 Toolkit Page Transition animations.
If you activate the performance counters you can see that just by changing the root frame to the WP7 frame, your fill rate is increased by 1. Since fill rates even in the best of apps are 1.5+ and the recommended maximum is 2.5, I'd say that's very bad.
Telerik has a WP7 Page transition control you might want to checkout. But honestly, I couldn't find/code any generic page transition that gives a well-performing page flip effect.
The latest changeset include some performance improvements for transitions. You could give them a try.
WHat's on the page could also impact performance. Does it contain a lot? or any events/storyboards which could be being triggered by the transition?
The new version of the silverlight toolkit (august 11) is much more faster than the old one! Transition animation begins right after click on an item. Try it out, eventually you also have to change other libraries (eg Microsoft.Phone.Controls) as found in
C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v7.1\Libraries\Silverlight
Toolkit can be found in:
C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v7.1\Toolkit\Aug11
This Link might help,
the frame is painted with the background brush colour with every
frame, as well as the page being painted.
The striking thing about this is that it's painting the colour that is
the same as the background behind it anyway. If the selected theme has
a dark background it's painting black on top of black. Or, if the
theme has a light background it paints white on white.
If we combine this knowledge of the unnecessary work the
TransitionFrame is doing with the fact that anything transparent
doesn't contribute to the fill rate a solution presents itself to us.
We just need to make the background of the TransitionFrame transparent