|
Problem solved, I don't know how the /clr switch got set in the project, but there it is! 
|
|
|
|
|
I have an option to make a Win32 Console Application in the New Project Wizard, that's close to what you're looking for. You could try making an empty project, too! Just include the basic dependencies you need.
|
|
|
|
|
Thanks, I figured it out. I started over with a basic W32 console application. I have no idea why my original attempt refused to function without NET installed, I started it the same way. 
|
|
|
|
|
You must've either specified a .NET console project, or turned on managed extensions (/clr switch) in your project settings.
Tech, life, family, faith: Give me a visit.
I'm currently blogging about: Homosexuality in Christianity
Judah Himango
|
|
|
|
|
As it turns out, the /clr switch was on. I'm not sure how it hapened, since I've been using VC++ 6.0 for a long time, just got started with this version.
|
|
|
|
|
I'm trying to print on a dot-matrix printer.
I want to send "raw" ascii characters to the printer (not graphics), in order to avoid the "NLQ" mode (sending raw text is the only way to print without the "NLQ").
I use OpenPrinter, StartDocPrinter, StartPagePrinter, WritePrinter, EndPagePrinter, EndDocPrinter and ClosePrinter.
But spanish characters like "eñe" (ñ Ñ), "cedilla" (ç Ç), spanish accents (á é í ó ú) and the "dieresis u" (ü) are not printed well.
I need to set the spanish charset.
I've also tried the GDI functions (creating a DC with CreateDC("WINSPOOL", printerName, NULL, NULL)), and using the stock font DEVICE_DEFAULT_FONT, but NLQ gets activated.
What else can I do?
|
|
|
|
|
You can send raw bytes of th eproper escape sequence to the printer to set it into the Spanish character set and then send those 'character' bytes out to the printer. Should print out fine then.
|
|
|
|
|
I have an SDI application with a FormView. The FormView has two buttons. One opens a CDialog derived class that is Modal and a Child.
The other opens a CDialog derived class that is Modeless and a Child.
Everything works fine when the Child style is removed and WS_POPUP is applied.
When it is applied the dialogs open up but are
(Modal and Child)
behind Mainframe with no way to get at it except minimize Mainframe. After the minimization of Mainframe the dialog does not allow one to click on it (Frame titlebar is grayed. I believe the whole dialog box is disabled.
(Modeless and Child
appears but does not allow one to click on it as the Frame titlebar is grayed. I believe the whole dialog box is disabled.
Now understand everything works as it should with the WS_POPUP style. Switch that and I get problems. The ONLY difference is the style. What is wrong?
Thanks.
//Modal Child
void CParentExamplesView::OnButton3()
{
CModalChild cmd;
cmd.DoModal();
}
//Modeless Child
void CParentExamplesView::OnButton4()
{
if (!m_pModelessChildDialog)
m_pModelessChildDialog= new CModelessChild;
if (!::IsWindow(m_pModelessChildDialog->GetSafeHwnd()))
m_pModelessChildDialog->Create(IDD_DIALOG6, this);
m_pModelessChildDialog->ShowWindow(SW_SHOW);
}
|
|
|
|
|
Dialogs SHOULD have parents!
CModalChild cmd;
cmd.DoModal(this);
m_pModelessChildDialog= new CModelessChild(this);
So give THAT a try.
|
|
|
|
|
Thanks,
DoModal() doesn't take any parameters
The modeless example IS passing in the parent.
Regardless if you don't pass in any parents the mainframe is the owner.
Still no answers.
|
|
|
|
|
mx483 wrote:
Now understand everything works as it should with the WS_POPUP style. Switch that and I get problems.
So why are you not wanting to use WS_POPUP? You've not indicated that you would rather use WS_CHILD. All I can gather is that you've found something that works and want to know why.
"One must learn from the bite of the fire to leave it alone." - Native American Proverb
|
|
|
|
|
Actually..
I found something that didn't work and wanted to know why. This is how I learn. I have no need to use the dialog as a child in modal or modeless...yet, but knowing why something does and doesn't work is paramount in continuing my growth as a programmer. I realize most people just solve a problem and blindly move on never really gaining from the experience. Solidifying concepts is what I'm trying to do. I really hoped people wouldn't constantly ask why I want to do this or that. My question was not a should or shouldn't but rather a why. I appreciate your taking the time to answer though.
|
|
|
|
|
Anonymous wrote:
I found something that didn't work and wanted to know why.
Really? When I read your post, it's easy to come away with a different impression. Consider, "I'm trying to drive a nail into a board with a hammer. Now understand everything works as it should with the nail. Switch that to a screw instead and I get problems. What is wrong?" Or, "I'm trying to drive my car with round tires. Now understand everything works as it should with the round tires. Switch that to out-of-round tires instead and I get problems. What is wrong?" See the confusion?
Anonymous wrote:
I really hoped people wouldn't constantly ask why I want to do this or that. My question was not a should or shouldn't but rather a why.
While I certainly understand and applaud your situation, what I have found over the years is that when folks get stuck and ask for help, it is usually because they are doing something wrong (at the design level) that should never have been done to begin with. This is especially true with MFC. Most folks, especially new ones, have no idea what MFC is doing behind the scenes. They've learned it from the outside-in rather than from the inside-out. Knowing what the underlying Win32 SDK is actually doing is very important in making a successful application. Consequently they make erroneous assumptions (e.g., "But I thought message maps worked this way."), thus leading to a situation where they are trying to solve a problem that was doomed from the start.
That said, MSDN clearly states:
Do not use the WS_CHILD style with a modal dialog box. The DialogBox function always disables the parent/owner of the newly created dialog box. When a parent window is disabled, its child windows are implicitly disabled. Since the parent window of the child-style dialog box is disabled, the child-style dialog box is too.
"One must learn from the bite of the fire to leave it alone." - Native American Proverb
|
|
|
|
|
And by stating the MSDN position you have answered the why! Thanks, that's all I wanted. Now I know not to do it and am richer for having asked. If I had known MSDN's position, which I was not able to locate in any of the help, I never would have asked in the first place.
"One does not have to get burned to actually learn that fire is hot. Otherwise we would all be dead" mx483
|
|
|
|
|
Hi Every body
How to read a comma seperated file in VC++
Thanks in advance
|
|
|
|
|
Use strtok[^]
... she said you are the perfect stranger she said baby let's keep it like this... Tunnel of Love, Dire Straits.
|
|
|
|
|
marcdev wrote:
Use strtok[^]
Are you sure that strtok reads a file??  
|
|
|
|
|
Obviously not, but the question is not how to read a file ... Maybe you need that I was more specific:
1st. Open the file.
2nd. Read each line putting it in a string.
3rd. Process the string using strtok to separate it by commas.
Is strtok useful now ? 
Marc Soleda.
... she said you are the perfect stranger she said baby let's keep it like this... Tunnel of Love, Dire Straits.
|
|
|
|
|
Hi
There may be other more elegant ways, but unless you are reading millions of entries, this works just fine. The char variable is read and then ignored, you only store or use the datx as you wish.
char separator;<br />
ifstream FileIn("C:\\SampleData\\divedata.dat");<br />
FileIn >> dat1 >> separator >> dat2 >> separator >> dat3 >> separator >> dat4;
Good luck
|
|
|
|
|
knapak wrote:
here may be other more elegant ways, but unless you are reading millions of entries, this works just fine. The char variable is read and then ignored, you only store or use the datx as you wish.
char separator;
ifstream FileIn("C:\\SampleData\\divedata.dat");
FileIn >> dat1 >> separator >> dat2 >> separator >> dat3 >> separator >> dat4;
This can hardly work!
Good luck
Agreed 
|
|
|
|
|
It would be more useful if you could explain why this can hardly work and provide examples of the alternatives. I've used it extensively and had no problems at all, but if there's a good reason to do something else we would be very happy to oblige. Otherwise is just empty discourse. Every time you assign a value to a variable, it takes the new value. If the variable is not used at all, given it is a single char variable, virtually no memory is wasted... why wouldn't it work?
|
|
|
|
|
knapak wrote:
It would be more useful if you could explain why this can hardly work
Try this line with your code:
This,is,a comma seperated,line
|
|
|
|
|
Fine, if you are mostly writing programs that deal with strings of characters, I can see the problem. However, it seems that were are here talking about reading ONLY numeric data, in which case my approach won't fail and IS SIMPLER.
Nevertheless, if you think your solution is more "elegant" why don't you provide a more comprehensive response, something beyond "use this", with clear sample code.
Cheers
|
|
|
|
|
knapak wrote:
Nevertheless, if you think your solution is more "elegant" why don't you provide a more comprehensive response, something beyond "use this", with clear sample code.
Why not just look at (and re-use) something others have already done, at CodeProject or elsewhere?
XTokenString[^]
string tokenize[^]
|
|
|
|
|
for example:
DirA = "c:\windows\system"
DirB = "c:\private\doc"
A realtive to B = ..\..\private\doc
how to implement this?
thanks in advance.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
