|
|
In a VS 2017 project, I have an ellipsis (...) in the title bar next to the minimize button. Never saw that before. It doesn't react to the mouse, and vanishes if I maximize the window. Comes back when the window isn't maximized. Resizing the window doesn't affect it. It's there when debugging and in design mode. Why? Anyone? 
Screen Capture[^]
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
modified 15-Jun-18 18:06pm.
|
|
|
|
|
I have never seen that as far as I am aware. Does the mouse cursor change when you move it over the ellipsis?
|
|
|
|
|
Richard MacCutchan wrote: Does the mouse cursor change when you move it over the ellipsis?
No reaction at all. It's just there. I created a new form just to see if it showed up again but it isn't.
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
|
|
|
|
|
Very strange, just one of those random bugs I guess. You may like to keep the project code and try reporting it to Microsoft.
|
|
|
|
|
Richard MacCutchan wrote: You may like to keep the project code and try reporting it to Microsoft.
I probably will. It's odd enough to generate a bit of curiosity but not doing any harm.
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
|
|
|
|
|
I just replicated it with a simple test, and it's not a bug, but a feature. If the text of the title will not fit the title bar, then trailing characters are replaced by an ellipsis.
Go to the form designer and check the text of your form's title. I will bet it has a lot of spaces after the actual text. Alternatively, a lot of spaces and then some extra characters.
|
|
|
|
|
That's not it. The ellipsis would be at the end of the text. This is beside the minimize button and the text is just two words. I added a better screen capture[^] below the first one where the text is visible.
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
|
|
|
|
|
Yes, and I bet if you go to the form's Design window in Visual Studio, and check the properties of the title you will find lots of spaces following the text. That's why the ellipsis disappears when you increase the width of the Window, because all the characters can fit into the title bar.
|
|
|
|
|
Richard MacCutchan wrote: lots of spaces following the text
OK, where the heck did all the spaces come from? Never encountered that before.
Thank you! 
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
|
|
|
|
|
You have three dots; according to the Ux-Guide from MS they should be used in a menu if the menu is to open a new window.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Eddy Vluggen wrote: You have three dots; according to the Ux-Guide from MS they should be used in a menu if the menu is to open a new window.
It's just plain old Winforms.
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
|
|
|
|
|
You may have some "utility" installed that injects a button into the title-bar of some application; yours being a form in design-mode, it may not hook up its designed functionality.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Eddy Vluggen wrote: You may have some "utility" installed that injects a button into the title-bar of some application; yours being a form in design-mode
Can't imagine what that might be. Not using any 3rd party products in the project. And I created another form in the project. It did not have the ellipsis. Copied all the controls from the original, still no ellipsis.
I was mistaken about one thing: Resizing the window does eventually affect it. Once the width hits about 1000 the ellipsis disappears. Comes back when the width is decreased.
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
|
|
|
|
|
Alan Burkhart wrote: Not using any 3rd party products in the project.
I wasn't referring to anything in the project, but a utility outside of it, that's part of another application. If you want to draw a button on the title bar of a form of another application, you often try to determine the correct window with some parameters. Those may just be equal to the one you were designing.
Alan Burkhart wrote: Resizing the window does eventually affect it. Once the width hits about 1000 the ellipsis disappears. Comes back when the width is decreased.
So the target is a window that never becomes larger than 1000 pixels.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
See my latest reply to Alan.
|
|
|
|
|
Tx for the update 
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Eddy Vluggen wrote: So the target is a window that never becomes larger than 1000 pixels.
It can be any size. Just hadn't had occasion to size it any larger.
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
|
|
|
|
|
The "title" is wider than the "title space" in the title bar; hence the "...".
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Yep. We finally figured that out. Thing is it was filled with spaces past the text. No clue how that happened.
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
|
|
|
|
|
Spaces will do it; sometime "unprintable characters".
(I tend to "trim" input since users tend to "lean" on the keys when sleeping).
I've had the latter in source code; weird compile errors ... but you can't "see em'".
Sometimes have to "delete the line" and "type it over".
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
I use .Trim a lot but never thought about needing it for the title bar of a form. Still curious about how it happened but I doubt I'll ever know.
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
|
|
|
|
|
Hello.
It's possible to use .Net framework to develop a C# Windows applications that will control printing from windows printing spool (like using quotas, adding custom messages on printed pages, etc)?
The approach I'm thinking (and started) to follow is to create a Windows Service and inside this service to monitor windows printing spool with a timer (looking for best approaches). Is that the right choice?
Any hints and advice to lighten my way will be very welcome and is the intent of this Question post.
I'm using
VS2015
.Net Framework 4.5.2
Some of the requirements I'm working on are:
- Checking in AD or LDAP if the user who requested printing is not over quota
- Blocking over-quota user's print
- Adding to every printed page in the footer or header of the page Companies Name.
- Save in printing server box a copy of the printing in PDF or some other format for future audit.
It's expected to use this app in different windows versions like XP/Vista/Win7,8,10
Best regards
|
|
|
|
|
|
You're wasting your time if you plan to spend time targeting anything less than Windows 10; like XP?!
And having had to deal with "print queues" and restarting failed print jobs, I can say you are biting off more than even most "pros" can chew.
And most of your "requirements" are only feasible at "report generation time"; NOT when the "report" is already "in the queue".
Sorry, but you should focus on something less ambitious if you hope to succeed.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
