|
Control docking and anchoring are well understood by everybody and we all know that the two techniques are mutally exclusive. The help pages says something like "Only one can be set at a time, and the last one set takes precedence".
I've always believed what I'm told by my elders and betters and was certain that code like the following would create an anchored control.
FancyControl fc = new FancyControl();
fc.Anchor = AnchorStyles.Top | AnchorStyles.Left;
SomePanel.Controls.Add(fc);
My FancyControl would typically be used fully docked and the constructor helpfully presets that condition. On the very rare occasion it should be anchored then just assign a value as shown.
Why oh why then, did the control remained dicked?
FancyControl fc = new FancyControl();
Debug.Print("Dock: {0} Anchor: {1}", fc.Dock, fc.Anchor);
fc.Anchor = AnchorStyles.Top | AnchorStyles.Left;
SomePanel.Controls.Add(fc);
On reading the Anchor property all became clear as the value was already Top|Left. Perhaps the Anchor property ignores redundant assignments? Of course it does and a delve into the published reference source confirms this. Search for DefaultLayout.SetAnchor in Reference Source[^] if you are interested.
The final solution for the simple task of setting the control's anchor property is
FancyControl fc = new FancyControl();
fc.Dock = DockStyle.None;
SomePanel.Controls.Add(fc);
OK I should have included the statement fc.Anchor = AnchorStyles.Top | AnchorStyles.Left; after undocking but it's redundant!
AlanN
aka Alan "2f hours debugging" N
|
|
|
|
|
Alan N wrote: did the control remained dicked?
Is that gender-specific control property?
Marc
|
|
|
|
|
No, having a dick does not imply gender at all these days.
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
Anchoring is not use in WPF. Docking is used if you use a DockPanel.
|
|
|
|
|
|
Could only ever reliably be called from the WhatDoYouGetIfYouMulitply6x9() method.
|
|
|
|
|
That should throw the Call6x7MethodInstead exception.
Jeremy Falcon
|
|
|
|
|
It should immediately throw the find_question event.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
No, it shouldn't. The event should only be thrown after 6 million years of intensive computation.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
I strongly suspect that the event function just contains:
stdout << "I'll have to think about it.";
Thread.Sleep(189345600000000000);
sdout << "I have it!";
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Oh my word...[^]
O_O
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
|
Wtf is that? I wondered when I started up a small tool on a Windows 8 Embedded machine: most of its UI was in English (as expected, because Windows' UI is in English), but an enumeration control was in German. How can that happen? Did I forget to copy a file? No, can't be: the English texts are always compiled into the main assemblies, only translated texts make it into satellite assemblies.
I investigated the issue further. And had to see:
Current Culture: de-DE
Current UI Culture: en-US
What an odd combination! And while the ResourceManager normally uses CurrentUICulture , the EnumDescriptionConverter used CurrentCulture ...
|
|
|
|
|
It's a mess, but there's a method in the madness.
I'm using a computer with an english UI (CurrentUICulture) so that I can easier search error messages. But I still want to have Swedish format (CurrentCulture) on money, date, time, decimal comma and so on.
The fact that to few people have a clue on what's what or how to us them, is a completely different question.
|
|
|
|
|
Exactly that's the background of the mixed English/German cultures. That's the first time I was faced with such a mixture. And thus I learned to take a closer look what type of Culture to use in future: CurrentUICulture for language, CurrentCulture for formats.
|
|
|
|
|
Bernhard Hiller wrote: That's the first time I was faced with such a mixture. And thus I learned to ... That's the most important thing
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
|
More likely a C++ problem: the counter is an unsigned int32, but it was passed to the formatting function as a signed int32... Now have fun with reading 2^32-1 emails.
|
|
|
|
|
If you would be so kind to publish your address here I would gladly help ... as would millions of others ... that said, (sub)empty inbox would bother you no more
modified 19-Nov-18 21:01pm.
|
|
|
|
|
...you look at the commit log, see a couple of messages saying "addressed a few bugs", check what they are and find out that the 'solution' was to comment some lines out!!!!
|
|
|
|
|
Or when I look at my log and it says addressed a few bugs but there is no body text at all! - Because I hate myself I guess.
|
|
|
|
|
The YAGNI Strikes Back
Code Trek 2: The Wrath of YAGNI
Code Trek 3: The Search for YAGNI
Code Trek 4: ....whales...really...?
Sorry, derailed a minute there. I was just going to say that YAGNI usually the cause of bugs that can be fixed with comments. Just saying.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Quite possibly. But if the code itself is unneeded then the commented version is even more unneeded...
|
|
|
|
|
On production version: absolutely.
On source version it can give a good idea of plans and thought process. Or it can be a horrible mess, which will still give the next people who look at it a hint as to the thought process of the author. By and large I tend to find commented code more useful than actual code comments
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
WiganLatics wrote: But if the code itself is unneeded then the commented version is even more unneeded... Ah, you're one of those who can't stand leaving commented code in place.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|