This question already has answers here:
What are the two numbers in top left of uap app using VS2015 and Windows 10?
(3 answers)
Closed 6 years ago.
I'm developing a universal windows app in vs 2015 (C#)
When I run the application, two little black boxes with white numbers are always blocking my way (I can't see my app behind), these boxes are located in the top-left and the top-right of the window
Please tell me what are these boxesand how to get rid of them??
thank you
I have never seen or used these counters, but a quick Google search shows that they are Visual Studio Frame Rate Counters that are used for debugging purposes.
Apparently you can disable them with the following code in your app. I have no tested this so I make no guarantees to whether it works or not.
Here is a good article that describes this functionality though and shows the exact boxes you are describing:
http://www.kunal-chowdhury.com/2015/12/uwp-frame-rate-counter.html#fqDguKy73ZwohOYh.97
#if DEBUG
if (System.Diagnostics.Debugger.IsAttached)
{
this.DebugSettings.EnableFrameRateCounter = false;
}
#endif
Hope this helps.
Related
This question already has answers here:
How to make the UI responsive in Winforms [closed]
(2 answers)
How to make size of Window responsive for every type of screen resolution using Windows form [closed]
(1 answer)
Closed 4 years ago.
I have created an Application in Visual Studio 2015 using C# as a P.L. I created it in my laptop whose resolution is 1920 * 1080 (as recommended). It runs smoothly on may laptop, the designs are meant to be as expected. But when I try to run it to another any screen resolution it just zoomed out and the designs, windows form components are not visible, inshort the GUI got crashed. I don't used any of those Flowlayout panel. Is there any setting or configurations on my project that i need to do to fix my problem ?
You may set the application windows form size to maximized so that it will fit in all resolutions by Set the System.Windows.Forms.Form.WindowState to FormWindowState.Maximized and then used flow layout/dock combinations to handle manual resizing
Please refer this video
This question already has answers here:
How to configure an app to run correctly on a machine with a high DPI setting (e.g. 150%)?
(6 answers)
Closed 5 years ago.
I developed an winforms program on w8 and just tried it on w10 for the first time, the following image shows how the text looks in the forms editor of vs2015 versus how it looks when the program is executed.
https://ibb.co/hhi40v
The text in the title bar renders fine.
I should probably mention I'm at 4k resolution with 150% scaling - I tried all the autoscalemode options and none did the job.
There seem to be ways to deal with this in wpf but in winforms I can't find any information, which is odd because this is presumably a common thing.
This is known issue - you need to develop your WinForms app to be a DPI-aware.
Read here for example and detailed explanation: Creating a DPI-Aware Application
Generally, you need to apply a specific Forms design rules to make them DPI-independent.
This question already has answers here:
.NET Equivalent of Snipping Tool
(3 answers)
Closed 5 years ago.
I'm looking for a way to draw a rectangular selection-visualiser, basically similar to Gyazo.
If any of you are familiar with iOS jailbreaking and have used Snapper 2 before, I'm trying to do that but for Windows. For those of you who aren't, it allows you to select an area you want for a screenshot and then keeps it on top of everything else, allowing you to drag it around, save it etc. It's really useful for phone numbers, WiFi passwords among other things.
The only issue is that I don't know how I'd go about drawing a selection area and grabbing an image of it.
Any help would be appreciated.
Windows since 7 has the Snipping tool. It might be close enough to the droid you are looking for: https://support.microsoft.com/en-us/help/13776/windows-use-snipping-tool-to-capture-screenshots
If you mean .NET with C#, there is Graphics.CopyFromScreen. Note that it does not work from Windows services - a interactive session is required and Services are barred from those by default since Vista.
One issues is having this thing be drawn "on top". Generally the topmost game is one you and the user can only loose. Everything that is able to win it is either part of Windows itself. Or uses a "intercept GPU output, draw something on top" approach, wich is not trivial.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
How does Microsoft One Note 2010 implement a window that is docked to the desktop?
I was wondering how one would go about making a program (in C# or C++) that would have a frozen pane and shrink the active area of the rest of the screen. A good example of this is the Facebook client chat program in full screen mode because it is always on top as well as shrinks the area of the screen that is active, including shrinking the desktop. What I'm trying to achieve is the green bar in the picture below that can never go away:
(note please ignore the red circle in the photo below, the only picture I could find of what I'm trying to do was from a meme about how on all military sites they have a suicide hotline because the systems are all so slow, they make you want to kill yourself)
It's documented on MSDN as an "AppBar": http://msdn.microsoft.com/en-us/library/windows/desktop/cc144177%28v=vs.85%29.aspx
It's a regular Win32 window anchored to one edge of the screen and also reduces the area for other windows to maximize into.
This question already has an answer here:
Closed 10 years ago.
Possible Duplicate:
WP7 RTM Emulator is displaying the framecounter and dx info on the rightside - is this the default?
I want to take a nice screenshot of my app and send to a friend, but I got the silly debug string in the upper right corner. How to I remove it?
Seems to be numbers and shift if using acceleration for instance
Try running it as non-debug as you can:
Use a release build instead of a debug build
Use Ctrl-F5 instead of F5 to launch (so there's no debugger attached)
IIRC, that will prevent the diagnostic information from showing. It's probably that you only need to take one of these steps, but I couldn't tell you which offhand.