|
Looks like std::unique_ptr is not defined in VS2008. I got it working using standard form like
ThreadNetMsgParamStruct *pThreadParams = (ThreadNetMsgParamStruct *)pParam;
But the problem is, a CDocument class can not process windows messages. Is there any other straight forward way to replicate UpdateAllViews() command without calling it directly?
thanks
PKNT
|
|
|
|
|
unique_ptr is like std::auto_ptr (its younger brother in stl). It deletes the pointer automatically when it goes out of scope (in this case at the end of the function or if you return from the func). The struct instance must be deleted otherwise you cause a memory leak. You have to send a message to a window and not to a document object. If you can't solve the problem using the info I provided (theory + 90% of the code needed) then either ask a colleague to do it for you or start learning about multithreading+gui and their relationship.
|
|
|
|
|
Kiran Satish wrote:
I am trying to call a GUI function from a worker thread...
Bad idea. See here for why.
"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
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
Just dont do it. Think of your thread as being in a different process, how would you communicate between them? With PostMessage and SendMessage. So create some custom IDs, handle them in your main window proc and post or send using those IDs from the thread.
You have to keep it clean on Windows, you cant bodge stuff. It might work for a bit, but eventually it will break.
|
|
|
|
|
Thanks, that's exactly how I did it over the weekend and it works well.
PKNT
|
|
|
|
|
Hi there,
Is there a way to disallow users from pasting anything to CEdit box control?
Right now they can right click and select the PASTE menu option.
And also do a Control + V.
How to disable this?
please give some sample code.
Thanks in advance.
|
|
|
|
|
|
Oh, but he said "Please give me some code". Are you sure he can handle a link? It might involve thinking....
|
|
|
|
|
Erudite_Eric wrote: might involve thinking
If 99% of the people asking questions here actually put forth any effort in thinking, then 99% of the questions would disappear.... 
|
|
|
|
|
Here you go:
<pre> if (add_uevent_var(env,
"MODALIAS=usb:"
"v%04Xp%04Xd%04Xdc%02Xdsc%02Xdp%02Xic%02Xisc%02Xip%02X",
le16_to_cpu(copy_dev->descriptor.idVendor),
le16_to_cpu(copy_dev->descriptor.idProduct),
le16_to_cpu(copy_dev->descriptor.bcdDevice),
copy_dev->descriptor.bDeviceClass,
copy_dev->descriptor.bDeviceSubClass,
copy_dev->descriptor.bDeviceProtocol,
alt->desc.bInterfaceClass,
alt->desc.bInterfaceSubClass,
alt->desc.bInterfaceProtocol))
return -ENOMEM;
modified 18-Jul-13 9:11am.
|
|
|
|
|
Hi,
I'm using wofstream to write text to a file
my problem is that, with any level of optimization, neither write() or << allows me to write a wstring or c string in the form of (WCHAR*).
example
WCHAR* str = new WCHAR[MAX_PATH];
wcscpy(str, L"walk");
myfile.write(str, wcslen(str));
No string written to file
wstring str2 = L"walk";
myfile << str2;
No string written to file
I am able to to do
myfile << "String";
how do I fix?
|
|
|
|
|
Unfortunately you don't. The wstream types take wide characters in but write them out as normal ASCII. You should use the old C-style fwrite or the newer WriteFile functions which allow you to specify the output character size.
Use the best guess
|
|
|
|
|
so wofstream can't be optimized? it all works well without optimization
|
|
|
|
|
doug25 wrote: so wofstream can't be optimized? it all works well without optimization
Sorry, I don't understand what you are saying here. As far as Irecall from all the tests I have run, you cannot write wide characters via a wstream. I would be interested to see the code you have that does work. In the meantime I will retry my own tests.
Use the best guess
|
|
|
|
|
sorry, I've discovered what was happening, it isn't a problem with wstring optimazation. I was converting the file to another format the functions i'm using behave differently with optimization.
The problem is nothing to do with vectors or wstrings. it's a directx set of functions i'm using that fail when optimazation is turned on. It was difficult to determine tat this was where the program was failing.
modified 17-Jul-13 12:17pm.
|
|
|
|
|
doug25 wrote: the functions i'm using behave differently with optimization.
I find that very difficult to believe. Much more likely is that you have a bug somewhere that only shows when you have optimization turned on.
Use the best guess
|
|
|
|
|
well, it could be a mistake I've made but I've managed to find exactly where the error occurs by using #pragma optimize("g", off)
and
#pragma optimize("g", on)
it's one function, I can't see any mistakes
#pragma optimize("g", off)
void AddDataObject(ID3DXFileSaveObject* xFileSave, ID3DXFileData* child, ID3DXFileSaveData* xSaveData)
{
SIZE_T nChildren = 0;
child->GetChildren(&nChildren);
GUID templateid, id;
child->GetType(&templateid);
child->GetId(&id);
char name[MAX_PATH];
SIZE_T sz;
child->GetName(name, &sz);
SIZE_T dataSize;
void* data = NULL;
child->Lock(&dataSize, (LPCVOID*)&data);
if(xSaveData)
{
xSaveData->AddDataObject(templateid, name, (const GUID*)&id, dataSize, data, &xSaveData);
}
else
{
xFileSave->AddDataObject(templateid, name, (const GUID*)&id, dataSize, data, &xSaveData);
}
child->Unlock();
for(int i=0; i<nChildren; i++)
{
ID3DXFileData* ch = NULL;
if(SUCCEEDED(child->GetChild(i, &ch)))
{
AddDataObject(xFileSave, ch, xSaveData);
}
}
}
#pragma optimize("g", on)
|
|
|
|
|
What problem and where does it occur?
Use the best guess
|
|
|
|
|
the problem is some strings are not loaded, or at least are not written to the new file. e.g. each line in the output file that should contain "Frame frame_name {" (works without opt.) reads "Frame {".
I will try freeing the memory of child data objects although I have assumed they get released when the top level data object get released and I will try what Jochan suggested.
There is very little documentation on how to use these functions.
I won't be able to reply for a while if I do fix the problem but cheers.
|
|
|
|
|
doug25 wrote: the problem is some strings are not loaded, or at least are not written to the new file. e.g. each line in the output file that should contain "Frame frame_name {" (works without opt.) reads "Frame {".
Now I'm totally lost; the code you posted does not seem to have anything at all to do with these comments. It may be better to close off this thread and start a new question when you are ready to proceed.
Use the best guess
|
|
|
|
|
I haven't explained it very well. Basically, I've written a program that writes a .x file using wofstream. But the file doesn't look very pretty so I'm using the directx code I posted to convert it to a better format, so I can also save it as binary or compressed as well as structured text. Basically saves me having to rewrite the program.
I'll close the thread.
|
|
|
|
|
|
You can just stop posting, or edit your original question and add "[closed]" or "[solved]" to the title, and a comment to the effect that you have closed it.
Use the best guess
|
|
|
|
|
That is a recursive function. You may generate assembler output to see the differences between the optimized and unoptimized code.
You should also check for success on all functions that may fail. At least the AddDataObject() return values should be checked and returned upon errors to leave the recursion if something wrent wrong.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
