|
What does that mean? I don't know hDC.
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
hDC are the device context on Windows, basically you call GDI functions (or GDI+ classes for those who use MFC, we can't for reasons) to paint directly on a control or form surface.
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
Sounds interesting
I#ll check that out
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Be wary that it is an old method, I don't know for how long it will be supported and it can be tricky, especially getting the User Interactions right.
I plainly stated "how do I do that", not "how it should be done"
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
Hmm, considering that i guess it doesn't make sense to try that out
But thanks for the intel
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Wrote all of my Win Forms custom controls myself. This way I can adjust and extend them as I please. It requires a lot of knowledge but your software really stands out. Because on many occasions a well drawn never-before-used custom control does a better job then a combination of standard controls.
Examples of my controls include: vertical tree of controls for editing small hierarchies, chronology of versions, sets control, very special input box(es), diff/reconciliation controls, etc.
I do not follow a typical control framework strategy and do not add gazillion of features to each control. I start with minimal extensions to fulfill the requirements (if starting from existing control). Then I refactor when new features are needed. Today the controls are rich and mature.
modified 24-Nov-16 4:55am.
|
|
|
|
|
I admire your way of thinking and doing things!
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
I use WPF, you can create pretty much anything in it once you know what you are doing (which is the hard bit)
|
|
|
|
|
Get familiar with GDI and draw it yourself. You're a developer, so develop!
|
|
|
|
|
So, I've just signed the contract for my first house, had a technician look it over and everything is in the clear. Great layout, great price, great running costs, great locations for dog and children. Everything feels good about the deal, both me and my wifes agree. No cold feet what so ever, all other houses we have bidded on I had some hesitation but now I'm just exited.
And add on top of that I mailed a recruiter for an add out of a whim because there's a position that felt perfect which would remove all IT-management from me and allow me to focus 100% on development and gotten great response on that.
Now I'm getting anxiety that there are some bad news on the horizon instead...
|
|
|
|
|
Just enjoy those good times.
You'll have time to get worried so don't waste your time now.
|
|
|
|
|
If bad news comes in threes, why not good news as well?
That would mean that you've got another good thing to look forward to!
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'll finally get a VR headset!?
|
|
|
|
|
Now you've gone ahead and jinxed your good thing happening streak!
|
|
|
|
|
Don't really believe in superstitions like that so I'm not too worried. I believe the biggest risk is that if I run around expecting something bad I'll instead create the conditions for something to happen.
Sooner or later life will happen but I'm not one to think its because these things, just unconnected events that you choose to interpret as such.
With that said I'll most likely see a lot of suicidal wildlife on my drive home today. ^^
|
|
|
|
|
You DID see the joke icon, right?
|
|
|
|
|
I'm with DP on this one, wait till after the 3rd good thing before fretting over the inevitable bad thing that will appear.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Procrastinate?
I'm all for it.
|
|
|
|
|
Orson farm[^]
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
You're a hiring manager. You are responsible for picking a candidate who will be in a long-term position with the company and who you know you will be able to mold/teach. Both candidates are friendly and willing to learn. But there's a slight challenge.
Candidate A is a fresh engineering graduate from a World Famous University and has no experience in Development.
Candidate B is having good experience of Development and knows all of the sorts, trees, and hashes and answer all of your questions quickly under pressure. He also writes extremely clean and readable code, follows SOLID principles, writes great unit tests and has good knowledge of Dev-Ops things. However, Candidate B has no engineering degree.
Both candidates are friendly and both seem like they have potential to learn.
Your firm uses modern development approach in either C# or Java and produces applications that must meet a efficiency standard.
Who do you hire and why?
___ ___ ___
|__ |_| |\ | | |_| \ /
__| | | | \| |__| | | /
|
|
|
|
|
B: Because.... B has good experience of Development and knows all of the sorts, trees, and hashes and answer all of your questions quickly under pressure. He also writes extremely clean and readable code, follows SOLID principles, writes great unit tests and has good knowledge of Dev-Ops things.
|
|
|
|
|
Does my company have an HR department?
|
|
|
|
|
Seriously? You want HR to have the final word on engineers??
I would prefer to have them as a first sieve...
... such stuff as dreams are made on
|
|
|
|
|
Certainly not, but they set the rules, even while not having a clue.
And territorial pissing is a strong force.
|
|
|
|
|
Unfortunately that is all too true to be funny
But then I'm working in a manufactuary - not even our IT has any clue about the needs of a software developer
But, to answer the question:
Personally, I'd go with B due to his experience, assuming he can show some work to proof these claims. The company however would likely prefer A, because he's got a degree and, being inexperienced, requires less pay and less holidays!
That said, I might also go with A if he is willing and able to learn the things B already knows, and possibly a few things more. And, if he is willing to stay with the company for long enough, that all the time learning skills will eventually pay off! The problem of course is that you can never be sure of that...
Sometimes I regret there is no such thing as an apprenticeship, nor a craftsmanship job title for software development. In theory, institutes like universities should teach students what they need for an actual job, but in practice they only really teach the most basic theoretical aspects. It takes years to actually learn the ropes after that, and a period of apprenticeship would be perfect for that purpose.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|