Dragging Hairlines to Widen Fields
-
Eddy Vluggen wrote:
Double-clicking the hairline should be enough :)
That works in many contexts, and I use it frequently, though I can't remember whether I remembered to try it in the Visual Studio/MSBuild macros window.
David A. Gray Delivering Solutions for the Ages, One Problem at a Time Interpreting the Fundamental Principle of Tabular Reporting
It's something I often forgot to add when using a DGV or listview, but it is a nice feature to have :thumbsup:
Bastard Programmer from Hell :suss: 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.
-
I just discovered, quite by accident, that if you drag the hairline at the right end of the value property of the list box that displays the names and values of the MsBuild macros, the hairline keeps moving to the right even when you drag outside the bounds of the control. Thus, you can keep dragging until it is sufficiently wide to show the end of the property of interest, such as, in my case, $(ProjectDir).
David A. Gray Delivering Solutions for the Ages, One Problem at a Time Interpreting the Fundamental Principle of Tabular Reporting
Frustratingly I suspect it is limited to a little less that 2147483647 pixels though....
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
I just discovered, quite by accident, that if you drag the hairline at the right end of the value property of the list box that displays the names and values of the MsBuild macros, the hairline keeps moving to the right even when you drag outside the bounds of the control. Thus, you can keep dragging until it is sufficiently wide to show the end of the property of interest, such as, in my case, $(ProjectDir).
David A. Gray Delivering Solutions for the Ages, One Problem at a Time Interpreting the Fundamental Principle of Tabular Reporting
Just wait until your app contains a list view, and you record in the registry the last column sizes. The fun begins when you forget to verify that the registry values actually exist when you retrieve them, and you set your list view column widths to rather large 32-bit random values. Windows is perfectly happy to do it, and tell your drawing code to draw a cell that is 16 pixels tall and 8 parsecs long.
Software Zen:
delete this; -
Just wait until your app contains a list view, and you record in the registry the last column sizes. The fun begins when you forget to verify that the registry values actually exist when you retrieve them, and you set your list view column widths to rather large 32-bit random values. Windows is perfectly happy to do it, and tell your drawing code to draw a cell that is 16 pixels tall and 8 parsecs long.
Software Zen:
delete this;Only eight parsecs? ;)
David A. Gray Delivering Solutions for the Ages, One Problem at a Time Interpreting the Fundamental Principle of Tabular Reporting
-
Only eight parsecs? ;)
David A. Gray Delivering Solutions for the Ages, One Problem at a Time Interpreting the Fundamental Principle of Tabular Reporting
-
Well... It's not the Kessel run!
- I would love to change the world, but they won’t give me the source code.
Forogar wrote:
Well... It's not the Kessel run
I had to look that one up. I at least had a clue about the size of a parsec. It took a bit of noodling for me to grok that Solo was bragging about covering the distance "in only 12 parsecs." Once I read about them being unable to travel in straight lines, that part made sense, and I suspect the same holds for Warp drive.
David A. Gray Delivering Solutions for the Ages, One Problem at a Time Interpreting the Fundamental Principle of Tabular Reporting
-
Forogar wrote:
Well... It's not the Kessel run
I had to look that one up. I at least had a clue about the size of a parsec. It took a bit of noodling for me to grok that Solo was bragging about covering the distance "in only 12 parsecs." Once I read about them being unable to travel in straight lines, that part made sense, and I suspect the same holds for Warp drive.
David A. Gray Delivering Solutions for the Ages, One Problem at a Time Interpreting the Fundamental Principle of Tabular Reporting
-
Only eight parsecs? ;)
David A. Gray Delivering Solutions for the Ages, One Problem at a Time Interpreting the Fundamental Principle of Tabular Reporting
Okay, so I rounded off a little.
Software Zen:
delete this; -
Okay, so I rounded off a little.
Software Zen:
delete this;Au contraire! This little exchange has been both enlightening and fun. Moreover, if you can cover the distance in only 8, you've bested Han Solo by a full third.
David A. Gray Delivering Solutions for the Ages, One Problem at a Time Interpreting the Fundamental Principle of Tabular Reporting
-
I just discovered, quite by accident, that if you drag the hairline at the right end of the value property of the list box that displays the names and values of the MsBuild macros, the hairline keeps moving to the right even when you drag outside the bounds of the control. Thus, you can keep dragging until it is sufficiently wide to show the end of the property of interest, such as, in my case, $(ProjectDir).
David A. Gray Delivering Solutions for the Ages, One Problem at a Time Interpreting the Fundamental Principle of Tabular Reporting
-
This has been part of Windows since at least 3.1 (pre-32 bit). I'm not surprised you didn't know about this as I have to constantly teach this trick to my users (and developers).
In general terms, I know that. I've used Windows since almost day 1, and I don't recall ever seeing a drag work when the mouse pointer moves outside the boundaries of the windows that has the focus. That's good to know, so long is it doesn't make the thing 3 parsecs wide. ;)
David A. Gray Delivering Solutions for the Ages, One Problem at a Time Interpreting the Fundamental Principle of Tabular Reporting