|
Can I use backcolor on datagrid when I MouseMove on it ?
|
|
|
|
|
Didn't you hear? VB6 will stop working at the end of the year; attempting to use it will cause your hard drive to melt into a large puddle. 
Seriously though you might want to consult the proper forms.
Visual Basic / VB.NET[^]
-------------------------------
DEBUGGING : Removing the needles from the haystack.
|
|
|
|
|
vongkham wrote:
Can I use backcolor on datagrid when I MouseMove on it ?
What made you post this on the poll forum? 
|
|
|
|
|
Nishant Sivakumar wrote:
What made you post this on the poll forum?
 The guy is a VB user, doesn't that tell you something?
Blogless
|
|
|
|
|
norm.net wrote:
The guy is a VB user, doesn't that tell you something?
"Success is the ability to go from one failure to another with no loss of enthusiasm." - W.Churchill
|
|
|
|
|
Especially people still on Visual Stduio 6.0, there can't be may positions requiring this still any more ?
Blogless
|
|
|
|
|
It's still the best for MFC (that's what the poll is about). In VS.Net they really screwed up the resource editor and that feature is important for MFC development.
|
|
|
|
|
ed welch wrote:
In VS.Net they really screwed up the resource editor and that feature is important for MFC development.
Yeah, that's my biggest gripe about Visual Studio 2003, still lets hope this has been addressed in next version. 
Blogless
|
|
|
|
|
norm.net wrote:
still lets hope this has been addressed in next version.
You make me laugh... LOLOLOL
------- sig starts
"I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
John Simmons / outlaw programmer wrote:
You make me laugh... LOLOLOL
Yeah you're probably right, and pigs might fly outta my butt.
Blogless
|
|
|
|
|
|
In my opinion they screwed up the whole gui. I find it soo much easier coding with vc6 + WndTabs[^]. But I admit I do use VC7.1 for remote debugging which is much improved in the new version.
John
|
|
|
|
|
norm.net wrote:
Especially people still on Visual Stduio 6.0, there can't be may positions requiring this still any more ?
Yeah, specially considering that the VC++ 6 compiler is far from standards compliant.
|
|
|
|
|
This is actually the main reason why I still use VC6. I have 500K lines of code that is vc6 compatible but will take a lot of work to get it to run under VC.NET.
John
|
|
|
|
|
You'd be surprised. A friend of mine works for a major American financial company and they are still using VS6 on W2K. They have yet to roll out XP and their programmers can only dream about using VS2003! Bummer.
The Rob Blog
Google Talk: robert.caldecott
|
|
|
|
|
I've even heard prople working NT4.0, with VS6.0, still these situtations are rare.
Blogless
|
|
|
|
|
That's what they said about COBOL programmers until year 2000 came around.
Same thing for supporting legacy C++ applications - someone needs to do it, with millions of lines around. You just can't write everything from scratch!
Inexperienced new hires seem to be really good at screwing up legacy code 
|
|
|
|
|
Blake Miller wrote:
That's what they said about COBOL programmers until year 2000 came around.
True, and some old Cobol programmer made a lot of easy cash.
Blake Miller wrote:
Same thing for supporting legacy C++ applications - someone needs to do it, with millions of lines around. You just can't write everything from scratch!
True, but that why you migrate applications to different platforms/language it's not the code, it's the ideas/design and logic that make up a computer application - maybe I'm wrong, I only have 18+ development experience 
Blogless
|
|
|
|
|
Sure, if you are migrating. Where I am working, we do not consider a new version of Windows to be a new platform. Nor is the announcement of 'Windows <whatever>' sufficient reason to rewrite 1,500,000+ lines of code. Nor is the announcement that C# or .NET is the 'latest shiny thing' a reason to rewrite 1,500,000 lines of code - ideas or no ideas. So, we need skilled, experienced C++/MFC people to maintain the product that generates this company 80 million dollars a year, and they are getting harder and harder to find. That's all I meant.
I agree, an endagnered species, but also the question implied is there a market out there, and I think the answer is that there is. Not the largest market, but there is a market.
When the time comes to migrate some mission critical code, and no one else out there can understand MFC any more, then sign me up in line to get the $500 an hour 'consulting' to the guys who only know some higher level language or construct to help them inteprpret the existing code base that they have. I would also think with 18+ years experience, you are as familiar as I am about how poorly things are documented, except perhaps in some military systems, where they are perhaps overly documented. I have only been coding since 1981 myself.
|
|
|
|
|
Blake Miller wrote:
then sign me up in line to get the $500 an hour 'consulting'
And me, that's what my retirement plan is 
Blake Miller wrote:
you are as familiar as I am about how poorly things are documented
Oh very much so, even the comments in some of the code I have seen and no help.
I suppose my real point is, people who are clinging onto MFC, hoping it has a long and healthy future as disillusioned, it's best to brush up your stills for the technologies that are gaining maturity - that is .net. As you know with your years of experience, you don't want to back yourself into a corner only to find when you finally move to another the company, your MFC skills are somewhat redundant.
Blogless
|
|
|
|
|
Blake Miller wrote:
and they are getting harder and harder to find
Any jobs going?
|
|
|
|
|
|
I Believe, Still people here in India learn there ABC for Visual or Windows programming in Visual Studio 6.0.... so i believe VS6.0 still a mature product
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
|
ThatsAlok wrote:
'05
I Believe, Still people here in India learn there ABC for Visual or Windows programming in Visual Studio 6.0
Maybe
ThatsAlok wrote:
so i believe VS6.0 still a mature product
Aged, it's now come to it's end product lifecycle.
Blogless
|
|
|
|
|
norm.net wrote:
Aged, it's now come to it's end product lifecycle.
According To Marketing research product faces four phases in product life cycle:- Introduction..( 1998) Growth(1999-2002) .... Mature(2003--- onward
and Last over ( Still have to come)..
So I believe Vs6.0 still in it Mature Phase
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)