|
Poor Kataric's head hurts.
But seriously, the FCL can't handle a right click the same way it handles a left click?
How come the button, even when no controls are present, depresses on a left click, but not on any other click, and would using mouseup provide the necessary depression animation?
|
|
|
|
|
You're thinking pretty clearly, if your head hurts.
The point should be this: Animation or whatever, you have to use the event required to trigger the animation or whatever. If you want/need to animate the down state of the button at mouse down, you'll have to handle that much with mouse down. If you want to trigger the right click at mouse down... the same applies. If you want to trigger it at mouse up... you'll have to use that event. To animate the up state (if you're animating the down), you'll have to use the appropriate events here as well. That may be MouseUp, exit, on focus change. You'll see which you have to use for what you want to do by taking a careful look at the control -- it furnishes the tools you *can* use to accomplish what you have or want to do. If it doesn't provide an event opportunity, you may be able to build one in, but the possibility of that too depends on having a driving event you can work with.
|
|
|
|
|
For example, the snippet I provided added a RighClick event to a button class, using the OnMouseDown event.
|
|
|
|
|
So the left click is just intrinsiclly written to animate on mouse down and mouse up?
|
|
|
|
|
Yes. I for one don't care about the animation, so my solution doesn't supply it either.
I suspect to have it you would need to write/derive your own Button that does the same (override the OnPaint method et al).
I won't bother, I hope the "next" version of .net has it built in, until then I'll simply have Buttons and whatever that kinda sorta respond to right-click, but don't depress.
|
|
|
|
|
That's right. The animation behavior can be added to the button class so that the button responds/animates to right mouse button behavior like it does the left, if, and only if, the button class allows you to invoke the down state. I build an extensive heirarchy of such button classes for the further purpose of supporting toggle behavior, which requires that you programmatically set a down state -- the same state you need to invoke to support your right click behavior.
I know it seems strange that the developers of the native FCL button class did not provide this type of functionality for you -- including a native right click. Sometimes there's a good underlying technical reason. In this case, I don't believe so. The fact that so many of us run into this issue and are obstructed from emulating all the desirable behavior in a practical way indeed supports our sentiments. The fact is (I adamantly believe), this is a perfect example of designers not doing the job the way the job needs to be done. But you can see how carried away they got with further adverse themes when you start getting involved in button renderers and all the further baggage thrown in. By the time you can get your brain around the basic, *undocumented* idea they had, you can write your own button class that even draws itself more efficiently. .NET is really slow across broad areas, and this kind of unnecessary overhead is a major reason why, because *nothing* comes without performance or resource footprint cost. Don't follow their example. Build clean, simple designs that *get* *the* jobs done. We used to say, "Keep it simple, STUPID." (KISS)
|
|
|
|
|
Ohhhhh, Kataric! When he said "KATARIC" I thought it was an acronym with which I'm unfamiliar.
Like, maybe, "Keep All The Access Rights In Check" or something.
|
|
|
|
|
Well, I just spent another five hours reworking my MouseTrap class.
It's way better than what I did yesterday. I'll probably write an article on it, but if you'd like be beta testers let me know.
|
|
|
|
|
I got it working guys. The MouseDown worked it seems.
This ended up being my solution.
//Init Function
this.button[i].MouseDown += new MouseEventHandler(Quest202_MouseDown);
//Handler Functions
private void Quest202_MouseDown(object sender, MouseEventArgs e)
{
switch(e.Button)
{
case MouseButtons.Left:
OnLButtonDown(sender);
break;
case MouseButtons.Right:
OnRButtonDown(sender);
break;
}
base.OnMouseDown(e);
}
private void OnLButtonDown(object sender)
{
Button temp = sender as Button;
if (temp != null)
temp.BackColor = Color.Red;
return;
}
private void OnRButtonDown(object sender)
{
Button temp = sender as Button;
if (temp != null)
temp.BackColor = Color.Black;
return;
}
Thank you for all your help. I really appreciate it.
|
|
|
|
|
|
Users? I'm writing this as an exercise for myself to learn c# becasue I don't know jack about it honestly.
Perhaps if what i'm doing transforms into something that might appeal to other people, I'll rewrite it to use more stable (if what i wrote is unstable, still don't know that) classes and whatnot.
Again, thanks for all your help guys. I'm sure I'll have more questions as I go along.
|
|
|
|
|
Well you're learning Jack now.
|
|
|
|
|
He's a great guy isn't he?
|
|
|
|
|
Hello,
I am developing a site with a ASP 2.0 Login control. The validation message works fine if the user's password is not correct.
When the password is the wrong case it does not login in the user, which is fine, but it does not fire the validation message either, which is a problem.
Can anyone point me in the right direction on getting the validation to work on incorrect case?
Thanks.
|
|
|
|
|
Translate both the original password and input password (attempt) to one case before comparing. (Most people don't want the incorrect case to be acceptable.)
|
|
|
|
|
Mike, correct. I don't want the incorrect password case to work.
If the user does not put in the correct password a validation message displays. I want this same message to display when a user uses the wrong case. Right now it just does a post back with no error message, it should be giving me the incorrect password message.
Any ideas what could be causing this?
|
|
|
|
|
The only thing that comes immediately to mind is to look for configuration properties related to case.
|
|
|
|
|
How do I create a windowless daemon in VS2005? Thx
|
|
|
|
|
A windows service can be considered a windowless daemon.
To create one, go to file>new>project and in your language of choice, choose Windows projects and Windows Service.
From there it's pretty self-explanitory.
HTH,
~dnc
|
|
|
|
|
Just as a community note: a windows service is not available w/ VS standard edition -- you must go higher.
Thx
|
|
|
|
|
LOL... sorry, I forget about that often... You could get around that by writing a console app and then using something like FireDaemon (I think that is the name?) that allows you to run an application as a service in Windows.
~dnc
|
|
|
|
|
public static Bitmap FromResource( IntPtr hinstance, string bitmapName ) I see that many others have had trouble getting Bitmap.FromResource() to work for them, and I've found conflicting or wrong information as to how to acquire the handle. Some examples call out to unmanaged functions. I'd like to avoid that if possible.
I have a VS2005 assembly DLL to which I've added many bitmaps as embedded resources (via Project.Properties...Add Files...). I assume that much is OK. Is there an entirely "managed" way to get the handle of the assembly to pass to the hinstance argument of FromResource()? If not, what is the recommended process?
|
|
|
|
|
For instance...
using System.Diagnostics;
myBitmap = Bitmap.FromResource( Process.GetCurrentProcess( ).Handle, @"MyBitmapResourceName" ); This call fails, reporting that the "Parameter is not valid."
|
|
|
|
|
This approach appears [?] to get a legitimate handle. The value is usually just over 1,000 -- 1,008, 1,032, etc. I've checked MyResourceName over and over again for case. I've tried all uppercase (which doesn't match the resource name), and I've tried odd syntax that I've seen in other examples (which resort to native C++ to get a handle) such as prefixing MyResourceName with "#" or including the file extension (which in my experience with resource files should be an error)... but still, all I get is a "Parameter is not valid" error:
IntPtr hInstance = Process.GetCurrentProcess().Handle;
if ( (IntPtr)0 != hInstance )
myBitmap = Bitmap.FromResource( hInstance, "MyResourceName" );
Process.GetCurrentProcess().Handle is as close as I've come to succeding, in that the value is possibly a legitimate handle/IntPtr value. Does anybody know how to do this?
|
|
|
|
|
hi
i have some tab controls and in tab_2_enter event, i want to set focus on specifid toolStripTextBox and selectAll method, but in runTime, when i enter to tab_2, toolStripTextBox does not selected, how to solve my problem ?
thanks
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
