Age | Commit message (Collapse) | Author | Files | Lines |
|
My QPEApplication does not have a public copy constructor. so we simply
avoid using it by creation the application directly.
|
|
it to 'Transformed' when launching rotated apps.
Patch courtesy Manuel Teira
|
|
Remove the setStyle and setFont overrides
as a result remove settings from the buildsystem and the Apperance GUI
We do this as we won't run NeoCal or TKC Apps on a GCC3 (now default compiler)
libqpe, to run these applications one can use oz-compat
|
|
party apps against our headers
|
|
-QWSDecoration scaling fixes by mickeyl
-Readd macros for DEPRECATED and VISIBILITY
-Move out showWidget and execDialog to widget_sowing.cpp
-QPE_EXPORT_SYMBOL for Q_EXPORT_INTERFACE
-Deprecated for FileSelector, QPEMenubar and Toolbar
|
|
|
|
- changed *.pro file to compile in backend
- some more fixes to rohfeedback and qpeapplication
|
|
U _ZN14QPEApplication6polishEP7QWidget
ich@opiezilla:~/programming/opie/head/opie$ nm lib/libopiecore2.so | grep polish
U _ZN12QApplication6polishEP7QWidget
in qt_override we had to overwrite the Palette for some widgets for some styles (setting no
background liquid and such) we overwrote the polish method.
As we did not inherit from QPEApplication the 'polish' symbol was only internal to
libqpe and this way Opie apps worked on Opies and Sharps libqpe, and Sharp apps work
on our libqpe. Now with libopiecore the compiler tries to include different symbols as shown above.
So for now we could disable the legacy palette polishing which shouldn't hurt anyway.
OApplication is the source of all evil, we wouldn't 'pull' in the polish symbol... but having
a 'shadow' weak symbol as backup isn't good as well.
Chicken you may enable the option in config.in...
|
|
widget to front)
|
|
only the taskbar size is approximated
|
|
|
|
|
|
|
|
|
|
and include the top level widgets in the to be iterated widgets
|
|
|
|
I've included 2 patches need to make opie support on the fly screen
resolution changing. This is done with the following,
qcop "QPE/System" "setCurrentMode(int,int,int)" 480 640 16
This is good for running applications in compatibility mode on the C700.
As you can see there isn't much to these patches.
|
|
iterate over the list and activate the next one.
-Install translation in .qm
-Add an else again ( was lost in a merge )
|
|
boards need
QPE_NEED_CALIBRATE
-launcher is the only one executin application
-allow processing of QCOPfiles after start ( qpeapplication )
-qcopenvelope no longer calls Global::execute
|
|
to prepare the possibility of building an opie 1.0 feed for the sharp rom
|
|
Install libopie.qm make apps fully translatable...
refactor installing trans into a method instead of having the same code copy
and pasted three times
|
|
started apps as well as those currently running.
Differs from setDefaultRotation in that 1) it rotates currently running apps,
and 2) does not set deforient or save orientation to qpe.conf.
|
|
|
|
|
|
a client (consistent to setDefaultRotation's behaviour)
|
|
changed the opiemail config.in files to the correct dependencies. How did this slip in again ?
- qApp->desktop()->qwsDisplay()->setTransformation( e );
+ //qApp->desktop()->qwsDisplay()->setTransformation( e );
|
|
Changed the opiemail config.in files to the correct dependencies. How did this slip in again ?
|
|
|
|
adapt depends to the actual required qt version.
|
|
- applications get *all* key events now, as long as they have the focus
- an application decides if it has the keyboard grabbed or not
- if it's grabbed, the app consumes the key press
- if it's not grabbed and a F1-F29 key is pressed, the app sends a QCop
call to the launcher (deviceButtonPressed(...))
- when the launcher receives a QCop deviceButtonPressed it simply sends
the configured QCopEnvelope
- all "special" actions (like menu, home) are now accessible via QCop
calls (see buttonsettings)
|
|
application
|
|
- added qt_override.* which provides the same functionality as libpreload
(the new -override patch for Qt/E is needed for this to work/compile)
- changed qpeapplication a bit to accomodate the new interface
|
|
still to test
bic changes to be resolved
more changes to be made?
|
|
are exactly like setVolume and volumeChange excopt of course, they
change the mic input level instead of the volume out level.
|
|
|