|
You have resolved the mystery that has been plaguing me for a week!!!!! I cant thank you enough!
Where did you learn about the 1001? Is it in MSDN ? Does the listbox part of the combo have a "code number" too? 1002?
Appreciate your help,
ns
|
|
|
|
|
Glad to have helped. 
I don't recall how I learned about the edit control's ID, but I had actually forgotten that it was 1001. I knew it had some fixed number, but I couldn't remember it. So I googled for "ID of edit control of combo box" and found the answer in an article in CodeGuru.
Regards,
Alvaro
When birds fly in the right formation, they need only exert half the effort. Even in nature, teamwork results in collective laziness. -- despair.com
|
|
|
|
|
Hello,
I currently work on a MFC C++ application with Visual 6.0.
This application have to manage 2 screen, 1 with the main Windows display, the second have to display a bmp or jpeg picture.
Does someone know how to manage the second screen ?
Thank you !
Paul JOACHIM
|
|
|
|
|
I don't know if that's what you want but you can use a splitter window (this will divide the screen like, for example, the file explorer).
Take a look at CSplitterWnd documentation !
What kind of project do you use?? Dialog based or SDI/MDI ?? The Splitter window is easy to implement in a SDI application.
|
|
|
|
|
Thank you for your answer. But I can't use a splitter windows because I work whith a existing application and I can't change its display. I just can add a second video flow (just for display bmp and jpeg picture).
Do you have an other idee ?
|
|
|
|
|
I studied the CSplitterWnd class like Cedric proposed me, and I think my first message was not clear. When I say "I want to manage 2 screen", I mean "2 monitor". So the CSplitterWnd class is not good for me.
|
|
|
|
|
hi
i am looking to read an wav file into an activeX windows mediaplayer
i know the location of my file, but i dont know how to get it to play
it seems to open, but what do i need to do to make it play.
help....i am a novice so be gentle
this is what i have got so far, im missing the bit i need to put in the try bit
char* message = ("D:\\callparent\\new_name\\020612125252-33381.wav");
CFile myFile(message,
CFile::modeCreate|CFile::modeNoTruncate|CFile::modeWrite|CFile::typeBinary|CFile::shareDenyNone);
try
{
return TRUE;
}
catch(CException* pE)
{
pE->ReportError();
pE->Delete();
myFile.Close();
return FALSE;
} 
|
|
|
|
|
What is this "activeX windows mediaplayer"? Is it a control in your dialog box? How did you add it? Please provide more info.
Regards,
Alvaro
When birds fly in the right formation, they need only exert half the effort. Even in nature, teamwork results in collective laziness. -- despair.com
|
|
|
|
|
Use:
#include <mmsystem.h>
sndPlaySound(...)
without any fileopen, etc.
Best regards, Alex.
================================
Useful links
|
|
|
|
|
hi,
I'm developing a program that uses linked list's as a cover for the database. So i have list's of >1000 struct's. wenn i shut down my program i get memory dumps:
C:\projecten\PLCServer 0.2\DBVoorraadBeheer.cpp(63) : {3263} normal block at 0x06B95498, 44 bytes long.<br />
Data: < dU U U > 01 00 00 00 64 55 B9 06 0C 55 B9 06 BC 55 B9 06 <br />
strcore.cpp(118) : {3262} normal block at 0x06B95440, 15 bytes long.<br />
Data: < A > 01 00 00 00 01 00 00 00 02 00 00 00 41 00 00 <br />
strcore.cpp(118) : {3261} normal block at 0x06B953B8, 67 bytes long.<br />
Data: < 6 Spir> 01 00 00 00 1B 00 00 00 36 00 00 00 53 70 69 72 <br />
strcore.cpp(118) : {3260} normal block at 0x06B95360, 25 bytes long.<br />
Data: < 0700> 01 00 00 00 06 00 00 00 0C 00 00 00 30 37 30 30 <br />
strcore.cpp(118) : {3259} normal block at 0x06B95308, 25 bytes long.<br />
Data: < Cool> 01 00 00 00 06 00 00 00 0C 00 00 00 43 6F 6F 6C
how can i prevent this?
[]D [] []D []
|
|
|
|
|
Willem B wrote:
how can i prevent this?
delete all objects/memory that you allocate with 'new' and free all memory you allocate with 'malloc'.
-c
Image tools: ThumbNailer, Bobber, TIFFAssembler
|
|
|
|
|
is it harmfull if i let the compiler delete it?
[]D [] []D []
|
|
|
|
|
|
Willem B wrote:
is it harmfull if i let the compiler delete it?
It just won't do it: You told him that you wanted memory (new), got it (new succeeded), and now you have to tell him that you dont want it anymore (delete).
If you want it automatic, then don't new your variables!
|
|
|
|
|
Anything allocated with new or malloc is not "deleted" by the compiler. It needs to be cleaned up with "delete", "free", or you can just let it happen when the program exits. However, if the program runs for a while, more and more memory may continue to be allocated and eventually you'll run out of it, causing the program to crash.
The only memory the compiler cleans up automatically is the stack, which you can use to efficiently allocate any variable:
{
CString s = "allocated on the stack so it will be free automatically";
CString* p = new CString("allocated on the heap, needs to be freed with delete");
delete p;
}
Regards,
Alvaro
When birds fly in the right formation, they need only exert half the effort. Even in nature, teamwork results in collective laziness. -- despair.com
|
|
|
|
|
I have a listctrl for logging. Logging can be activated or deactivated. When logging is deactivated, I want to make the text and background grayer grayer. I know how to use CustomDraw, but how do you make colors grayer? Anyone got a clue?
|
|
|
|
|
Gray is an equal combination of red, green and blue color values.
Jason Henderson
"You must be the change you wish to see in the world." - Gandhi
articles profile
|
|
|
|
|
Ok, but that doe not make me a lot wiser. How do I actualy translate color values to gray values or to their darker equvalents?
|
|
|
|
|
Most GDI functions take a COLORREF which defines the color you want the GDI object to be. A COLORREF is made up of red, green and blue components and you can use the RGB(r,g,b) macro to get a COLORREF.
So basically, to make the color darker, you could decrease the red, green, and blue values by the same percentage. To make it grayer, you could extract the red, green and blue values from the original color then equalize each value toward a set value of gray, say RGB(192,192,192). Here's an example of making orange grayer:
Original Orange:
Red = 236
Green = 122
Blue = 0
Gray value:
R = 192
G = 192
B = 192
if (original value > gray value)
new value = original value - (original value - gray value)/2
else
new value = original value + (gray value - original value)/2
New values:
R = 214
G = 157
B = 96
ORIGINAL COLOR
NEW COLOR
Darken example using original orange and a percantage value of 50%:
New values:
R = 118
G = 61
B = 0
DARKENED COLOR
Jason Henderson
"You must be the change you wish to see in the world." - Gandhi
articles profile
|
|
|
|
|
Thanx!! This is exactly what I was looking for. 
|
|
|
|
|
What do you mean greyer ? Make them darker ? lighter ?
You can convert the RGB values to HSV and modify the V value to make the color darker or lighter.
Max.
Maximilien Lincourt
For success one must aquire one's self
|
|
|
|
|
#define NEXT_INDEX ????<br />
<br />
void something()<br />
{<br />
int A0 = NEXT_INDEX;
int A1 = NEXT_INDEX;
int A2 = NEXT_INDEX;
...<br />
...<br />
}
Hi, how can I define NEXT_INDEX macro so that it increments by one, each time the compiler parses it?
|
|
|
|
|
You can use a static variable that you increment with the macro. Something that looks like:
<br />
static int StaticIndex = 0;<br />
#define NEXT_INDEX StaticIndex++;<br />
This should work!
|
|
|
|
|
This would increment the index at runtime. What I need is the pre-processor to increment the index as it compiles so that the indices are found at compile time and fixed at runtime.
Something like this (which will not compile..)
#define AAA 0<br />
<br />
#define NEXT_INDEX<br />
{<br />
AAA
#define AAA (AAA+1) //next time it is incremented by one<br />
}
First time using NEXT_INDEX it compiles to AAA (which is 0 at first), next time I want it to compile to 1. This setup imo makes sence, but not to the compiler..
|
|
|
|
|
IMHO, there is no way of storing information at compile time. So, there is no way of storing a numbeer, incrementing and using it at compile time.
It's not the fall that kills you: it's the sudden stop - Down by Law, Jim Jamursch (1986)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
