I'm the author of a Windows application that's been around for years. The app uses the wxWidgets UI library. For the newest version, we upgraded to the Microsoft c++ compiler in Studio 10 and to the latest Windows SDK library. We did not change much else in the app. Now, several users have reported that after a period of time running the app, the menus go crazy. All of the users reporting the problem are running on Windows XP. The menus either get huge, filling the screen, and have a giant italic font with strikethroughs. Or they get really small, so that the only thing shown are up and down arrows, suggesting the rendering code thinks the screen real estate is too small to display anything else.
You can find example screen shots here:
Once the menus go crazy, all menus are affected, except the standard Windows and MDI menus. The only way to recover is to restart the app.
The code in the app and wxWidgits is a thin layer on top of the standard Windows API. Once the menus are created, afaik Windows manages the rendering.
Any ideas what's going wrong?
Related
At one point I was able to see our Outlook add-in app in the target options in f12 devtools for troubleshooting, but sometime last month it stopped showing up there. My colleagues are stumped, and I can't find much online in the way of troubleshooting.
I tried checking my Windows version and Outlook version against others who can see it in their devtools, but we're all on Windows 10 enterprise v1803, Outlook v1910, and IE 11. I've tried many things over the month since this happened like rebooting my PC, making sure I have the latest updates from IT, refreshing the options, running some commands I found online for targeting the right browser for devtools, etc. No change.
Another peculiar thing is that I'm seeing some completely different things in the Add-in than they are, like button alignments and div widths and such. I had our dev environment looking perfect on my end, but when a few people on the team screenshared with me there were a number of styling issues I can't reproduce. Even weirder, nobody experiences these issues in O365, it's just the desktop Outlook app on our Windows machines.
Any ideas on how to troubleshoot this would be very greatly appreciated.
Steps I take to produce the issue:
Click on manifest icon for our app in Outlook ribbon. App loads in the sidebar.
Open F12 devtools (both 32 and 64 bit for good measure from the System32 and SysWOW64 directories).
App is not in the target list. Click refresh, still not in the list.
FYI, any IE 11 windows I have open show up there, just not my app.
Starting in Windows 10 version 1903, the latest version of Office will use Edge WebView instead of IE to render add-ins. Edge WebView requires a different debugger (not the F12 debugger) called Microsoft Edge DevTools. You can find out more about it here.
When a Windows 10 computer wants to share some of its screens using webrtc protocol (firefox navigator), a list of the windows that can be shared appears. In this list, only "normal" applications appears, not the one related to "apps". By example, spotify window appears, but OneNote window is not listed.
It seems (?) webrtc screen share is not compatible with UWP apps.
Knows someone a way to share the screen of an app via webrtc ?
Note: following link allows to reproduce this issue:
https://mozilla.github.io/webrtc-landing/gum_test.html
you do not need share anything, just push "window" and see the list of windows that appears.
I believe Chromium (the open source version - not sure about Chrome) faces the same problem as UWP requires to use a new Win 10 API which shows it's own window selector. And then obviously that selector doesn't work on other problems. So it's a common problem on Win 10, with no known good solution as far as I can tell.
I want to create an application to run on a Windows 7 PC with a touch screen that is a sort of toolbox with large icons optimized for touch screens.
I need it to include a file browser with a hard coded path. That way I can auto launch the application and they will be taken to the folder right away. I would also like a section where I can put "Useful Applications" shortcuts so that they do not have to go through the start menu or the desktop.
Can someone guide me where I can start learning how I can do this? I would most likely code in C#
Get started with Windows Runtime apps. You can write a Windows Runtime app in a variety of languages, such as C# or C++ with XAML, C++ with DirectX, and JavaScript with HTML/CSS. Now you can easily create apps for Windows devices and Windows Phone from a single project.
https://dev.windows.com/en-us/getstarted
I heard that Microsoft refuse app's which unreadable in the "night mode" whatever it is? I mean when the phone goes into night mode all the color fonts are changed and that makes app unusable, then they reject the app.
I nave to submit RSS app and I do not know even what I have to watch out about that night mode. Please introduce me.
I suspect that what you mean is "light theme" mode. There are a lot of useful comments about this on this other thread. Windows Phone 7.1 Light/Dark themes management.
From my own personal experience, this is a bit of a headache. If your app isn't very stylistic, try to use the built-in colours for all your controls and whatever you do don't put an image background on it (that was my downfall).
After I've shut down a VS 2008 web project, well, a lot of times, I see many instances of the WebDev icon in the "tooltray" / system notification area:
These are no longer active instances; they were shut down by VS.
When I mouse over any of these, Windows Vista "conveniently" collapses the tray for me. This makes life miserable if the app I want is in between any of them (e.g., Outlook in the image above), and even worse if I actually want to right click on the "active" WebDev.
Any idea how I can get VS, WebDev, or Windows to fix this behavior?
There is a utility on CodeProject that does this: TrayIconBuster
http://www.codeproject.com/KB/system/TrayIconBuster.aspx
It runs every x minutes and removes all phantom icons...
Not the perfect solution, because I think this should be built in to Windows...