|
i think another way :by set mouse right key hook
HWND hWnd=::FindWindow(.....)
if(hWnd)
Hook MouseRKeyHook=SetWindowsHookEX(
WH_MOUSE,
(HookPRoc) mouseRKeyProc,
.....
)
LRESULT CALLBACK MouseRKeyProc(....)
{
when(lparam==“MK_RBUTTON")
//add you want functionality
...}
|
|
|
|
|
Hello,
I have never attempted to map drives using code, can someone point me in the right direction (what functions or pieces do I need to research). I want to be able to map drives to NT shares that require NT authentication. When I say map drives I want to be able to assign a drive letter to a share and or just connect directly and access the files.
Any help would be greatly appreciated!
Thank you,
Rob
Whoever said nothing's impossible never tried slamming a revolving door!
|
|
|
|
|
IIRC you use NetUseAdd()
Ant.
|
|
|
|
|
If you want to do the share beforehand use NetShareAdd() 
Ant.
|
|
|
|
|
Has anyone used USB? Is this similar to RS232 serial transfer? How do you enumerate the ports?
|
|
|
|
|
Short answer: No, it is not similar.
Longer answer: the Universal Serial Bus has basically very little to do with 'serial transfer', despite it's name. There is no concept of ports: the USB is a hub-based network of devices, much like the Ethernet of today.
Programming the USB is just as difficult: in order to send data from a computer to a device, the device must implement an USB endpoint. Usually this is achieved through a USB-compatible electronics chip. Using this chip requires a driver that the operating system loads in order to communicate with the device. You can then ask the OS to enumerate through available endpoints, open a serial connection to an endpoint and send/receive data. The OS will then worry about correctly delivering the data to the recipent connected to the bus.
Naturally, you could re-write the USB base device driver so that it would work as a serial-only device. In such a case, you could manually enumerate the ports, but you'd also lose all the benefits of the USB specification. In english, you'd be using the USB in a way it was not designed to be used. All other USB devices on the system would fail to function with the serial-only USB device. I believe such drivers are available for testing purposes, however.
For more information on how the USB works, I recommend visiting this page
I also recommend the 'USB Complete' book by Jan Axelson, ISBN# 0-9650819-5-8.
For some nice, detailed USB-programming information, visit this page.
-Antti Keskinen
----------------------------------------------
The definition of impossible is strictly dependant
on what we think is possible.
|
|
|
|
|
Thanks for the information. There seems to be a scarcity information out there on USB on the web on this subject, but maybe I was expecting it to be much simpler than it is.
-----------------------------
All truth passes through 3 stages.
First, it is ridiculed.
Second, it is violently opposed.
Third, it is accepted as being self-evident.
|
|
|
|
|
I am trying to get into view the last bit of text posted to the multiline Edit Box with a vertical scroll enabled via these lines of code:-
m_strOutput+= m_strGeneral + crlf; // Total display string; adding m_strNewText at the end
m_Output.SetWindowText(m_strOutput); // Display the new text appended onto the old text
m_Output.GetScrollInfo(SB_VERT, &scrollInfo, SIF_ALL);
scrollInfo.nPos = scrollInfo.nMax;
m_Output.SetScrollPos (SB_VERT, scrollInfo.nPos, TRUE);
m_Output is the Edit Box and I was trying to set the scroll position to the current maximum, but no luck. i.e. the botton of the text.
I still have to use the mouse to click on the Edit Box scroll bar to display the end of the posted text.
Is it that difficult to have the behavour of the Edit Box scoll reversed?
I have tried many options/varients but still no luck!
|
|
|
|
|
When doing my homework, I had this code:
<br />
....<br />
int main(){<br />
const int a=10;<br />
int* p=(int*)&a;<br />
*p=100;<br />
int i=a;<br />
cout << "p=" << p << endl;<br />
cout << "&a=" << &a << endl;<br />
cout << "*p=" << *p << endl;<br />
cout << "a=" << a << endl;<br />
cout << "i=" << i << endl;<br />
return 0;<br />
}<br />
Here is the output:
p=0012FF7C
&a=0012FF7C
*p=100
a=10
i=10
I guessed that a had to be 100, but it's 10.
It seem that compiler has replaced all instance of variable a to 10 at compile time, event if a has been allocated a storage. So the trick to change a constant by casting its pointer is not effect. Is that right?
Any comment is welcome.
Thanks.
|
|
|
|
|
I do not understand your explaination very well, but the program seems logical to me.
const int a = 10; const: means 'a' is a constant wich you cannot change.
then put a in p (thus p = 10)
then put 100 in p and then i = a;
Where is your problem?
|
|
|
|
|
nguyenvhn wrote:
const int a=10;
where did you see it was 100 ??
TOXCCT >>> GEII power
|
|
|
|
|
toxcct wrote:
where did you see it was 100 ??
Here:
int* p=(int*)&a;<br />
*p=100;
Because p (who is a pointer) receives the adress of the variable a and then you put 100 in the content pointed by p (so, at the same adress than a)... So you replace the value of a.
But I don't understand why it prints 10 and not 100. The const keyword has something to do with it but I don't know what.... 
|
|
|
|
|
what do you think "const" mean ? constipated ?
for me (and for C/C++ also), it means "constant", that is, you cannot modify it ! that's all....
TOXCCT >>> GEII power
|
|
|
|
|
Yes of course I know this (I'm not completely stupid  ) but if you try to change the contents of it, you will have a compile error.
Or here, you change it by another way (using the adress of the variable). And there is no errors BUT the adress p and the adress &a are the same but their contents are different so there is something strange (two pointers that are pointing at exactly the same adress but the values they hold are different  )!!
It would be normal if *p still contain 10 at the end (that menas the content of a was unchanged)
|
|
|
|
|
in fact, the compiler don't say anything because const is an identifier for the compiler, and as we don't explicitely write into variable a, there is no compile error. but a is still const (certainly not even in the stack...) so *p cannot access the value correctly to alter it.
TOXCCT >>> GEII power
|
|
|
|
|
Sounds like your constipated!!!!!
|
|
|
|
|
hey man, first, you write as an anonymous, and secondly, where did you sense of humour go ???
did you trash it ? 
TOXCCT >>> GEII power
|
|
|
|
|
Sounds like your are constipated!!!!
|
|
|
|
|
pouet pouet pouet traallalalilouuu
TOXCCT >>> GEII power
|
|
|
|
|
if you do this:
int a = 10;
=> a is the value AND &a is the pointer
int* p = 100;
=> *p is the value AND p is the pointer
thus if I see correctly: int* p=(int*)&a; means that *p = 10 (* and & are opposites) and p and &a are still different. (you should do p = &a; if you would like to copy pointers)
Then again I could be mistaken (you always do working with pointers)
|
|
|
|
|
excuse me but int* p=(int*)&a; is as much correct as your p = &a;
secondly, you say
int a = 10;
a is the value AND &a is the pointer. a say NO. &a is the ADDRESS !!
and to finish, even if you're right, you don't answer the post to typed...
TOXCCT >>> GEII power
|
|
|
|
|
If you try to do
p = &a;
in this example the compiler will complain that it can not convert from const int* to int* ! 
Ant.
|
|
|
|
|
V. wrote:
int* p = 100;
=> *p is the value AND p is the pointer
Yes but he is assigning the adress of a in p just before:
int* p=(int*)&a;<br />
So p and &a are the same (in this case, the adress of &a).
|
|
|
|
|
and if you output *(int*)&a rather than a? 
Ant.
|
|
|
|
|
where do you see a difference between *(int*)&a and a you, except in confusing the reader ?? 
TOXCCT >>> GEII power
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
