AllowTransparency and issues with ComboBox, Menu popup
-
I have recently started working on WPF. In my XAML file, I have set AllowTransparency = True. The combo box stopped showing the drop down items after setting the AllowTransparency property to True. On investigating further, I found there is a hot fix available on request from MS but a few people did complain that the hot fix never solved the problem. Have you encountered this problem and reolved it successfully? I believe this is an old bug. References - http://support.microsoft.com/kb/943326[^] https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=369500&wa=wsignin1.0[^]
-
I have recently started working on WPF. In my XAML file, I have set AllowTransparency = True. The combo box stopped showing the drop down items after setting the AllowTransparency property to True. On investigating further, I found there is a hot fix available on request from MS but a few people did complain that the hot fix never solved the problem. Have you encountered this problem and reolved it successfully? I believe this is an old bug. References - http://support.microsoft.com/kb/943326[^] https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=369500&wa=wsignin1.0[^]
I've had this problem for years on XP and Server 2003 (newer OS's don't seem to have a problem). Whenever the resolution changes it gets into this state. The patch didn't do anything for me - I either have to restart or use the arrow keys to move through the combo box items. This could be fixed in 4.0, I have not tried. I'm still on 3.5 SP1.
-
I've had this problem for years on XP and Server 2003 (newer OS's don't seem to have a problem). Whenever the resolution changes it gets into this state. The patch didn't do anything for me - I either have to restart or use the arrow keys to move through the combo box items. This could be fixed in 4.0, I have not tried. I'm still on 3.5 SP1.
I am on 3.5 as well. I am in a process to create a prototype and propose WPF for our new application suite. Now this bug scales down all the UI I have done so far using Transparency and rounded window etc. Yes, this problem is specific to XP and I don't think we are upgrading to Win7 anytime soon at our enterprise level. A naive question, ideally, to develop using .NET 4.0 would I need to upgrade to VS 2010?
-
I am on 3.5 as well. I am in a process to create a prototype and propose WPF for our new application suite. Now this bug scales down all the UI I have done so far using Transparency and rounded window etc. Yes, this problem is specific to XP and I don't think we are upgrading to Win7 anytime soon at our enterprise level. A naive question, ideally, to develop using .NET 4.0 would I need to upgrade to VS 2010?
It's not a naive question. Given the fact that VS allows multi-targetting, this is a perfectly reasonable question. The answer, is yes - you really do need to upgrade to VS2010.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
It's not a naive question. Given the fact that VS allows multi-targetting, this is a perfectly reasonable question. The answer, is yes - you really do need to upgrade to VS2010.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Thanks Pete. Upgrading it to VS2010 is another issue for us at the moment, VS2008 would be OK. I think I am going to have a bit hard time presenting WPF as the better candidate for our Enterprise apps. An alternate option being considered is Google Web Toolkit/Java at the moment. We have quite a few native apps in VS2003 and .NET apps in 2005. I recently started using VS2008 for WPF. I tried installing .NET 4 and it failed on XP! I found quite a few people have this issue. I'll dig into this sometime later today.