|
For localization purposes, I've been using the gettext library in my MSVC-compiled application (x86) using these instructions from the GNU site (https://www.gnu.org/software/gettext/FAQ.html#windows_woe32). It works fine.
Is there a 64 bit version of gettext for windows? - the one listed on the GNU site is 32bit.
modified 23-May-14 22:47pm.
|
|
|
|
|
A number of suggestions here[^].
|
|
|
|
|
Is it possible (how?)put CDocktablePane into CFormView or dockCMDIChildWndEx like CDocktablePane? (Visual Studio 2010)
I've found following instruction, but I'm not able to use it
http://www.johnbyrd.org/blog/index.php?catid=2&blogid=1
I don't understand for example this text
At this point, you should search through your old CView class to find any references to a COleDropTarget. These references should be changed to refer to the m_OleDropTarget member that you put within the CYourDockablePane class.
I believe that somebody smarter tham me will be able to help me
thank you in advance
|
|
|
|
|
Or you could just ask the person who wrote the blog.
|
|
|
|
|
How?
do you know him?
do you have any cotact to him?
could you share it with me?
modified 23-May-14 15:44pm.
|
|
|
|
|
What? You posted a link to his blog in your original question.
|
|
|
|
|
Yes I did.
Can you imagine that I couldn't found any contact information to him?
yes you're right I'm lazy but without exaggeration
|
|
|
|
|
Did you try the link at the bottom of the page that says "Comments"?
|
|
|
|
|
|
Hi All,
my objective is to create a .MD5 file using Rehash.exe which will be called by CreatedProcess().
if i run from command line its working fine
C:\temp>rehash.exe -none -md5 "C:\temp\aaa.TFI" > "C:\temp\aaa.MD5"
but if i implement in code and use CreateProcess, its not working
below is the code snippet
int main()
{
STARTUPINFO si;
PROCESS_INFORMATION pi;
ZeroMemory( &si, sizeof(si) );
si.cb = sizeof(si);
ZeroMemory( &pi, sizeof(pi) );
LPSTR lp_rehashEXE = "C:\\temp\\rehash.exe";
LPSTR lp_Parameter = " -none -md5 C:\\temp\\Praveer.TFI > C:\\temp\\Praveer.MD5";
if(!::CreateProcess(lp_rehashEXE, lp_Parameter, NULL, NULL, false, 0, NULL, NULL, &si, &pi))
{
printf( "CreateProcess failed (%d)\n", GetLastError() );
return false;
}
// Wait until child process exits.
::WaitForSingleObject(pi.hProcess, INFINITE );
// Close process handles.
CloseHandle( pi.hProcess );
return 0;
}
Please help!!!
|
|
|
|
|
"is not working" is a poor report. Could you please tell use more? Moreover, in the two different tests (namely command line and CreateProcess call) why don't you give exactly the same arguments to Rehash ?
Veni, vidi, vici.
|
|
|
|
|
Look at the documentation of CreateProcess[^]
Now look carefully at the difference between the first and second parameter types - LPCTSTR and LPTSTR respectively.
The first is a constant string and the second is not a constant.
In your code, you're using a pointer to a read-only memory location, which is like a constant string.
Here is an excerpt from the documentation -
The Unicode version of this function, CreateProcessW, can modify the contents of this string. Therefore, this parameter cannot be a pointer to read-only memory (such as a const variable or a literal string).
«_Superman_»
I love work. It gives me something to do between weekends.
Microsoft MVP (Visual C++) (October 2009 - September 2013) Polymorphism in C
|
|
|
|
|
It works, you just dont have rehash.exe in C.\temp
I compiled your code and it and it worked.
Output:
Line, Character counting Program === <EXER3> === by Newbie
Usage: fileName
EXE Path:
Press any key to continue
|
|
|
|
|
One parent dialog is containing 2 child dialog but one at a time.
I need to resize one and not to resize other.
How can I do?
|
|
|
|
|
What's wrong in calling SetWindowPos[^] just for the right child?
Veni, vidi, vici.
|
|
|
|
|
You need to do it manually.
Get the parent dialog client size (CWnd::GetClientRect) and use either CWnd::MoveWindow or CWnd::SetWindowPos to move/resize the child dialog of your choice.
be careful about the CRect that is returned by GetClientRect, you might have to use ScreenToClient to ClientToScreen to convert the rect before move/resize the child dialogs.
I'd rather be phishing!
|
|
|
|
|
Windows 7, Visual Studio 2012, C++
The Microsoft Web page discussing "Quote: Socket overlapped I/O versus blocking/nonblocking mode found here:
http://support.microsoft.com/kb/181611[^]
states:
Quote: To create a socket with the overlapped I/O attribute, you can either use the socket API or the WSASocket API with the WSA_FLAG_OVERLAPPED flag set.
(I added the bolds in the above quote.) What is the difference between socketAPI and WSASocket API?
Please show a code fragment that creates a socket with socket API and another that creates it with WSASocket API.
Thank you for your time
If you work with telemetry, please check this bulletin board: www.irigbb.com
|
|
|
|
|
The functions such as socket [^] are the old style socketAPI group, based on BSD sockets from the early days of UNIX. The WSAxxx functions are the later Microsoft adaptation.
|
|
|
|
|
Is there a difference in speed?
Edit: My email shows another response that says
Quote: The main difference is that socket is a function in the C runtime, and WSASocket is a Windows API.
That response does not show up when I log in here. So can I presume that the WSAxxx versions are faster since they bypass the C runtime, which are, presumably, wrappers that then call the API internally?
Thank you for your time
If you work with telemetry, please check this bulletin board: www.irigbb.com
|
|
|
|
|
bkelly13 wrote: can I presume that the WSAxxx versions are faster since they bypass the C runtime No, you cannot presume anything. It is quite possible (but I don't know) that WSA is built on top of sockets rather than being a complete re-implementation.
|
|
|
|
|
That response was from me. I deleted it because it was wrong. The socket function is not in the C runtime. I'm sorry to have misled you.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Hi bkelly13 !
The "WSASocket API" are Microsoft-specific new functions for handling sockets in Windows.
If your code is to run on Windows machines only go with this new API since it provides more flexibility and some functionality benefits when working with types of sockets other than blocking.
Here are some qoutes from the Remarks paragraph in the MSDN regarding WSARecv :
Quote: The WSARecv function provides some additional features compared with the standard recv function in three important areas:
•It can be used in conjunction with overlapped sockets to perform overlapped recv operations.
•It allows multiple receive buffers to be specified making it applicable to the scatter/gather type of I/O.
•The lpFlags parameter is used both on input and returned on output, allowing applications to sense the output state of the MSG_PARTIAL flag bit. However, the MSG_PARTIAL flag bit is not supported by all protocols.
Same goes for WSASend :
Quote: The WSASend function provides functionality over and above the standard send function in two important areas:
•It can be used in conjunction with overlapped sockets to perform overlapped send operations.
•It allows multiple send buffers to be specified making it applicable to the scatter/gather type of I/O.
You can also find code examples for working with these API in there.
I have created and worked with sockets using this API (Blocking mode and event-based Overlapped mode) and overall it seems to work fine. If relevant, I can send you the code.
Bye,
Amit C.
|
|
|
|
|
I understand and am going with the WSA series. I am putting significant effort into this project. If you have code you don't mind sending, I will look at it. I am declaring my code as open source and will post it. Please send to user name "online" with that symbol followed by my domain bkelly then further followed by dot "ws", yes, its just that simple.
Thank you for the time you spent on your reply.
Thank you for your time
If you work with telemetry, please check this bulletin board: www.irigbb.com
|
|
|
|
|
I am drawing (ownerdraw) a button. I used
if ( (state & ODS_SELECTED) || (state & ODS_FOCUS ))
{
}
to check selected state. Problem is this....If I call BN_CLICKED from parent window then control does not come into above condition but if I click button its working fine.
Please suggest how to set state to ODS_SELECTED?
|
|
|
|
|
The BN_CLICKED message is send to the parent window of a button when it is clicked. It is send by the button control, not to it.
If you want to simulate a button click, send the BM_CLICK[^] message to the button control.
|
|
|
|