Age | Commit message (Collapse) | Author | Files | Lines |
|
If the dialog sizeHint is smaller than the width of the desktop
qpe_show_dialog didn't 'maximize' the widget and just showed it.
QPEApplication::showDialog does better in that respect but does not
have custom 'centering' of the dialog. But that doesn't matter
as we save/restore size and position for BigScreen.
|
|
|
|
LIBQPE_WIHTROHFEEDBACK already in $OPIEDIR/config.in
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
__attribute__((unused))
|
|
(Important for MAC)
|
|
of the new value. This deletes the timer and would fix possible
shortage on timer resources
-A small friend to hook to an internal signal to avoid problems
in Opie::Core::ODevice entering the event loop to wait for
the sound to be finished. processEvents() can give strange results as
some applications do not expect that the eventloop is entered. This
could possible deliver a Timer, or an Event from QSocketNotifier
which could give all kind of problems of wrong reentrancy.
So let us avoid it.
|
|
the 'moc' as it doesn't have a preprocessor in Qt2 and Qt3
|
|
-Use only a define in library.pro and add source code
conditional.
|
|
is to enable precompiled header support with Opie. Compiling results
are already quite promising.
|
|
|
|
- changed *.pro file to compile in backend
- some more fixes to rohfeedback and qpeapplication
|
|
mickey thanks for spotting the linking failures :}
|
|
into QPEApplication
Icons and Config Option will be comitted by WIMPIE
|
|
this could help Opie/X11 build
|
|
|
|
|
|
|
|
- tagged 1.1.4 in CVS
- bumped version to 1.1.5-snapshot
|
|
|
|
|
|
Now this should handle mac and linux with qte 2.3.7 and above ..
|
|
Weak symbols just protect us against unresolved symbols at runtime. But, if it
is unresolved at compile time, linking will fail !
|
|
by OMAF
|
|
multiple includes and while I touched the file I updatet the
QPE license header
|
|
-In regards to precompiled headers drop the 'protected -> public define hack'
and use TrollTechs solution inspired from QETWidget to static_cast to
a private reimplementation to change the method. This was taken from
Qtopia
|
|
QPEApplication creation.
Also update the comment in the API docu as now FontFactories are loaded
|
|
|
|
|
|
- honor FontFamily and FontSize as set in qpe/Appearance
- NOTE to packagers: Remember to ship appropriate qpe.conf files for the different devices!
|
|
Somehow the Launcher triggers issues with libqpe and MimeType.
Due the mix of calling MimeType::clear, MimeType type(doclnk.linkFile()),
MimeType::clear
the registration of Application was cleared and not reentered due the
inner static variable in MimeType::init which was set.
Now make sure that if we clear that we will reenter the Application in all cases!
|
|
- replace system-call "mkdir..." with QDir::mkdir
|
|
- use POSIX rename
|
|
- cleanup code
|
|
This works on Qt2.3.8 and Qt2.3.7
|
|
|
|
|
|
|
|
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...
|
|
use rm -rf on directories, not just -f
|
|
|
|
|
|
|