Incorrect not all rubix cubes problems are solvable. Not if the rubix cube is taken apart at least. An inproper algorithm can result in this. I believe that the same goes for this 2 dimensional...
Type: Posts; User: inZane
Incorrect not all rubix cubes problems are solvable. Not if the rubix cube is taken apart at least. An inproper algorithm can result in this. I believe that the same goes for this 2 dimensional...
MFC uses api so how can one be better than the other. I personally prefer to use MFC because of the reduction in time. Even if I did not use the MFC I would create my own classes to wrap the API. ...
ok a couple of things...
1. usr->username on a char array(usr[60])
the -> (arrow notation is used for accesing members of a struct
or a class when the variable is pointer to the object...
try this program....
#include<iostream>
#include<string>
#include<direct.h>
using namespace std;
I had a hell of a time trying to read your code... try using the code tags next time [ CODE] foo()...[ /CODE] to make your code readible....
Anyway any updates to textboxes must meet the following...
Are you using MFC?
why do all that instead of just using the pointer to the message to write.. it is already there...
sorry change this
afx_msg void OnEdit(UINT nId);
to this..
OnFile(UINT nId)...
That is just it... If you created your menu using the menu editor use the identifiers assigned by the menu resource editor... Check the properties of the item. Place function calls to handle those...
check out the tutorials at www.codeguru.com there is a few on these subjects...
rebuild the project....(rebuild all) and insure that you provide enough time for the dialog to display....
Also why don't you create your CDialog derived class for more control....
classes should be declared in an h file...
((CMyPage*)(pSheet->GetPage(1)))->LoadCombo(m_pSet);
try casting it... or just use the page directly as you suggested
you might want to look into using kbhit()
I have not tested or intend to test the code below but I have done something
#include<conio.h>
char sEntry[4] = ""
i = 0;
while( i < 3 )
{
Use the MFC functions for instance type in the function and study the declarations of their functions... also as in the previous message most MFC books explain this naming style .....
it depends on when it needs it...
If you only need to load it once when the page is created...
do it by Handling the OnInitDialog for the property page....
other wise say for instance it changes...
look into handling the OnPaintMessage for the child windows...
and erase the background from there each time this is the only way that I can think of....
ShowError is user defined... you must define it declare it and define it your self...or leave it out....there are like a gazillion possible errors....
CPropertyPage is derived from CDialog. Therefore you can handle the OnInitDialog and load the list box there.... You would not want to handle it onSetActive since this could result in multiple loads...
you will probably have to use the gdi objects
Device context and the like in combination with
the Logical fonts LOGFONT ... which allows you to set many attibutes...such as strike out and...
its cin.getline( char *buffer, int length, char delimit = '\n')
well not exactly with those variable names but you should get the picture....
anyway also use the string class and you can do all...
how about.....
#include<iostream.h>
#include<stdio.h>
void main( void )
{
Might I suggest Practical Visual C++ by Que or isit Qeue.... anyway this is an awsome book... It was my first book I used for visual c++. I also used Jones MFC Programming with Visual C++. That...
check out the matrix sample zMan posted earlier this week...
it has some console functions including the GoToXY and changing the text color...
why that's a handle....
just kidding...
it works something like this... if this does not work email me tomorrow at [email protected]
I will send you a sample that works...
if(...