Reply to: .Net click through forms

[ASB]

Actually, there might be a slight overhead in loading the stopwatch wrapper object (needs to load the Diagnostics assembly?) so DateTimeNow.Subtract(someStoredVal) would probably be marginally quicker.

I liked the modal dialogue suggestion.

And all because the lady loves Milk Tray.

Out of interest (and boredom) I had a look at it in reflector. It does have a call to a kernel function on first instantiation to discover if it's high res or not. I it calls the same functions as datetime.now does in general. I think one would need a few hundred billion iterations to find a timeable difference though..

[ASB]

Or to save using a timer, store the system time at form load and if the new form's button is clicked less than 200ms or so after form load, ignore it. 3 lines of code I expect.

btw stopwatch is not a timer. It is just a wrapper round datetime. It's lightweight. However it does some more calculations than would be done with using datetime.subtract.now.subtract.

[TheBigYinJames]

I doubt there is any difference in efficiency between datetime.now.subtract and using a stopwatch.

Actually, there might be a slight overhead in loading the stopwatch wrapper object (needs to load the Diagnostics assembly?) so DateTimeNow.Subtract(someStoredVal) would probably be marginally quicker.

I liked the modal dialogue suggestion.

And all because the lady loves Milk Tray.

[ASB]

Can't remember off the top of my head what the resolution of DateTime is, in earlier .Net it was as large as 500ms. Stopwatch will use high def if it's available.

The precision has always been (according to the Docs) 100 Nanosecs. However there are some issues:-

https://connect.microsoft.com/Visual...?wa=wsignin1.0

Internally the stopwatch uses datetime.utcnow - which is precisely what datetime.now does.

I doubt there is any difference in efficiency between datetime.now.subtract and using a stopwatch.

[TimberWolf]

Can't remember off the top of my head what the resolution of DateTime is, in earlier .Net it was as large as 500ms. Stopwatch will use high def if it's available.

Ah, I see you'd proposed a similar and probably more exact solution earlier. My bad.

[Bright Spark]

display a small modal form saying "Loading..." for about 3secs when first button is pressed.

[TheBigYinJames]

Or to save using a timer, store the system time at form load and if the new form's button is clicked less than 200ms or so after form load, ignore it. 3 lines of code I expect.

Can't remember off the top of my head what the resolution of DateTime is, in earlier .Net it was as large as 500ms. Stopwatch will use high def if it's available.

[TimberWolf]

Or to save using a timer, store the system time at form load and if the new form's button is clicked less than 200ms or so after form load, ignore it. 3 lines of code I expect.

[ASB]

Xog,

Firstly I don't think it's a double click, otherwise the doubleclick event of the button should fire. So it's two single clicks not quick enough. The second click message is not dispatched until the click handler completes. However at this point this is just a message up the spout and the target is unknown. After the click event completes the message causes a click even on the second form because this is what is valid at that screen location at the time of dispatch.

The basic problem you have is that you don't want to respond to the second click until you are in a known state and that is after all message pumping.

If you make sure buttons on the form as disabled at load time and then enable them in the show event the second form is fine. Unfortunately this means the click will go to the first form which may be unhelpful........

TheBigYinJames solution is probably the pragmatic one.

However you could use a custom windows message and override the message queue - but this seems like a lot of faffing about.

[xoggoth]

Not practical to change forms as both have numerous "buttons", actually labels forming hot spots on a picture. Too restricting to avoid any coincidence of positions. Is the two shown at top here:

http://www.gatekeeperel.co.uk/animalsuk.html

[Durbs]

Does sound like a user education issue though.

Not really, if you need to educate users to use your interface, generally your interface design is flawed, not the users so i'm guessing re-education is not the answer he's looking for.

Can you not just alter the part of the screen it appears on? Or is this a full screen thing. Hard to say without seeing it but i'd look to re-do the layout of the child form before fudging with timers/fade-ins etc.

[Scrag Meister]

Is the Double click event being triggered?

Or is it 2 slow single clicks?

Does sound like a user education issue though.

[xoggoth]

It's for kids so they probably don't just double click, they go clcik cklickety clicketyclicktey clcick clcikchchhk...

[TheBigYinJames]

Ta but not possible, there are a whole load of buttons on both forms.

Tell the users not to double click buttons? Do they press BBC1 twice when they change channel on the TV?

What about ignoring the click of the child button for the first 500ms (rather than disabling it?

create a global System.Diagnostics.Stopwatch, start it in the form init code.
In the click handler, wrap the code in an if .ElapsedMilliseconds > 500

[xoggoth]

Ta but not possible, there are a whole load of buttons on both forms.