I want to open an app bar when an item is selected in the from a listview and things are working as expected by using a boolean parameter and binding that to AppBar.IsSticky and AppBar.IsOpen.
The challenge which I am facing is once i open app bar normally (i.e. by right click or through touch sensor) the above functionality no longer works for me even though the binded boolean values with AppBar.IsSticky and AppBar.IsOpen is still getting true when a item from lisview is selected.
Any suggestions?
I got the answer, i was missing two way binding for AppBar.IsSticky and AppBar.IsOpen
Related
I've got a complex form where some components are hidden until they are needed. I'd only got a few tooltips set (using the designer rather than doing it myself), but I noticed the other day that they had stopped working. Eventually I'd narrowed it down to some tooltips I'd got set on a tabpage that wasn't visible - If I made the tabpage visible then all the tooltips worked. I've worked round the problem by changing my form_Load code so that the tabpage is only made invisible (and removed from the tab control) right at the end of the form_Load code rather than at the beginning. This solution seems a bit clunky and might stop working if say the form load time changes or something.
Thanks
Kristian
My tooltips stopped working again after I added about 400 tooltips to a form. The tooltips loaded fine initially, but as I kept adding blocks of 100 (I have about 100 tooltip per tab page and may have say 20 tab pages). My fix for this was to create a new tooltip container for every tab page. The tooltip container is still created on the main form, but each tab page will use a different tooltip container.
Dim ToolTipPanel As ToolTip
ToolTipPanel = New System.Windows.Forms.ToolTip(Me.components)
I also set the tag property of the tooltip container to keep track of which one was which as I seemed unable to set the name property via code.
I'm working on a Windows Phone 8 app, which is basically a port of my existing Silverlight app. On one screen in the SL version, I have 10 ComboBox controls that default to nothing selected, forcing the user to make a selection before saving the item. That works great (this is my company's bug tracking application, so I want the users to be forced to make these selections, else they'll leave in a default, which will likely be incorrect).
In WP8, the powers that be seem to want us to use their ListPicker from the WPToolkit (since there is no ComboBox there or in the default controls). However, this is more a ListBox that supports SelectedIndex but not SelectedValue and SelectedValuePath. I've been using an index property in my viewmodel(this is kind of a pain since the model loads async, but I've been working around that..), but I have to default it to an actual option, which negates the business rule of forcing a selection.
I've also tried essentially copying the source code for ListPicker and have it inherit from Selector (the base control just inherits from ItemsControl), but that won't work as the Selector constructor is internal.
It seems like what I want to do is add support for SelectedValue and SelectedValuePath. Is that possible? Or am I going about this the wrong way?
I have a program which runs mainly though a NotifyIcon in the bottum right of my windows screen (XP). Whenever I open the ContextMenuStrip that appears when the icon is right clicked, a box also appears in the task bar. I also have nested menus inside the menu (mouse over one item leads to another menu), and each additional menu also creates a taskbar box upon appearing. So once I am at the third or fourth nested menu, there would be 3 or 4 windows appearing in the taskbar. After the menu disapears, so do the windows in the taskbar.
How can I stop the taskbar from displaying boxes to represent these menus? I have done nothing in my code as far as I know to create this type of behavior. I have searched for similar problems but have found nothing similar. There is no "showintaskbar" property for these items as far as I can see, and no other property that I can find which would affect this. I have investigated the owner of the contextmenustrip since I read the owner may effect these type of behaviors, but that doesnt seem to be helpful as there isn't an owner property of the contextmenustrip.
I don't know what else to search for, so I am here hoping someone can give me a clue as to what else may effect this type of behavior.
Any help is greatly appreciated. Thank you!
If you are using the ContextMenuStrip.Show() method, it will display in the taskbar as you describe. Try assigning your menu to the NotifyIcon.ContextMenuStrip property instead.
I am constructing an ASP.NET Menu using an asp:XmlDataSource and setting the Data property and binding the Menu. Everything works well until I have to change the menu. For instance when I remove a menu item from the xml and set the Data to a new xml string and rebind the menu. The item is missing from the datasource but still shows up in the menu. I double check to make sure it is not a refresh problem by doing a Menu.FindItem with the path to the item , which still shows up in the menu. I have even opened the page in another bowser and the item still shows up, so it must be a server issue.
Is there some chaching on the server that needs to be reset or what am I missing?
I will solve my own issue.
The thread at: http://forums.asp.net/t/1239541.aspx/1/10 showed that the xmldatasource has the EnableCaching set to true by default, so even though I was changing the Data property the changes were never making it to the menu.
Just finishing off an update to an application written in VB.NET that used to run fine under CE.NET 4.2. Deployment platform is now Windows Mobile 6.1.
The application runs in full screen, however whenever a new form is opened, the task bar, i.e. the bar with the start button comes to the fore and then the new form takes over. This is particularly annoying as I have a form that has many sub forms which are 128,128 and still the task bar flashes and obscures part of the user input screen.
Has anyone comes across this? Any known workarounds?
You can use the technique I posted here to disable the task bar.
I assume your application flow is something like:
Form 1 open.
Form 1 close.
Form 2 open.
The problem is that between the Form 1 closing and the Form 2 opening the background window may be partially drawn (e.g. the task bar will draw).
To work around this we normally create a parent window (which is your case is full-screen window) which sits behind the form windows. That way when one is closing and the next is opening it falls back to displaying the parent window which can display anything you like (blank?).