Autodesk 15606-011408-9300 Developer Guide - Page 71

Browser Differences, Event Observer Set Methods

Page 71 highlights

Browser Differences The following table summarizes the basic differences between how Netscape Navigator and Internet Explorer handle events: Netscape Navigator Internet Explorer For Netscape Navigator, Autodesk MapGuide provides an observer applet that you embed in your application using the tag. For Autodesk MapGuide Viewer Plug-In, this applet is called: MapGuideObserver6.class For Autodesk MapGuide Viewer, Java Edition, it is called: MapGuideObserver6J.class You can use the same instance of the observer applet for all events. For Internet Explorer, you write a few lines of VBScript code that tell Internet Explorer the name of the event handler. You must create a separate event handler for each type of event you want to handle. To call an Autodesk MapGuide method that triggers an event, you pass the Autodesk MapGuide observer as a parameter. Internet Explorer knows how to find the event handler without being passed its name because it assumes the event handler name will match the event it is handling. Event Observer Set Methods There are some MGMap methods whose sole function is to allow you to set an observer for a specific event. For example, when the map view changes (for example, in response to a user panning or zooming), you can set the observer for the onViewChanged by creating a function called onLoad (a browser event) and inserting the MGMap.setViewChangedObserver method to set the observer for the onViewChanged event. You can do this for each of the events you want to handle. Note that specifying an observer is not required for all events-just for the events you want to handle. Working with Event Handlers | 71

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208

Working with Event Handlers
|
71
Browser Differences
The following table summarizes the basic differences between how Netscape
Navigator and Internet Explorer handle events:
Event Observer Set Methods
There are some
MGMap
methods whose sole function is to allow you to set an
observer for a specific event. For example, when the map view changes (for
example, in response to a user panning or zooming), you can set the observer
for the
onViewChanged
by creating a function called
onLoad
(a browser
event) and inserting the
MGMap.setViewChangedObserver
method to set
the observer for the
onViewChanged
event. You can do this for each of the
events you want to handle. Note that specifying an observer is not required
for all events
just for the events you want to handle.
Netscape Navigator
Internet Explorer
For Netscape Navigator, Autodesk
MapGuide provides an observer applet
that you embed in your application
using the <
APPLET>
tag.
For Autodesk MapGuide Viewer Plug-In,
this applet is called:
MapGuideObserver6.class
For Autodesk MapGuide Viewer, Java
Edition, it is called:
MapGuideObserver6J.class
You can use the same instance of the
observer applet for all events.
For Internet Explorer, you write a few lines
of
VBScript
code that tell Internet
Explorer the name of the event handler.
You must create a separate event handler
for each type of event you want to handle.
To call an Autodesk MapGuide method
that triggers an event, you pass the
Autodesk MapGuide observer as a
parameter.
Internet Explorer knows how to find the
event handler without being passed its
name because it assumes the event han-
dler name will match the event it is
handling.