|
i have a ListView with Report style, an imageList is attached to it. I want to avoid image for a single item in the row. I tried to insert the item with out specifying LVIF_IMAGE flag, when i do so the item displays the first image in the image list.
Thanks & Regards
|
|
|
|
|
nitin3 wrote: tried to insert the item with out specifying LVIF_IMAGE flag, when i do so the item displays the first image in the image list.
Instead, specify the LVIF_IMAGE flag and set the value of iImage as -1;
|
|
|
|
|
i allready tried by setting iImage as -1, it displays the same image at index 0.
Is this a known issue or a problem in my code ?
Thanks & Regards
|
|
|
|
|
nitin3 wrote: i allready tried by setting iImage as -1, it displays the same image at index 0.
I hope you have set the LVIF_IMAGE flag to also.
nitin3 wrote: Is this a known issue or a problem in my code ?
Possibly. Can you show the code?
|
|
|
|
|
Use default image (a white image)
If images than all.
Greetings from Germany
|
|
|
|
|
IMO, iIt would be probably shown as a blank space then, just before the text.
Somethings seem HARD to do, until we know how to do them.
_AnShUmAn_
|
|
|
|
|
If we didn't set the image but set an image list, then also it will show a blank space.
|
|
|
|
|
Hi,,,,
I have one GUI i.e,SDI application which is inherited from Form view
I want to add Key maaping to that GUI.
For that when i press 'a' i have to focus on One button
when i am press 'A' then i have to focus on another button.
//There is a problem in KEYDOWN MessageMap related to my application.
So,I use PreTranslate message to handle key events.but when i press 'a'it will treat that as 'A'.
so,please help me in this Regard.
|
|
|
|
|
I think if u handle WM_CHAR instead of WM_KEYDOWN, you can identify 'a' and 'A'.
|
|
|
|
|
Thanks for the Reply...
But i have some problem when using WM_CHAR and WM_KEYDOWN message maps.
So,Can i Handle it in "PreTranslateMessage"..
any suggestions.......
|
|
|
|
|
|
You may use GetKeyState(VK_SHIFT) [^] to distinguish between lower case and upper case keys in PreTranslateMessage .
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
CPallini wrote: You may use GetKeyState(VK_SHIFT) [^] to distinguish between lower case and upper case
And when caps Lock Key is on?
|
|
|
|
|
Make a try before arguing
(i.e. CAPS LOCK key down makes GetKeyState(VK_SHIFT) returning the same value it returns whenever SHIFT key is held down)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
CPallini wrote: Make a try before arguing
But I tried now. GetKeyState(VK_SHIFT) is not giving the same value when shift key is down and when CAPS LOCK key is on.
Did you actually check like this..?
if( GetKeyState(VK_SHIFT)&0x8000 )
|
|
|
|
|
Well, actually it is not the same value, but bit 0 contains the meaningful info in both cases, hence GetKeyState(VK_SHIFT) & 0x0001 should do the trick.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
CPallini wrote: hence GetKeyState(VK_SHIFT) & 0x0001 should do the trick.
I dont think so. Cause the low bit indicates the key is toggled. Suppose the application is started and at that state
if( GetKeyState(VK_SHIFT) & 0x0001) - > will return false.
Then I press shift key and release it. After that
if( GetKeyState(VK_SHIFT) & 0x0001) - > will return true.
Then if i again press shift and release,
if( GetKeyState(VK_SHIFT) & 0x0001) - > will return false.
So basically, checking the 0 bit have no meaning in the case of shift key. 0th have use only in the case of toggle keys such as CAPS LOCK, NUM LOCK etc...
|
|
|
|
|
Again, make a test.
(I did).
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Thanks...
GetKeyState() works fine....
Regards
varma
|
|
|
|
|
phanindra varma wrote: Thanks...
You're welcome.
phanindra varma wrote: GetKeyState() works fine....
Sure.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Hi,
I used following codes to Open window when double click to the Systray Icon.
No error detected when i compiled the codes. However, the codes does not working...
Any other alternate way to Open window when double click to the Systray Icon???
PLease help me???/
LRESULT CMainFrame::WindowProc(UINT message, WPARAM wParam, LPARAM lParam)
{
// Open window when double click to the Systray Icon
if(message == MYWM_NOTIFYICON){
switch (lParam){
case WM_LBUTTONDBLCLK:
switch (wParam) {
case IDR_TRAYICON:
ShowWindow(SW_NORMAL);
SetForegroundWindow();
SetFocus();
return TRUE;
break;
}
break;
}
}
return CFrameWnd::WindowProc(message, wParam, lParam);
}
regards
usha.
|
|
|
|
|
cb02061 wrote: switch (wParam) {
case IDR_TRAYICON:
Whats is this IDR_TRAYICON?I think that case is unnecessary. Remove it and try..
modified on Thursday, June 26, 2008 10:41 PM
|
|
|
|
|
Hi Naveen,
Not working also??
|
|
|
|
|
Show how you added the tray icon and the entry in the message map.
|
|
|
|
|
cb02061 wrote: No error detected when i compiled the codes.
You don't say whether you've debugged your code. Compiling cleanly is MILES away from actually doing what you've asked it to do.
Try doing:
LRESULT CMainFrame::WindowProc(UINT message, WPARAM wParam, LPARAM lParam)
{
if(message == MYWM_NOTIFYICON
{
ASSERT(FALSE);
switch (lParam){
Then see if
(a) message MYWM_NOTIFYICON ever arrives - if not, look at how you set up your little icon.
(b) do you then get the dblclk message?
(c) and does wParam equal your code?
The show-my-window code looks fine to me (no guarantee though!), so I'd concentrate on the wiring to detect double clicks.
Lastly, use the pre tag as described in the "read this before posting" message. The rules there are good ones. Without formatting, your code is hard to read. And you're just lucky you don;t use any <s or >s.
Iain.
Plz sir... CPallini CPallini abuz drugz, plz plz help urgent.
|
|
|
|