Disclaimer: I am not going to claim to know much about this, but I ran across some information in my files today and thought I would pass it along. I printed this information in 2001, so it is old, but I suspect still relevant. The point of this disclaimer is: Don’t send me emails or feedback asking me for more information about this.
The following explains the fields in a DB_notify_events database entry in the .DB files used by Platform Builder. This information could be useful for setting up an entry in your Platform.db or Project.db files to handle notification events.
Example Entry:
Database: "DB_notify_events" : 0 : 1 : 0001001F : 0
Record :
Field : 0001001f : "repllog.exe"
Field : 0002001f : "AppRunAtRs232Detect"
Field : 00030013 : 9
End
The fields of the Record are:
Field
|
Data
|
0001001f
|
Application to run when the event is triggered. In this case repllog.exe which handles ActiveSync connections
|
0002001f
|
Command line to pass to the application when it starts. In this case AppRunAtRs232Detect.
|
00030013
|
The notification event value that entry should handle. In this case 9 which is NOTIFICATION_EVENT_RS232_DETECTED. Oddly, the RS232 detected event is used to start ActiveSync connections, even if the connection is USB.
|
Notification Event Values:
Event Macro Name
|
Event Value
|
NOTIFICATION_EVENT_NONE
|
0
|
NOTIFICATION_EVENT_TIME_CHANGE
|
1
|
NOTIFICATION_EVENT_SYNC_END
|
2
|
NOTIFICATION_EVENT_ON_AC_POWER
|
3
|
NOTIFICATION_EVENT_OFF_AC_POWER
|
4
|
NOTIFICATION_EVENT_NET_CONNECT
|
5
|
NOTIFICATION_EVENT_NET_DISCONNECT
|
6
|
NOTIFICATION_EVENT_DEVICE_CHANGE
|
7
|
NOTIFICATION_EVENT_IR_DISCOVERED
|
8
|
NOTIFICATION_EVENT_RS232_DETECTED
|
9
|
NOTIFICATION_EVENT_RESTORE_END
|
10
|
NOTIFICATION_EVENT_WAKEUP
|
11
|
NOTIFICATION_EVENT_TZ_CHANGE
|
12
|
NOTIFICATION_EVENT_MACHINE_NAME_CHANGE
|
13
|
NOTIFICATION_EVENT_RNDIS_FN_DETECTED
|
14
|
NOTIFICATION_EVENT_INTERNET_PROXY_CHANGE
|
15
|
Copyright © 2009 – Bruce Eitman
All Rights Reserved