misoget_thread_priority()EPriorityNull (-30, cannot be set by user code),
EPriorityMuchLess (-20),
EPriorityLess (-10),
EPriorityNormal (0),
EPriorityMore (10),
EPriorityMuchMore (20),
EPriorityRealTime (30),
EPriorityAbsoluteVeryLow (100),
EPriorityAbsoluteLow (200),
EPriorityAbsoluteBackground (300),
EPriorityAbsoluteForeground (400),
EPriorityAbsoluteHigh (500,
highest possible apart from the kernel).set_thread_priority(integer priority)get_process_priority()EPriorityLow (150),
EPriorityBackground (250),
EPriorityForeground (350),
EPriorityHigh (450),
EPriorityWindowServer (650),
EPriorityFileServer (750),
EPriorityRealTimeServer (850),
EPrioritySupervisor (950).set_process_priority(integer priority)num_alloc_heap_cells()num_free_heap_cells()alloc_heap_cells_size()heap_biggest_avail()heap_total_avail()check_heap()heap_base_address()alloc_heap_cell(integer size)free_heap_cell(integer address)disk_total_avail(integer drive_num)get_subst_path(integer drive_num)create_drive_subst(integer drive_num, unicode path)local_bt_name()local_bt_address()imei_code()set_hal_attr(integer attr, integer value)get_hal_attr(integer attr)tick_count()reset_inactivity_time()take_photo([(integer, integer) size] [, integer format] [, integer quality] [, integer samplescheme])Takes a photo using the number 0 camera of the device, if any, and returns it as a JPEG. The operation can fail for a number of reasons, such as the camera being in use by another application. Any failure results in an exception being thrown.
The function supports the following named arguments:
size which is a tuple of integers,
format which is a EFormatConstant,
quality which specifies the JPEG quality and
samplescheme which is a TJpegImageData constant.
Only available on Symbian OS 7.0s and higher.
Supported values for the keyword parameters are as follows:
size is a tuple of (width, height).
What values are recognized depends on the phone;
always available are (160, 120), (320, 240) and (640, 480).
The 7610 also supports (1152, 864).
format may have the following values:
EFormatFbsBitmapColor4K (0x040),
EFormatFbsBitmapColor64K (0x080),
EFormatFbsBitmapColor16M (0x100).
quality defines the JPEG quality and is an
integer in the range of 0 to 100 (both inclusive).
samplescheme defines which method of
color sampling is used in the JPEG. Possible values
are:
EMonochrome (0),
EColor420 (1),
EColor422 (2),
EColor444 (3).
vibrate(integer duration, integer intensity)Runs the vibra motor for the specified duration of time at the specified intensity. The duration is specified in milliseconds, and must be greater than zero. The intensity is a value between -100 and 100 (inclusive), and it specifies percentage of full rotation speed. Positive and negative values cause rotation in opposite directions; a zero value indicates no rotation, and thus it makes little sense to call this function with 0 intensity argument.
Vibration will not work unless enabled in the profile. Only supported on Series 60 2nd Ed FP2 and higher.
FsNotifyChange()FsNotifyChangenotify_change(integer type, callable callback [, unicode pathname])Asynchronously requests notification of changes either anywhere in the filesystem, or only in locations matching the optionally specified pathname (which may contain wildcards).
The type parameter indicates the kind of change that should
result in notification—its value should be one of:
ENotifyEntry=0x00
(directory addition or deletion, or change of disk in a drive),
ENotifyAll=0x01
(any change),
ENotifyFile=0x04
(file creation, rename, or deletion),
ENotifyDir=0x08
(directory creation, rename, or deletion),
ENotifyAttributes=0x10
(attribute change),
ENotifyWrite=0x20
(change resulting from a write to a file),
ENotifyDisk=0x40
(change resulting from a raw write to a disk).
If the registration to observe for changes fails, this method
throws an exception, and no change notification will be delivered.
Otherwise a change notification request will remain pending until
either delivered, or cancel or close is called,
in which case the request gets cancelled without notification.
Change notification is delivered by calling the callable object provided as a parameter. It should accept a single integer argument, which will be passed as 0 to indicate that a filesystem change has taken place. If change observation fails, the callback will be called with a negative argument, which is a Symbian error code that should give some indication of the cause of the failure. The callback is not allowed to throw an exception; if it does, the calling thread will be panicked.
Only one request per FsNotifyChange object may be
outstanding at any one time, and it is an error to call this
method when there is an outstanding request. Once a request
completes, it is necessary to make a new request to observe
for subsequent changes—it is okay to call this method from
within the callback.
cancel()close()