Hi,
By looking/reviewing at the current symbian qt mobility feedback api backend
and examples I found out these things. Comments from differents parties welcome!
- current backend uses MTouchFeedback* Instance() method to get pointer to
feedback object. These is used in every api call that is made. Is this ok way
or should it use CreateInstanceL/DestroyInstance methods and store pointer
inside backend for its lifetime. Is there some performance/ issues or any other
considerations? Also the backend plugin extends api classes allthough the api
says that MTouchFeedback class is not meant for extending outside lib.
- currently error handling is not taken care of. Leaving functions are not
called with TRAP harness.
- advanced tactile feedback is flagged with in symbian.pro file with this
"contains(S60_VERSION, 5.2)". Does it actually work? Is there 5.2 spesified in
symbian.conf?
--> May beed a config test to work properly. I am now testing this with
"exists($${EPOCROOT}epoc32/release/winscw/udeb/z/system/install/Series60v5.2.sis
)|exists($${EPOCROOT}epoc32/data/z/system/install/Series60v5.2.sis) " but I
think is not a proper solution with MCL builds. After changing this low-level
api tests seem to work better (I can change the duration, but intensity doesn't
quite work as it works in 5.0 (tube)).
- (N8) When changing the actuator to vibra from hapticsplayer application I get
this debug output:
03:24:05.826 [Qt Message] CActiveScheduler::RunIfReady() returned
error: -21. (and the vibra doesn't work. ) Probably a bug.
- Plugin priority function always returns PluginLowPriority? (minor issue, why
is it chose a low prio value?
- Hapticsplayer example application is missing cababilities:
03:17:36.351 *PlatSec* ERROR - Capability check failed - Process
hapticsplayer was checked by Thread hapticsplayer::hapticsplayer and was found
to be missing the capabilities: ReadDeviceData . Additional diagnostic
message: Checked whilst trying to Get a P
03:17:37.386 *PlatSec* ERROR - Capability check failed - Process
hapticsplayer was checked by Thread hapticsplayer::hapticsplayer and was found
to be missing the capabilities: WriteDeviceData . Additional diagnostic
message: Checked whilst trying to Set a
-> added to pro file: symbian: {
TARGET.CAPABILITY = WriteDeviceData ReadDeviceData
}
Api spesific comments.
- these is know status change signals in api. If there was it would be easier
to code clients using this api (meaning when that effect is done, do this one).
Or have I missed something?
-antti
_______________________________________________
Qt-mobility-feedback mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
