Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
isn't needed
it is LIBOPIE2DB anyway
|
|
|
|
|
|
|
|
|
|
|
|
|
|
all view use the same config object otherwise there will be problems writing
a new config
|
|
|
|
|
|
opie-eye specifics are implemented. So we can move that into the
MM lib and use it in other programs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
opiepim links with opiedb2 -> needs depend in config.in
qlibrary_unix -> print dlopen errors ALWAYS not only indebug
BTmanager.pro needs opieui2
|
|
modified this define to optimistically
|
|
|
|
|
|
|
|
implement key handler for arrow keys
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
and fixed compiler warning
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Factory is the same as in OPIE_EXPORT_APP, name is the display name
(third parameter of OApplication). In non-quicklaunch mode it will generate
a Opie::Core::OApplication object instead of a QPEApplication object.
|
|
|