|
You may give an example of your data. Inspecting the text file may also give a hint what is going wrong.
[EDIT]
I have replaced the usage of "%lf" by "%f" in my post. But this should make no difference with MS compilers.
modified 18-Mar-15 13:09pm.
|
|
|
|
|
Hi Jochen,
I'm getting data like this
18832315686612578000000000000000000000000000000000000000000000000000.00 18832315686612578000000000000000000000000000000000000000000000000000.00 18832315686612578000000000000000000000000000000000000000000000000000.00
18832315686612578000000000000000000000000000000000000000000000000000.00 18832315686612578000000000000000000000000000000000000000000000000000.00 18832315686612578000000000000000000000000000000000000000000000000000.00
It's 2 raws of numbers..3,5 lines are continuation of 1st line..ans so 4,6 ..
It's basically limited to 1kb irrespective of the duration of experiment
|
|
|
|
|
That are quite large numbers. Are they the correct values? If your numbers are in that range, you should use the "%E" format.
|
|
|
|
|
Hi Jochen,
Now it's working perfectly!. I did a a mistake in closing the file. Thank you so much for your prompt and precise feedback!.
|
|
|
|
|
Fine that all is working now and thank you for the feedback.
|
|
|
|
|
Hi Jochen,
The data i'm getting is of very large sample. I use a inbuilt thread class calls at very high frequency. Basically I want to reduce the sampling rate so that I'll get significant data with less samples..Do you have any idea how to create periodic thread with a fixed frequency?
|
|
|
|
|
It is difficult to answer this without knowing how samples are triggered, new data are signaled, and what is done by your thread class.
When sampling is triggered by your app, you can control the frequency. If it is free running you may skip samples (e.g. processing only every second one).
When using a worker thread you usually call a wait function (e.g. WaitForSingleObject) that returns upon events or a time out. The time out value can be used for periodic execution.
|
|
|
|
|
Basically two functions one is for updating graphics and other for haptics rendering. Haptic rendering sampling rate is quite large compared to graphics. In the library I'm using there is a thread class basically gives priority to haptic and graphics rendering. But I'm not able to see any section in the code where they access system timing and setting sampling rate etc.
I'm thinking about assigning some condition inside data will be written into the file at a rate of 100 samples per second. There is an inbuilt precision clock with the library, so if I've I can get cpu time with precision clock , how can formulate a condition to write data at a rate 100Hz??
|
|
|
|
|
As far as I understood you have a haptic device which is some kind of hardware which generates data at a frequency defined by the hardware. If the library does not provide functions to set the sample rate, it is probably fixed. The thread is then activated when new data are available.
But again, without knowing the hardware and the library (which acesses the hardware specific driver), it is rather impossible to answer.
Do you want to write the data to a file with 100 Hz. This is probably too fast (especially when the file must be opened for each write). It again depends on your requirements (who is reading the file). If the data should be read by another process, you may use some kind of IPC (Inter Process Communication).
Regarding timers:
Windows has no high resolution timers. While it is possible to measure times with high resolution (QueryPerformanceCounter), the system timers have a resolution of about 10 ms by default and can be tweaked down to 1 ms.
|
|
|
|
|
Jochen Arndt wrote: the system timers have a resolution of about 10 ms by default and can be tweaked down to 1 ms.
What about the waitable timers? SetWaitableTimer[^]
Quote: pDueTime [in]
The time after which the state of the timer is to be set to signaled, in 100 nanosecond intervals.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Windows uses internally 100 ns based times (FILETIME structure). But this does not mean that the internal timer tick is running with a resolution of 100 ns.
There are undocumented functions to query the range of resolution and set the resolution (NtQueryTimerResolution, NtSetTimerResolution). On a typical system, the range is 0.5 to 15.6 ms.
|
|
|
|
|
How can I configure a periodic thread of particular frequency?
|
|
|
|
|
Just call Sleep() with a time out value of 1000 / frequency[Hz].
A better implememntation would use WaitForSingleObject() with the same time out value and a handle to a terminate thread event so that you can terminate the thread:
UINT worker_thread_func(LPVOID pParam)
{
MyClass *pThis = (MyClass *)pParam;
HANDLE hKillEvent = pThis->m_hKillEvent;
while (1)
{
if (WAIT_OBJECT_0 == WaitForSingleObject(hKillEvent, TIME_OUT_VAL))
break;
}
return 0;
}
|
|
|
|
|
Hi Jochen,
I still didn't get idea of using WaitForSingleObject() as a timer. Basically WaitForSingleObject is a predefined function under windows.h? right?. Can you bit explain how exactly this can be embedded with a project?
|
|
|
|
|
It is a Windows API function that is used with threads. It will suspend the thread until the event specified by the passed handle occurs or the time out time has elapsed.
Using threads is an advanced topic. So you should read about it first. A starting point may be Using Worker Threads[^].
Your requirement was to execute specific tasks in fixed intervals. This can be done by Windows timers from within your main (GUI) thread. But this will block the main thread for the task execution time. With short intervals, this will lead to delayed user input (mouse and keyboard actions are not performed immediately). To avoid this, a worker thread can be used.
|
|
|
|
|
Message Closed
modified 30-Mar-15 8:31am.
|
|
|
|
|
I can't answer this without knowing the library.
That depends on the library, the implementation of that 'clock' and if it can generate some kind of signal.
|
|
|
|
|
Hi Everyone..
I very rarely ask programming-specific questions in public forums, but this one has me completely stumped.
I just can't seem to get the Windows Native API function, "Shell_NotifyIcon" to work, no matter what I try.
This is the Windows API function that enables an application to add its "Icon" to the Windows System Tray, aka: the "System Notification Area", and then enables it to pop up "notifications", etc..
At least, in theory..
No matter what I try however, this function always fails in my app.
And when I call the GetLastError() function to try to determine what was allegedly wrong with the call, sometimes I'll get a "timeout" error (whatever that means), sometimes I'll get an "invalid window handle" (but the handle's perfectly valid), and other times the call will actually succeed, but the very next call will fail with the same variable results..
I'm compiling in Windows 64-bit using Visual C++ Express, BTW..
I've tried calling both the ANSI and Unicode versions of this function and get the same results. I've tried specifying different "versions" to this function (it's a parameter), and I get the same results. I've tried compiling both with and without "enabling Visual Styles", but, you guessed it, same results..
And I've looked at all the sample code on the Internet that uses this function, including most of the code on this site, and without exception, none of the code I've looked at is doing anything more than my own code is doing..
Which is all, needless to say, exceedingly frustrating..
My app also changes its own execution priority, so I took that out to see if it would make a difference - it didn't..
I also came across an excellent article on Shell_NotifyIcon on the Internet:
"The trouble with Shell_NotifyIcon()"]
So I implemented a retry count, as he suggested. Unfortunately, the only difference that made was that I had to wait four seconds before I could see it fail (yet again)..
The methodology involved is this:
my Main Dialog Box's WM_INITDIALOG message handler calls this:
#define TRAY_ICON_ID 0xABC // <== ..our System Tray Icon Id
#define BALL_ICON_ID 0xDEF // <== ..our Balloon Tip Icon Id
#define MSG_FROM_TRAY (WM_APP + 0xDAD) // <== ..the "callback message" ID..
static NOTIFYICONDATA *NID;
static void Init_NID( HWND hDlg )
{
if ( NID = new NOTIFYICONDATA )
{
memset( NID, 0, sizeof( NOTIFYICONDATA ) );
if ( LoadIconMetric( AppInst,
(PCWSTR)MAKEINTRESOURCE( IDR_TrayIcon ),
LIM_SMALL, &NID->hIcon ) == S_OK )
{
if ( LoadIconMetric( AppInst,
(PCWSTR)MAKEINTRESOURCE( IDR_BallIcon ),
LIM_SMALL, &NID->hBalloonIcon ) == S_OK )
{
bool Opning = strcpy( NID->szTip, "My App Name" ) &&
strcpy( NID->szInfoTitle, "Hi There" ) &&
strcpy( NID->szInfo, "My notification message.." );
if ( Opning )
{
NID->uTimeout = 5000;
NID->uID = TRAY_ICON_ID;
NID->dwInfoFlags = NIIF_USER;
NID->uCallbackMessage = MSG_FROM_TRAY;
NID->cbSize = sizeof( NOTIFYICONDATA );
NID->dwState = 0;
NID->dwStateMask = NIS_HIDDEN | NIS_SHAREDICON;
return;
}
DestroyIcon( NID->hBalloonIcon );
}
DestroyIcon( NID->hIcon );
}
delete NID;
NID = NULL;
}
}
The same Dialog Box procedure also calls two other Tray-related functions, Min2SysTray(), which attempts to add the Tray Icon, display a notification, then hide the Dialog Box, and ProcMsgFromTray(), which processes messages from the Tray.
All three are invoked from the same Dialog Box procedure in the following way:
static INT_PTR CALLBACK MainDlg( HWND hDlg, UINT uMsg, WPARAM wParam, LPARAM lParam )
{
switch ( uMsg )
{
case WM_SYSCOMMAND:
switch ( wParam )
{
case SC_CLOSE:
QuitThisApp( hDlg );
return( true );
case IDM_About:
DialogBoxParam( AppInst,
MAKEINTRESOURCE( IDD_About ),
hDlg, AboutDlg, 0 );
return( true );
case SC_MINIMIZE: if ( Min2SysTray( hDlg ) ) return( true );
}
break;
case MSG_FROM_TRAY:
ProcMsgFromTray( hDlg, wParam, lParam );
return( true );
case WM_INITDIALOG:
Init_NID( hDlg );
return( true );
case WM_DESTROY: PostQuitMessage( 0 );
}
return( false );
}
Where the code for my Min2SysTray() function is:
static bool Min2SysTray( HWND hDlg )
{
bool Success = false;
if ( NID )
{
NOTIFYICONDATA Ver;
memset( &Ver, 0, sizeof( NOTIFYICONDATA ) );
Ver.uID = NID->uID;
Ver.uVersion = NOTIFYICON_VERSION_4;
Ver.cbSize = sizeof( NOTIFYICONDATA );
NID->hWnd = Ver.hWnd = hDlg;
NID->uFlags = NIF_ICON | NIF_MESSAGE | NIF_TIP | NIF_SHOWTIP;
if ( Shell_NotifyIcon( NIM_ADD, NID ) && Shell_NotifyIcon( NIM_SETVERSION, &Ver ) )
{
NID->uFlags = NIF_INFO | NIF_MESSAGE | NIF_TIP | NIF_SHOWTIP;
if ( Success = Shell_NotifyIcon( NIM_MODIFY, NID ) )
ShowWindow( hDlg, SW_HIDE );
}
}
return( Success );
}
And the code for my ProcMsgFromTray() function is:
static void ProcMsgFromTray( HWND hDlg, WPARAM wParam, LPARAM lParam )
{
if ( HIWORD( lParam ) == NID->uID )
{
switch ( LOWORD( lParam ) )
{
case NIN_SELECT:
case NIN_KEYSELECT:
case WM_LBUTTONDBLCLK:
if ( NID ) Shell_NotifyIcon( NIM_DELETE, NID );
ShowWindow( hDlg, SW_SHOW );
}
}
}
And that's pretty much all of the code. Needless to say, I haven't been able to figure out what's wrong with it (yet?), if anything..
So what I need is another pair of eyes. Or two, or four.. or a thousand..
Uh! My frustration's bubbling to the surface.. please to excuse..
Anyway, if there's anyone out there who can find anything wrong with the above code, and/or can help in any other way, please respond..
Thanks in advance..
modified 16-Mar-15 23:23pm.
|
|
|
|
|
From code you posted it seems very improbable to me that it can work with memory dynamically allocated (new) for NOTIFYICONDAT. This memory is released when sub exits, while it is not reused may happen that it works, as soon it is reused and filled with data making nosense for IconNotify it will not work anymore.
The problem you mentioned is related only to services and program that starts before desktop (iexplorer) is started (that is the case of utilities wrote by the author of article you mentioned). In that case the solution is to wait for initialization to complete. You will find all info, if you need, here[^].
Making it static and changing the access to its members it works for me.
This is the amended code:
#define MSG_FROM_TRAY (WM_APP + 0xDAD) // <== ..the "callback message" ID..
static BOOL Opning = TRUE;
static NOTIFYICONDATA NID;
static void Init_NID( HWND hDlg )
{
memset( &NID, 0, sizeof( NOTIFYICONDATA ) );
if ( LoadIconMetric( AppInst,
(PCWSTR)MAKEINTRESOURCE( IDR_TrayIcon ),
LIM_SMALL, &NID.hIcon ) == S_OK )
{
if ( LoadIconMetric( AppInst,
(PCWSTR)MAKEINTRESOURCE( IDR_BallIcon ),
LIM_SMALL, &NID.hBalloonIcon ) == S_OK )
{
strcpy( NID.szTip, "My App Name" );
strcpy( NID.szInfoTitle, "Hi There" );
strcpy( NID.szInfo, "My notification message.." );
if ( Opning )
{
NID.uTimeout = 5000;
NID.uID = TRAY_ICON_ID;
NID.dwInfoFlags = NIIF_USER;
NID.uCallbackMessage = MSG_FROM_TRAY;
NID.cbSize = sizeof( NOTIFYICONDATA );
NID.dwState = 0;
NID.dwStateMask = NIS_HIDDEN | NIS_SHAREDICON;
return;
}
DestroyIcon( NID.hBalloonIcon );
}
DestroyIcon( NID.hIcon );
}
}
static BOOL Min2SysTray( HWND hDlg )
{
BOOL Success = FALSE;
NOTIFYICONDATA Ver;
memset( &Ver, 0, sizeof( NOTIFYICONDATA ) );
Ver.uID = NID.uID;
Ver.uVersion = NOTIFYICON_VERSION_4;
Ver.cbSize = sizeof( NOTIFYICONDATA );
NID.hWnd = Ver.hWnd = hDlg;
NID.uFlags = NIF_ICON | NIF_MESSAGE | NIF_TIP | NIF_SHOWTIP;
if ( Shell_NotifyIcon( NIM_ADD, &NID ) && Shell_NotifyIcon( NIM_SETVERSION, &Ver ) )
{
NID.uFlags = NIF_INFO | NIF_MESSAGE | NIF_TIP | NIF_SHOWTIP;
if ( Success = Shell_NotifyIcon( NIM_MODIFY, &NID ) )
ShowWindow( hDlg, SW_HIDE );
}
return( Success );
}
static void ProcMsgFromTray( HWND hDlg, WPARAM wParam, LPARAM lParam )
{
if ( HIWORD( lParam ) == NID.uID )
{
switch ( LOWORD( lParam ) )
{
case NIN_SELECT:
case NIN_KEYSELECT:
case WM_LBUTTONDBLCLK:
Shell_NotifyIcon( NIM_DELETE, &NID );
ShowWindow( hDlg, SW_SHOW );
}
}
}
modified 16-Mar-15 19:13pm.
|
|
|
|
|
Apologies. I made a mistake in transcribing the original code.
Which actually has nothing to do with why this code still doesn't work - just to be clear.
In the original code, the NID->szTip, NID->szInfoTitle, and NID->szInfo structure members are not initialized by strcpy(). I changed it to a bunch of strcpy() calls to "simplify" the code (to make it easier to read)..
They are initialized in the original code by a function call whose return value sets an auto bool called, "Opning". When I substituted out that function call for those strcpy() calls (for simplicity), I also (erroneously) took out the "bool Opning =" part.
My bad.
To make a long story short, the following is a far more correct "transcription" of the existing code:
#define TRAY_ICON_ID 0xABC // <== ..our System Tray Icon Id
#define BALL_ICON_ID 0xDEF // <== ..our Balloon Tip Icon Id
#define MSG_FROM_TRAY (WM_APP + 0xDAD) // <== ..the "callback message" ID..
static NOTIFYICONDATA *NID;
static void Init_NID( HWND hDlg )
{
if ( NID = new NOTIFYICONDATA )
{
memset( NID, 0, sizeof( NOTIFYICONDATA ) );
if ( LoadIconMetric( AppInst,
(PCWSTR)MAKEINTRESOURCE( IDR_TrayIcon ),
LIM_SMALL, &NID->hIcon ) == S_OK )
{
if ( LoadIconMetric( AppInst,
(PCWSTR)MAKEINTRESOURCE( IDR_BallIcon ),
LIM_SMALL, &NID->hBalloonIcon ) == S_OK )
{
bool Opning;
if ( Opning = LoadStrings( NID->szTip,
NID->szInfo,
NID->szInfoTitle ) )
{
NID->uTimeout = 5000;
NID->uID = TRAY_ICON_ID;
NID->dwInfoFlags = NIIF_USER;
NID->uCallbackMessage = MSG_FROM_TRAY;
NID->cbSize = sizeof( NOTIFYICONDATA );
NID->dwState = 0;
NID->dwStateMask = NIS_HIDDEN | NIS_SHAREDICON;
return; }
DestroyIcon( NID->hBalloonIcon );
}
DestroyIcon( NID->hIcon );
}
delete NID;
NID = NULL;
}
}
Again, sorry for that oversight.
However, as is readily apparent from the above code, it is incorrect to say that the "memory is released when sub exits". The memory is only released if the function fails to initialize the entire structure.
Thing is though, even if the function does fail (which BTW, I've never seen it do, and I've debugged this a lot), then the NID variable would get set to NULL, which would prevent the Shell_NotifyIcon() function from ever getting called (because the function that calls it checks the NID before it does anything else).
And to forestall the inevitable question, yes, I am sure that my "LoadString()" function is not overwriting any other structure members (with strings too big)..
Anyway, the structure always initializes fine, so I don't think that's the problem.
I am curious though, about what you meant when you said that it "works for me"? Are you compiling in 64-bit?
|
|
|
|
|
I see, I have misinterpreted the usage of new in your code.
What I mean is that I compiled a sample with a C (not C++) compiler and it works for me.
The only problem I found compiling the code in 64bits is that a manifest resource is required.
This is my full sample:
#define WIN32_LEAN_AND_MEAN
#include <windows.h>
#include <windowsx.h>
#include <commctrl.h>
#include <tchar.h>
#include <shellapi.h>
#include <stdio.h>
#include <stdlib.h>
#include "main.h"
#define NELEMS(a) (sizeof(a) / sizeof((a)[0]))
static INT_PTR CALLBACK MainDlgProc(HWND, UINT, WPARAM, LPARAM);
#define AppInst ghInstance
static HANDLE ghInstance;
#define TRAY_ICON_ID 0xABC // <== ..our System Tray Icon Id
#define BALL_ICON_ID 0xDEF // <== ..our Balloon Tip Icon Id
#define MSG_FROM_TRAY (WM_APP + 0xDAD) // <== ..the "callback message" ID..
static BOOL Opning = TRUE;
static NOTIFYICONDATA NID;
static void Init_NID( HWND hDlg )
{
memset( &NID, 0, sizeof( NOTIFYICONDATA ) );
if ( LoadIconMetric( AppInst,
(PCWSTR)MAKEINTRESOURCE( IDR_TrayIcon ),
LIM_SMALL, &NID.hIcon ) == S_OK )
{
if ( LoadIconMetric( AppInst,
(PCWSTR)MAKEINTRESOURCE( IDR_BallIcon ),
LIM_SMALL, &NID.hBalloonIcon ) == S_OK )
{
strcpy( NID.szTip, "My App Name" );
strcpy( NID.szInfoTitle, "Hi There" );
strcpy( NID.szInfo, "My notification message.." );
if ( Opning )
{
NID.uTimeout = 5000;
NID.uID = TRAY_ICON_ID;
NID.dwInfoFlags = NIIF_USER;
NID.uCallbackMessage = MSG_FROM_TRAY;
NID.cbSize = sizeof( NOTIFYICONDATA );
NID.dwState = 0;
NID.dwStateMask = NIS_HIDDEN | NIS_SHAREDICON;
return;
}
DestroyIcon( NID.hBalloonIcon );
}
DestroyIcon( NID.hIcon );
}
}
static BOOL Min2SysTray( HWND hDlg )
{
BOOL Success = FALSE;
NOTIFYICONDATA Ver;
memset( &Ver, 0, sizeof( NOTIFYICONDATA ) );
Ver.uID = NID.uID;
Ver.uVersion = NOTIFYICON_VERSION_4;
Ver.cbSize = sizeof( NOTIFYICONDATA );
NID.hWnd = Ver.hWnd = hDlg;
NID.uFlags = NIF_ICON | NIF_MESSAGE | NIF_TIP | NIF_SHOWTIP;
if ( Shell_NotifyIcon( NIM_ADD, &NID ) && Shell_NotifyIcon( NIM_SETVERSION, &Ver ) )
{
NID.uFlags = NIF_INFO | NIF_MESSAGE | NIF_TIP | NIF_SHOWTIP;
if ( Success = Shell_NotifyIcon( NIM_MODIFY, &NID ) )
ShowWindow( hDlg, SW_HIDE );
}
return( Success );
}
static void ProcMsgFromTray( HWND hDlg, WPARAM wParam, LPARAM lParam )
{
if ( HIWORD( lParam ) == NID.uID )
{
switch ( LOWORD( lParam ) )
{
case NIN_SELECT:
case NIN_KEYSELECT:
case WM_LBUTTONDBLCLK:
Shell_NotifyIcon( NIM_DELETE, &NID );
ShowWindow( hDlg, SW_SHOW );
}
}
}
int PASCAL WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpszCmdLine, int nCmdShow)
{
INITCOMMONCONTROLSEX icc;
WNDCLASSEX wcx;
ghInstance = hInstance;
icc.dwSize = sizeof(icc);
icc.dwICC = ICC_WIN95_CLASSES ;
InitCommonControlsEx(&icc);
wcx.cbSize = sizeof(wcx);
if (!GetClassInfoEx(NULL, MAKEINTRESOURCE(32770), &wcx))
return 0;
wcx.hInstance = hInstance;
wcx.hIcon = LoadIcon(hInstance, MAKEINTRESOURCE(IDR_ICO_MAIN));
wcx.lpszClassName = _T("TacitoniClass");
if (!RegisterClassEx(&wcx))
return 0;
return DialogBox(hInstance, MAKEINTRESOURCE(DLG_MAIN), NULL, (DLGPROC)MainDlgProc);
}
static INT_PTR CALLBACK MainDlgProc(HWND hwndDlg, UINT uMsg, WPARAM wParam, LPARAM lParam)
{
switch (uMsg)
{
case WM_INITDIALOG:
Init_NID( hwndDlg );
return TRUE;
case WM_SIZE:
return TRUE;
case WM_COMMAND:
switch (GET_WM_COMMAND_ID(wParam, lParam))
{
case IDOK:
EndDialog(hwndDlg, TRUE);
return TRUE;
}
break;
case WM_SYSCOMMAND:
switch ( wParam )
{
case SC_CLOSE:
PostQuitMessage(0);
return TRUE;
case SC_MINIMIZE:
if ( Min2SysTray( hwndDlg ) )
return TRUE;
}
break;
case MSG_FROM_TRAY:
ProcMsgFromTray(hwndDlg, wParam, lParam);
break;
case WM_CLOSE:
EndDialog(hwndDlg, 0);
return TRUE;
}
return FALSE;
}
modified 17-Mar-15 4:53am.
|
|
|
|
|
Thanks very much Frankie-C, that information is (I hope) fairly indicative of what I've been suspecting (actually dreading) about this whole fiasco since shortly after it began..
And that is that I don't think the 64-bit Shell_NotifyIcon() works.. like, at all..
That's the only logical explanation that I can think of for what I'm seeing (and what you're saying)..
So this is good; this is progress..
Fortunately, the manifest resource issue that you mentioned is easily rectified. Just add the following #pragma in your StdAfx.h:
#pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' "\
"version='6.0.0.0' processorArchitecture='*' publicKeyToken='6595b64144ccf1df' language='*'\"")
Then set the following option in your Project Property Page:
Linker ==> Manifest File ==> Generate Manifest ==> Yes (/MANIFEST)
and voila! No need to create a manifest resource.. Assuming, of course, that you're using some reasonably recent version of Microsoft Visual Studio..
Of course, as you may have already surmised, I'm telling you this in the hope that you'll try compiling your code in 64-bit, and apprise me of the results that you get..
If my suspicions are correct, your code, like mine, won't work in 64-bit..
If I'm wrong about that, then that would be almost as good (actually better in the long term). Then I'll just take your code verbatim, and start adding in bits of my other stuff until it fails. In my experience, bugs are rooted out far more easily when you're adding to code that works, as opposed to attempting to subtract from code that doesn't..
But I kinda need to know that the 64-bit Shell_NotifyIcon() works for someone, *anyone*, before I go down that (very long) road.. Because at this point, I don't think it will..
Anyway, thanks again for your help. I see that you're still insisting on a static NID as opposed to a static NID pointer.. Well, six of one, half dozen the other - you know. The reason I made it a pointer (and yes, in my own code, it's still a pointer) is because the whole System Tray thing is an End-User option, so why allocate memory that might never be used? And because making it a pointer allows it to double as a kind of boolean - if it's not NULL, it means that all steps of the initialization succeeded, and if it is NULL, then don't use it at all.. Kind of an all-or-nothing approach..
And last and least, I think we both know that that silly "Opning" variable doesn't need to be in either your code or mine. To be sure, it still serves a purpose in my original code, but I left it in here (this forum) only out of respect for the narrative - it is completely superfluous..
Anyway, I'm being far too verbose - it's late; too much coffee.. Need to..
|
|
|
|
|
Thanks Tacitonitus,
BTW my code is 64 bits, and I assure you that it works. I didn't use VC, but PellesC compiler.
You can get the working project (with even the executable) here[^] if you need.
Just to give more detail, my manifest contains:
="1.0"="UTF-8"="yes"
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
type="win32"
name="MyOrganization.MyDivision.MyApp"
version="1.0.0.0"
processorArchitecture="amd64"
/>
<description>Verbal description of MyApp.</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="amd64"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
<application>
<supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
<supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
<supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
</application>
</compatibility>
</assembly>
This is important because if I compile without it the loader complains about a missing ordinal in commctl32:
The ordinal 380 could not be located in the dynamic link library COMCTL32.dll.
|
|
|
|
|
Yes, I got exactly that same error message when I tried to "disable Visual Styles", to see if it would make a difference..
So it looks like I've got to take that "very long" road I mentioned..
Well, like I said, in the long term, that's probably a good thing (I'm trying to stay positive)..
So let me ask you: what size Icons are you passing in to the LoadIconMetric() function(s)?
I'm passing in 32x32 pixel Icons, and trusting that the LoadIconMetric() function will either squash it down to the appropriate size, or return an error code if it can't. However, I can no longer trust even the most obvious of assumptions any more, which is why I'm asking..
Also, I can't download your project because you have to be a member of whatever to do so.. But that doesn't matter much - I'm.. uh.. somewhat familiar with the code.. 
This is maddening - according to you, the code works fine - it just doesn't work for me.. 'cause I'm.. special.. or cursed.. or something.. 
Well, whatever. Ignore the previous paragraph. I guess I'll just have to keep slogging it out..
Cheers..
|
|
|
|
|
Icon is 32x32 256 colors.
To download the sample you have just register is not a big issue.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
