This is NOT a question
-
Given my (relatively) advanced years, I'm allowed to be a grumpy old man. I'm now exercising that right (and I recognise that no right exists without responsibility, and it's part of that responsibility towards the usefulness of CP as a contributor via the forums that makes me act). MFC is a set of foundation classes to make working with Win32 easier. That's 'easier', not necessarily 'easy'. It helps tremendously if you can learn about the Win32 API itself while you are using MFC, because some day you will need to write something that there's no wrapper for. Go and read Petzold, or actually read the MSDN documentation. At a push, step into some of the source of MFC. But do something that will actually advance your knowledge of the area you're working in. If you're doing CS in college, pay more attention when your proposed assignments or homework are being discussed. If you don't want to do the work, you won't reap the reward (or if you do, it won't last past your first week in a new job). If you're doing this for a living (which many of us here are), recognise that hey, we are all in the same boat here, and it pays to be polite, and help where you can. Unless I missed a memo somewhere, no one actually gets paid to help anyone else on here, so if you come across as insufferably rude, you won't get much help. If I see "URGENT: PLEASE HELP", I tend to skip that. No point helping people who can't plan properly :)
Steve S Developer for hire
-
Given my (relatively) advanced years, I'm allowed to be a grumpy old man. I'm now exercising that right (and I recognise that no right exists without responsibility, and it's part of that responsibility towards the usefulness of CP as a contributor via the forums that makes me act). MFC is a set of foundation classes to make working with Win32 easier. That's 'easier', not necessarily 'easy'. It helps tremendously if you can learn about the Win32 API itself while you are using MFC, because some day you will need to write something that there's no wrapper for. Go and read Petzold, or actually read the MSDN documentation. At a push, step into some of the source of MFC. But do something that will actually advance your knowledge of the area you're working in. If you're doing CS in college, pay more attention when your proposed assignments or homework are being discussed. If you don't want to do the work, you won't reap the reward (or if you do, it won't last past your first week in a new job). If you're doing this for a living (which many of us here are), recognise that hey, we are all in the same boat here, and it pays to be polite, and help where you can. Unless I missed a memo somewhere, no one actually gets paid to help anyone else on here, so if you come across as insufferably rude, you won't get much help. If I see "URGENT: PLEASE HELP", I tend to skip that. No point helping people who can't plan properly :)
Steve S Developer for hire
Steve S wrote:
Go and read Petzold, or actually read the MSDN documentation.
Word!
-
Given my (relatively) advanced years, I'm allowed to be a grumpy old man. I'm now exercising that right (and I recognise that no right exists without responsibility, and it's part of that responsibility towards the usefulness of CP as a contributor via the forums that makes me act). MFC is a set of foundation classes to make working with Win32 easier. That's 'easier', not necessarily 'easy'. It helps tremendously if you can learn about the Win32 API itself while you are using MFC, because some day you will need to write something that there's no wrapper for. Go and read Petzold, or actually read the MSDN documentation. At a push, step into some of the source of MFC. But do something that will actually advance your knowledge of the area you're working in. If you're doing CS in college, pay more attention when your proposed assignments or homework are being discussed. If you don't want to do the work, you won't reap the reward (or if you do, it won't last past your first week in a new job). If you're doing this for a living (which many of us here are), recognise that hey, we are all in the same boat here, and it pays to be polite, and help where you can. Unless I missed a memo somewhere, no one actually gets paid to help anyone else on here, so if you come across as insufferably rude, you won't get much help. If I see "URGENT: PLEASE HELP", I tend to skip that. No point helping people who can't plan properly :)
Steve S Developer for hire
-
Given my (relatively) advanced years, I'm allowed to be a grumpy old man. I'm now exercising that right (and I recognise that no right exists without responsibility, and it's part of that responsibility towards the usefulness of CP as a contributor via the forums that makes me act). MFC is a set of foundation classes to make working with Win32 easier. That's 'easier', not necessarily 'easy'. It helps tremendously if you can learn about the Win32 API itself while you are using MFC, because some day you will need to write something that there's no wrapper for. Go and read Petzold, or actually read the MSDN documentation. At a push, step into some of the source of MFC. But do something that will actually advance your knowledge of the area you're working in. If you're doing CS in college, pay more attention when your proposed assignments or homework are being discussed. If you don't want to do the work, you won't reap the reward (or if you do, it won't last past your first week in a new job). If you're doing this for a living (which many of us here are), recognise that hey, we are all in the same boat here, and it pays to be polite, and help where you can. Unless I missed a memo somewhere, no one actually gets paid to help anyone else on here, so if you come across as insufferably rude, you won't get much help. If I see "URGENT: PLEASE HELP", I tend to skip that. No point helping people who can't plan properly :)
Steve S Developer for hire
If I were stood next to you right now I would shake your hand, pat you on the back and run away with your cane. Learning to use a wrapper, in my opinion, is not learning to code. I see many programs and especially libraries that are coded in MFC, much of the time it's unwarrented. We all know MFC apps come with baggage. If the project is a large scale multi media library, then no problem. But I don't want to download a 3mb calculator, nor would I expect anybody else to. What pains me the most is to see an excellent code sample that would greatly help in one of my projects, only for it to be MFC only. There are very few projects/articles on here that cater for non MFC users. Is it so difficult for people to test what is defined?
-
If I were stood next to you right now I would shake your hand, pat you on the back and run away with your cane. Learning to use a wrapper, in my opinion, is not learning to code. I see many programs and especially libraries that are coded in MFC, much of the time it's unwarrented. We all know MFC apps come with baggage. If the project is a large scale multi media library, then no problem. But I don't want to download a 3mb calculator, nor would I expect anybody else to. What pains me the most is to see an excellent code sample that would greatly help in one of my projects, only for it to be MFC only. There are very few projects/articles on here that cater for non MFC users. Is it so difficult for people to test what is defined?
-
Given my (relatively) advanced years, I'm allowed to be a grumpy old man. I'm now exercising that right (and I recognise that no right exists without responsibility, and it's part of that responsibility towards the usefulness of CP as a contributor via the forums that makes me act). MFC is a set of foundation classes to make working with Win32 easier. That's 'easier', not necessarily 'easy'. It helps tremendously if you can learn about the Win32 API itself while you are using MFC, because some day you will need to write something that there's no wrapper for. Go and read Petzold, or actually read the MSDN documentation. At a push, step into some of the source of MFC. But do something that will actually advance your knowledge of the area you're working in. If you're doing CS in college, pay more attention when your proposed assignments or homework are being discussed. If you don't want to do the work, you won't reap the reward (or if you do, it won't last past your first week in a new job). If you're doing this for a living (which many of us here are), recognise that hey, we are all in the same boat here, and it pays to be polite, and help where you can. Unless I missed a memo somewhere, no one actually gets paid to help anyone else on here, so if you come across as insufferably rude, you won't get much help. If I see "URGENT: PLEASE HELP", I tend to skip that. No point helping people who can't plan properly :)
Steve S Developer for hire
-
Steve S wrote:
we are all in the same boat here
Yeah but some of us should always wear a life Jacket while others should just stay on dry land at get their fish filet at McDonalds. Don't ask, I have no idea what that means. :-D
led mike
led mike wrote:
some of us should always wear a life Jacket while others should just stay on dry land at get their fish filet at McDonalds
Mind if I use that as a signature?? :-D
-
led mike wrote:
some of us should always wear a life Jacket while others should just stay on dry land at get their fish filet at McDonalds
Mind if I use that as a signature?? :-D
-
Given my (relatively) advanced years, I'm allowed to be a grumpy old man. I'm now exercising that right (and I recognise that no right exists without responsibility, and it's part of that responsibility towards the usefulness of CP as a contributor via the forums that makes me act). MFC is a set of foundation classes to make working with Win32 easier. That's 'easier', not necessarily 'easy'. It helps tremendously if you can learn about the Win32 API itself while you are using MFC, because some day you will need to write something that there's no wrapper for. Go and read Petzold, or actually read the MSDN documentation. At a push, step into some of the source of MFC. But do something that will actually advance your knowledge of the area you're working in. If you're doing CS in college, pay more attention when your proposed assignments or homework are being discussed. If you don't want to do the work, you won't reap the reward (or if you do, it won't last past your first week in a new job). If you're doing this for a living (which many of us here are), recognise that hey, we are all in the same boat here, and it pays to be polite, and help where you can. Unless I missed a memo somewhere, no one actually gets paid to help anyone else on here, so if you come across as insufferably rude, you won't get much help. If I see "URGENT: PLEASE HELP", I tend to skip that. No point helping people who can't plan properly :)
Steve S Developer for hire
-
If I were stood next to you right now I would shake your hand, pat you on the back and run away with your cane. Learning to use a wrapper, in my opinion, is not learning to code. I see many programs and especially libraries that are coded in MFC, much of the time it's unwarrented. We all know MFC apps come with baggage. If the project is a large scale multi media library, then no problem. But I don't want to download a 3mb calculator, nor would I expect anybody else to. What pains me the most is to see an excellent code sample that would greatly help in one of my projects, only for it to be MFC only. There are very few projects/articles on here that cater for non MFC users. Is it so difficult for people to test what is defined?
Win32 coding is lot better than MFC . For example , I did my first TCP server using CSocket . I tried to use the same CSocket in a console application . I was able to create,bind and listen on the server object -but I was surprised to find that OnAccept() never fired when clients attempted connections ! . It took me a while to realise that in a console app, if we use CSocket, then the messages won,t be pumped to the socket layer . Someone suggested me to use a invisible framewnd class to act as message handler ! So lets learn it in the right way (hard way ?)- Win32
redindian