|
Roger Allen wrote:
If its just the number of lines the control could display without a scrollbar, then you can compute this by gettting the client area size of the control, the DC and the font, and then count the number of lines like this:
thousand thanks, Roger! 
|
|
|
|
|
PS: instead of GetDC/ReleaseDC I might better use a CClientDC(this), which is an MFC encapsulation of this AFAIK.
|
|
|
|
|
Just came across this. Very good sample collection on connection string format, just want to share it with u all:
http://www.able-consulting.com/MDAC/ADO/Connection/OLEDB_Providers.htm#OLEDBProviderForSQLServer
And to moderator:
is it possible that u put a similar tutorial on your site? It's very handy and will be very helpful later on.
Thanks.
norm
norm
|
|
|
|
|
|
I have a background in my CListCtrl. I don't want it to scroll though. How does one stop that from happening? Thanks for any help.
|
|
|
|
|
Repaint the background everytime you do any scroll event, perhaps?
But you'll need to double buffer your painting to prevent flicker I think!
Perhaps not much for help this but anyway...
Rickard Andersson@Suza Computing
C# and C++ programmer from SWEDEN!
UIN: 50302279
E-Mail: nikado@pc.nu
Speciality: I love C#, ASP.NET and C++!
|
|
|
|
|
I was wondering if anyone here has had any experience with using Waitable timers.
I am in the process of writing a scheduler, similar to SQL Server's Job scheduling utility. The reason i need it is because SQL server doesn't meet all of my criterias.
Now, I have been reviewing various ways of scheduling jobs and I posted earlier on this topic, except for it got buried under various other posts.
I was wondering whether Waitable Timers or TimerQueues are good candidates for a scheduling device? I guess what I would be doing is create all these timers for every job scheduled and then waitonmultiple objects. And I guess my WaitOnMulitple object parameter must be set to true, to allow things to go through as soon as they are signalled.
So, are there any issues and problems that these two suffer from?
thanks
|
|
|
|
|
I'm ranging through a CEdit object's lines, but every time I do the following, LineLength() returns the length of the first edit line. 
Any help? I understand this function, LineLength(i), to return the length of the edit control line, whose index is zero-based, i. That much is correct, right?
CString sLine;
for(int i=0; i<m_Edit->GetLineCount();i++)
{
m_Edit->GetLine(i, sLine.GetBuffer(m_Edit->LineLength(i)), m_Edit->LineLength(i));
...
...
}
BW
"I'm coming with you! I got you fired, it's the least I can do. Well, the least I could do is absolutely nothing, but I'll go you one better and come along!"
- Homer J. Simpson
|
|
|
|
|
Have you tried the following instead?
CString sLine;
for(int i=0; i<m_edit->GetLineCount();i++)
{
m_Edit->GetLine(i, sLine);
...
...
}
(I would've tried this on my machine -- but I'm building a huge project at the moment..)
"No one goes to hell because of their sin, but because of rejecting God's method of salvation: His Son's life for yours..."
"It does not take a majority to prevail ... but rather an irate, tireless minority, keen on setting brushfires of freedom in the minds of men." --Samuel Adams
|
|
|
|
|
The MSDN says LineLength returns the length of the line which contains the character at index "nLine" (I know, great way to name the parameters MS!). So, to get the length of a specified (actual) line index, we'll use LineIndex in conjunction with LineLength:
m_Edit->GetLine(i, sLine.GetBuffer(m_Edit->LineLength(i)), m_Edit->LineLength(m_Edit->LineIndex( i )));
Chris Richardson
Programmers find all sorts of ingenious ways to screw ourselves over. - Tim Smith
|
|
|
|
|
BTW, this worked for me.
Thanks!
BW
"I'm coming with you! I got you fired, it's the least I can do. Well, the least I could do is absolutely nothing, but I'll go you one better and come along!"
- Homer J. Simpson
|
|
|
|
|
Hello everyone,
I have a question about multithreading and syncing data. I have two threads A and B; A feeds data to a cache in B then waits until B is finished with its cache. Example in Pseudo code:
The Mutexes were taken out for code clarity.
A thread:
{
for (I=0; I < 5; ++I)
B->loadData(i);
B->Wait(); // Now wait for thread B to finish processing data.
...
}
B Thread
{
Handle dwWait;
Handle dwRun;
Vector<int> vI;
ThreadFunc()
{
while (1)
{
WORD wdCheck = WaitForSingleObject(dwRun, INFINITE);
switch (wdCheck)
{
case: 0
{
for (int I = 0; I < vI.size(); ++I)
...
SetEvent(dwWait); // Now vector is empty send event.
}
case: 1
{
}
}
}
void Wait()
{
WaitForSingleObject(dwWait, INFINITE);
}
void loadData(int I)
{
vI.push_back(I);
SetEvent(dwRun);
}
}
My question is, why doesn’t thread A always wait for Thread B to finish before continuing on.
Thanks in advance.
Ken
|
|
|
|
|
The key is in the piece of pseucode:
for (I=0; I < 5; ++I)
B->loadData(i); This feeds the cache with 5 ints, signalling dwRun after inserting each int. So, imagine the following (possible) pattern of execution:- A feeds the 1st
int.
- A sets
dwRun.
- The system yields controls to B.
- B processes the cache (containing only one
int) and sets dwWait.
- The system yields controls to A.
- A loads the remaining four
ints, setting dwRun after each insertion.
- A
Waits and exits immediately, as dwWait is already set. There's still some data in B's cache.
See the problem now?
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
|
Thanks for your help and time, Joaquín 
I see, so the event is already set by the time the wait function is called by A. Thus that is why Thread A does not always wait for Thread B. So how would one go about fixing this dilemma? Perhaps by putting another mutex around the wait function call? Or maybe use a while loop in the Wait function that checks if the vector is empty? Are there any examples of something like this that I could refer to?
Example:
void Wait() // While loop checking size of vector.
{
while (vI.size() != 0)
WaitForSingleObject(dwWait, INFINITE);
} // But this does not seem like a very clean solution.
Thanks again for your help.
Ken
|
|
|
|
|
The easiest solution is probably to split LoadData into two functions, say LoadData and Run, the first feeding the cache and the second setting dwRun, and call Run only when finished pushing the data.
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
|
Thanks again.
Another possible solution that I came up with, which is to reset dwWait in the Wait function. This seems to work??? But I'm wondering if there is an even cleaner way to solve this?
Example:
void Wait()
{
if (vI.size() != 0)
{
ResetEvent(dwWait); // This will make sure to wait for event.
WaitForSingleObject(dwWait, INFINITE);
}
}
Thanks for all of the help.
Ken
|
|
|
|
|
Watch out, this solution you propose is broken! The possibility of deadlock is minimal, but this is even worse, as chances are you don't notice anything till it's too late and the app has been released. Counterexample:- A feeds the data.
- A checks
vI.size()!=0. This evaluates to true (B has not been given access by the system yet).
- Thread switch: B begins executing, process the whole data and sets
dwWait.
- Thread switch: A resets
dwWait and wait for completion --for ever.
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
|
Hi again,
Ok, here is my latest attempt to resolve this.
Handle mMutex;
mMutex = CreatMutex(...);
ThreadFunc()
{
while (1)
{
WORD wdCheck = WaitForSingleObject(dwRun, INFINITE);
switch (wdCheck)
{
case: 0
{
WaitForSingleObject(mMutex, INFINITE); // New code here.
for (int I = 0; I < vI.size(); ++I)
...
ReleaseMutex(mMutex); // New code here.
SetEvent(dwWait); // Now vector is empty send event.
}
case: 1
{
}
}
}
void Wait()
{
WaitForSingleObject(mMutex, INFINITE); //New code here.
if (vI.size() != 0)
{
ResetEvent(dwWait); // This will make sure to wait for event.
ReleaseMutex(mMutex); // New code here.
WaitForSingleObject(dwWait, INFINITE);
}
ReleaseMutex(mMutex); // New code here.
}
Wooweee, I think I got it right this time.
Again thanks for all of your help.
Ken
|
|
|
|
|
Is there a way to prevent a modal dialog from closing when a user initiates the WM_CLOSE?
I'm handling WM_CLOSE message using my own OnClose() where I display a message box with YESNOCANCEL. If the user selects CANCEL I want to return them to the current dialog, unharmed. I tried just returning before executing CDialog::OnClose(), but it still closes and ends the application.
I've read many suggestions within the forum and nothing seems to do what I want, all result in the dialog closing and app ending.
-kg
Ken Goguen
|
|
|
|
|
This is done Handling the WM_CLOSE..
void CTestDlg::OnClose()
{
if(MessageBox("Close?","Really?",MB_YESNOCANCEL)== IDYES)
{
CDialog::OnClose();
}
else
{
}
}
|
|
|
|
|
Like I said, that's what I am doing and it still closes...
void CMyDlg::OnClose()
{
if (curFileDirty) {
int answer=MessageBox( "Changes have been made. Would you like to Save them?", "Warning", MB_YESNOCANCEL | MB_ICONQUESTION );
if (answer==IDYES) {
if (currentPrjFilePath=="")
OnFileSaveAsConsolidation();
else
OnFileSaveConsolidation();
finalClose();
CDialog::OnClose();
}
if (answer==IDNO) {
finalClose();
CDialog::OnClose();
}
}
}
Ken Goguen
|
|
|
|
|
Ummm... Override also OnOK and OnCancel to do-nothing functions and see what happens.
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
|
You need to do what RobJones showed in handing your OnClose. Note in particular, do *NOT* call CDialog::OnClose if you don't want to close the dialog!
Also, you will probably have to override OnOK and OnCancel and do something simimlar there, if your dialog has OK and Cancel buttons.
Even a broken clock is right twice a day.
|
|
|
|
|
When I include a manifest (XML) file to use the Common Controls version 6 in the Resource or the path, and I call ::MessageBox(NULL, TEXT("Hello"), TEXT("Hello"), MB_OK), the messagebox isn't shown (I only hear a sound), if I do not include the manifest everything works fine.
It goes even wrong when I do:
#include "resource.h"
#include <tchar.h>
#include <windows.h>
int __stdcall
_tWinMain (HINSTANCE hInstance, HINSTANCE, TCHAR * lpCmdLine, int mainFrameDisplayMode)
{
MessageBox(NULL, TEXT("Hello"), TEXT("Hello"), MB_OK);
}
Sjoerd van Leent
LPCTSTR Dutch = TEXT("Double Dutch ");
|
|
|
|
|
This is most weird! Try adding the flag MB_ICONINFORMATION as well as MB_OK (Just a guess) .
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
