|
|
The Windows functions still faithfully keep a return code (MK_MBUTTON = 16) for if the middle mouse button is down. Can computer mice with 3 buttons still be bought? Or have they gone where the passenger pigeon went?
|
|
|
|
|
This is hardly a question for a C++ forum? You can find different mouse types in any PC store.
|
|
|
|
|
Many mice have a scroll wheel which is also the middle button. If you have such a mice, just try to press the wheel instead of scrolling it.
So only the simplest / cheapest mice have only two buttons. Many even have more than three buttons nowadays.
|
|
|
|
|
print these numbers 6 28 66 in form of pyramid like
00006
00028 00066
|
|
|
|
|
1) Do not repost. You have already posted this homework question in the thread immediately below.
2) We do not do your homework. It's set to test what you know, not how good you are at getting strangers on the Internet to do your work for you.
Try it yourself, and you'll probably find it's not as difficult as you think. After all, it will be based on topics you've recently covered in your course.
If you're still stuck, then talk to your teacher.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
print these numbers 6 28 66 in form of pyramid like
00006
00028 00066
|
|
|
|
|
It's called string formatting and you want leading zeros
Here is the full reference
printf - C++ Reference[^]
Look at the sample with leading zeros ... which will be in your case you want 6 digits
printf ("Preceding with zeros: %06d \n", 6);
printf("Preceding with zeros: %06d \n", 28);
printf("Preceding with zeros: %06d \n", 66);
In vino veritas
|
|
|
|
|
Hereinafter, / should be backslash.
I am working on a recursive directory search function. It uses FindFirstFile, FindNextFile, WIN32_FIND_DATA info; , etc. It seems to work. If while working on directory X it comes across a subdirectory X/Y, it calls itself recursively to search the contents of directory X/Y (unless the directory's name starts with a fullstop). OK so far.
But, if the function recurses (say) 6 deep in a deep nest of directories, then the computer will have to keep tract of 6 FindFirstFile, FindNextFile, WIN32_FIND_DATA info; directory scan processes at once. Can I trust the computer to keep tract of all that lot at once and not trip over itself?
|
|
|
|
|
When you say "the computer", do you mean your application, or the windows system? If the former then only you can say; if the latter then: yes.
|
|
|
|
|
If the function recurses (say) 6 deep in a deep nest of directories, then each recursion level would have to keep track of a level of the directory tree, by a FindFirstFile, FindNextFile, WIN32_FIND_DATA info; directory scan process, all 6 at the same time. Can one application be trusted to run these 6 FindFirstFile, FindNextFile , WIN32_FIND_DATA info; directory-scans at once?
modified 29-Jul-16 17:58pm.
|
|
|
|
|
Anthony Appleyard wrote: Can one application be trusted to run these 6 FindFirstFile, FindNextFile , WIN32_FIND_DATA info; directory-scans at once?
Well it isn't doing them all at once, it is doing them one at a time. If you are concerned about testing your application it is easy enough to create a structure to run your application on. But be aware of the limitations imposed by the MAX_PATH constant as described at FindFirstFile function (Windows)[^].
|
|
|
|
|
When the function is called again, all of the context information is pushed onto the stack and the new function call starts. When the function unwinds, the most recent context information is popped from the stack and the function picks up where it left off. This is all handled automatically by the system.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
Im using this for the first time for mapping a function "f" with variable count of parameters
declarition:
template <class...A> void AllItemsO(void (*f)(A...), A... args)
{
}
call in cpp:
AllItemsO<IapVisibilityInfo*, IPickCookie*, MakeSubObjSpecial, AVHC(Object)&>(&IcompDWO3D::SetObjMat, visInfo, pci, doit, obj);
function to call is:
IcompDWO3D::SetObjMat
parameters:
visInfo, pci, doit, obj
compiler always shows up an error C2784
Fehler 1 error C2784: "void CapDWOICollection::AllItemsO(void (__cdecl *)(A...),A...)": template-Argument für "void (__cdecl *)(IapVisibilityInfo *,IPickCookie *,aprivis::MakeSubObjSpecial,aprivis::avhObjectWrapper &,A...)" konnte nicht von "void (__thiscall component::IcompDWO3D::* )(IapVisibilityInfo *,IPickCookie *,aprivis::MakeSubObjSpecial,aprivis::avhObjectWrapper &)" hergeleitet werden.
looking at what I have shown bold, it seems that it cannot spread the functionparameters form the A... variadic to single paarameters?
A non variadic verison with 2 Parameters looks like this and works:
template <class T1, class T2> void AllItemsO2(void (*f)(T1, T2), T1 p1, T2 p2)
{ for (auto _F : *this) if (_F) ((_F)->*f)(p1, p2); }
any help for my syntax?
|
|
|
|
|
I've got this the following code snippets... when compiling, I kept on getting error: implicit declaration of function. This "eeprom_memory_update_byte" came from avr/eeprom.h. What I am trying to update the atmel processor eeprom memory (not write, but to update)
In commands.c (in a function):
bool Update_EEPROM_Memory_byte(byte val1, byte val2)
{
uint8_t eepromAddr = val1;
uint8_t eepromVal = val2;
eeprom_memory_update_byte(eepromAddr, eepromVal);
return 1;
}
In eeprom.h
void eeprom_update_byte (uint8_t *__p, uint8_t __value);
In eeprom.c
bool eeprom_memory_update_byte(uint8_t eeprom_addr, uint8_t eepromValue)
{
eeprom_update_byte((uint8_t*) eeprom_addr, eepromValue);
uint8_t eepromVal = eeprom_read_byte(( uint8_t *) eeprom_addr);
if (eepromValue == eepromVal)
return 1;
else
return 0;
}
please help!
|
|
|
|
|
The first parameter in eprom_update_byte() function declaration is different than what is the the implemntation. In the .h file it is a pointer to a uint8_t (uint8_t *__p), and in the implementation it is a copy of the object (uint8_t eeprom_addr) passed by value. I'm guessing, change the implementation line in the .c file. But that might cause you to call the function differently like,
eeprom_memory_update_byte(&eepromAddr, eepromVal);
|
|
|
|
|
You haven't given us the implementation of this prototype function
void eeprom_update_byte (uint8_t *__p, uint8_t __value);
Implicit declaration error usually means you provided a prototype but no body code ... hence I am worried you haven't given me that functions code. I am assuming the EEPROM is flash and that code will do what we call the toggling test until it writes the byte to the flash. Warning if it is FLASH you usually also have to release protection registers by writing special commands to special addresses before you can write to the flash, did the original code also provide a function to release the protection on a sector per chance?
However onto your code as it stands, you are passing in the address to write as a byte which gives you a range of 0-255 in memory see here
bool Update_EEPROM_Memory_byte(byte val1, byte val2) {
uint8_t eepromAddr = val1;
uint8_t eepromVal = val2;
The original function they provided had a pointer to an byte (uint_8) which will be most likely be 32 bit ... see
void eeprom_update_byte (uint8_t *__p, uint8_t __value);
I suspect you need your address to be a long ..... try
bool Update_EEPROM_Memory_byte(unsigned long val1, byte val2){
unsigned long eepromAddr = val1;
uint8_t eepromVal = val2;
Adjusted last function to take the long
bool eeprom_memory_update_byte(unsigned long eeprom_addr, uint8_t eepromValue)
{
eeprom_update_byte((uint8_t*) eeprom_addr, eepromValue);
uint8_t eepromVal = eeprom_read_byte(( uint8_t *) eeprom_addr);
if (eepromValue == eepromVal)
return 1;
else
return 0;
}
The alternative to an unsigned long for the address is to keep it as a pointer (uint8_t*).
That all means nothing if you have no code for the function eeprom_update_byte which isn't shown.
Other housekeeping Update_EEPROM_Memory_byte should return the result of eeprom_memory_update_byte rather than a static 1 (TRUE) result.
In vino veritas
modified 30-Jul-16 0:22am.
|
|
|
|
|
how to create buttons to input txt file and pdf files in microsoft visual c ++ ?
|
|
|
|
|
|
First I would like to start thanks to all on the CodeProject I think I am getting a little better at this (this being MFC)
Well my code works fine Under the VS 2012 debugger, However When I rebuild it in Release mode. I get a message that my program stopped working with the option of invoking the VS debugger, which I do the code points to MFC code Unhandled Exception going back via the Call Stack it points to CString code Which I will gladly post,
Well the Next thing I did seeing the code works fine in Debug mode, was code a CATCH_ALL exception handler just to see if the code with go to the CATCH_ALL block in Which I invoke AfxMessageBox(".... exception handler") and the message was displayed.
I think at this point I have to get a little more specific (as to what type of exception)
So at the point I think I'll post my code The Bold underline code seems be
where the problem is when I go bank via the Call Stack In Debug mode I check the contents
and tempstr is a Valid Null Terminated String
Can someone at least point me to where I might be able find information exception to catch the specific exception that's giving me the problem
Thanks
if(pMsg->message==WM_KEYDOWN)
{
TRY
{
if(pMsg->wParam==VK_RETURN)
{
main_app = (CHERC_CMDApp *)AfxGetApp();
memcpy((void *)main_app->mybaseeventptr->command,(void *)"REL",3);
memcpy((void *)main_app->threadptr[curr_thread]->sockbuffer,(void *)"REL",3);
main_app->threadptr[curr_thread]->num_buff = 3;
CString tempstr = PSW.ia;
tempstr.SetAt(16,0x00);
tempstr.MakeUpper();
if(tempstr == end_address)
{
memcpy((void *)main_app->threadptr[curr_thread]->sockbuffer,(void *)"TERM",4);
main_app->threadptr[curr_thread]->num_buff = 4;
}
::PostThreadMessage(main_app->threadptr[curr_thread]->m_nThreadID,WM_SEND_SOCK_MESS,22,(LPARAM) main_app->mybaseeventptr->command);
::GetCaretPos(&mycursor);
mychar = myedit->CharFromPos(mycursor);
longchar = mychar;
cursorline = myedit->LineFromChar(longchar);
linelen = myedit->LineLength(cursorline);
linelen = 125;
linechar = myedit->LineIndex(cursorline);
myedit->GetLine(cursorline,currline.GetBufferSetLength(linelen +1),linelen);
buffptr = currline.GetBuffer(10);
myeventptr = main_app->mybaseeventptr;
strncpy((char *)myeventptr->command,(char *)&nu_lls[0],5); myeventptr->send_window = this;
myeventptr->SetEvent();
}
}
CATCH_ALL(e)
{
AfxMessageBox("In ProgDebug Exception Routine");
}
END_CATCH_ALL
}
|
|
|
|
|
The big difference for variables between DEBUG mode and RELEASE mode is stack variables aren't zeroed.
The simple statement
void SomeFunc (void){
int i;
}
i is guaranteed to start as zero in DEBUG mode but could be literally anything in RELEASE mode.
In the above if you need the variable to start as zero you need it.
void SomeFunc (void){
int i = 0;
}
Now you most likely have a structure or pointer variable you are assuming is zero but you have not explicitly set it in a local variable. Your code will then always work in DEBUG mode but almost never works in RELEASE mode.
In vino veritas
|
|
|
|
|
How about in release mode I attach the debugger I try to stepping thru the code that's giving me a problem
Thanks
|
|
|
|
|
Also turn your error level to 4 in release mode and look for any warning along the lines possible use of uninitialized variable.
In vino veritas
|
|
|
|
|
MFC throws exceptions derived from the CException class which contain additional information and provide a function to show a message.
So you may add this block of code on front of your CATCH_ALL block:
CATCH(CException, pEx)
{
pEx->ReportError();
pEx->Delete();
}
The operation that might fail in your code is CString::SetAt (when the position is beyond the end of the string). This will throw an exception in release builds and assert with debug builds. Because you are not getting an assertion with a debug build, the only reason for an exception in release builds can be a different (shorter) PSW.ia string. If this is not the case the exception source is probably somewhere else.
To avoid such out of range acesses you should check the length or use a function that handles them like CString::Left.
|
|
|
|
|
How about pEX->GetErrorMessage.....
I think ReportError is just a message box with out any information ?
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
