Skip to main content

HotSpotMode enumeration

HotSpotMode enum has following values
Inactive
NotSet
Navigate
Postback

You can set HotSpotMode either on ImageMap control or individual HotSpot control for the ImageMap.

If you specify it on ImageMap only, all the HotSpot controls interhit the behavior. All HotSpot controls must be set to NotSet to inherit the behaviour.

If you specify NotSet on ImageMap and HotSpot control, the default behaviour is Naviagate.

If you specify NotSet only on HotSpot, it works out the behaviour based on the setting on ImageMap.

The setting on HotSpot takes precendence over the ImageMap.

The settings take precendence in the order they are specified. Hence you should specify inactive map before you specify active map to create complex mapping.

Comments

Anonymous said…
There are thousands of blogs and websites providing the same nature of information again and again, I guess they copy it from one another. Anyhow, the piece of information you have provided is something different and unique. Keep up the good work.

logo designer

logo designers
26 April 2012 at 11:09
Post a Comment

Popular posts from this blog

Why there is semicolon at the start of a JavaScript function?

Very often while reviewing the code for my team, I will come across a semicolon at the start of JavaScript function as show below ; (function () { 'use strict'; ...and I often wondered what purpose it served. Guess what. It is an insurance to make sure your script works fine when all other scripts are merged together;  The leading ; in front of immediately-invoked function expressions (iffe) is there to prevent errors when appending the file during concatenation to a file containing an expression not properly terminated with a ;. So there you go. Now you know what that little semicolon is doing there in your code.
3 comments
Read more

C# Performance Improvement - The Power of StringBuilder

 Often when we are wring code we don't think about performance and go with the default options available to achieve a task. String concatenation is one such scenario. If you are doing simple and few string catenations, then you can use the following result = string1 + string2; string1+= string2; result = String.Concat(string1,string2); String.Format and string interpolation are few other options.  However when you are performing large and repetitive  operation, string catenation can be expensive. Here is an example to prove the point.  As you can see it took 41 seconds to perform 100k string catenation. Now lets replace this with StringBuilder and see.  8 ms!!!!!! That is a massive performance difference. Hope you get the point. More info on StringBuilder can be found here https://learn.microsoft.com/en-us/dotnet/api/system.text.stringbuilder?view=net-7.0
Post a Comment
Read more