| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Task-number: 254824
|
|
|
|
|
|
|
|
|
|
| |
Move initialization of QAction/QActionGroups elsewhere.
Detect the root widget by checking its parent against
the parent widget passed in and apply only
the size part of the geometry property to it.
Task-number: 254824
Initial-patch-by: joao <joao@abecasis.name>
|
|
|
|
|
|
|
|
|
|
|
| |
When you set -showinternal on the command line, qdoc will include
everything marked \internal in the documentation. This flag is not
very useful at the moment for two reasons: (1) It generates hundreds
of qdoc errors because most of the things marked with \internal don't
have any documentation anyway, or the documentation has other errors
in it that weren't being detected because of the \internal. (2) There
is a bus error toward the end, which I haven't tracked down yet. For
now, use -showinternal at your own risk.
|
|
|
|
| |
Reviewed-by: Friedemann Kleint
|
|
|
|
|
|
| |
These changes were added to qdoc in the days when we thought we
might switch to doxygen. Now we have taken the approach of making
qdoc output be more doxygen-like, so this ifdefed code is now dead.
|
|\
| |
| |
| |
| | |
Conflicts:
src/gui/embedded/qkbdtty_qws.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When a form is loaded, Designer will set the path to the resource as
an absolute path rather than the path actually stored in the file. There
is code to work around this to make file paths relative when saving the
file later on, but no work around for Qt Jambi. So when saving Qt Jambi
forms, you would get an absolute path to the resource which contains the
location of the resource file (.jar or on disk) This of course breaks
the concept of resources, as the .jui file was no longer portable. The
fix is to special case Qt Jambi resources and set the relative path
when loading them.
The patch has no effect on regular Designer.
Task-number: 254621
Reviewed-by: Kai Koehne
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Additionally we turn -ltcg on by default on Windows CE.
See commit 56191830 for details.
Reviewed-by: mauricek
BT: yes
|
| |
| |
| |
| |
| | |
used character operations whenever possible
better usage of QLatin1String
|
|\ \
| |/
| |
| |
| | |
Conflicts:
tests/auto/qtreeview/tst_qtreeview.cpp
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Thomas Sondergaard (2):
Danish translations
Updated danish translations. Added them to relevant project files.
Request-url: http://qt.gitorious.org/qt/qt/merge_requests/549
Reviewed-by: Simon Hausmann <simon.hausmann@nokia.com>
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Reviewed-by: kh
|
| | |
| | |
| | |
| | |
| | |
| | | |
Correcting invalid padding values. none is not a valid padding value.
Rev-by: David Boddie
|
| | |
| | |
| | |
| | | |
Task-number: 249222
|
| | |
| | |
| | |
| | | |
Task-number: 251486
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There was an empty <div> element with a name that came after it.
I moved the name inside the <div> element. And there were some <b>
elements that began inside one element and ended inside the next
element. I just removed them, because they didn't really add
anything. And I made the "Access functions:" bold.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Crash when replacing the QDockWidget contents
widget by a widget using a container extension.
Task-number: 254553
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
sneak in white space change :)
|
| | |
| | |
| | |
| | | |
Reviewed-by: Martin Smith
|
| | | |
|
| | |
| | |
| | |
| | | |
Reviewed-By: David Boddie
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The form builder used for preview of the templates did not implement
custom widget handling (FormBuilder::createCustomWidgets()).
On encountering a promoted widget, the widget factory
would then create a Widget Database entry specifying QWidget
inheritance (emergency fallback) which could not be overidden later
on.
To fix this, moved the code for handling custom widgets from
QDesignerResource to QSimpleResource and create a new
formbuilder class that handles it especially for the New Form Dialog
preview.
Task-number: 254282
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In Java, "null" is represented as a keyword, not as the integer 0. The
old code assumed the latter. Code such as
translate("fooBar", "fooBar", null);
would thus not be detected by lupdate when parsing Java files.
Reviewed-by: ossi
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
doc/src/stylesheet.qdoc
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-By: Kavindra Palaraja
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: Trust Me
|
| |\ \ \
| | |/ / |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
immensely increase readability"
This was pushed accidentially.
This reverts commit ffecdf0bf9f25f7ab9aa4f69e37507dd595fecea.
|
| | |\ \ |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
increase readability
Unfortunately the patch causes quite some regressions and I think some refectoring of this class
would be needed.
I didn't do that since there is no API docs, the variable naming is not very clarifying and the
code is hard to read due to it not using the coding style and mixing tabs as well as spaces.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Reviewed-By: David Boddie
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now we have explicit columns we cann make our docs look a bit better using
some simple css additions. This adds light backgrounds in targetted
places to make the text more readable.
|
| |\ \ \ \
| | | |/ /
| | |/| |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
src/corelib/kernel/qobject.cpp
src/corelib/kernel/qobject_p.h
src/network/access/qhttpnetworkconnection.cpp
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Restore 4.4 behaviour by using a QStackedLayout as the layout containing
the actual form (as was in 4.4). The difference in behaviour was caused
by insertion of an additional widget with a QVBoxLayout which is supposed
to ease setting of inheritable properties (style, etc).
Reviewed-by: Kai Köhne <kai.koehne@nokia.com>
Task-number: 253236
|
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
QDesignerFormWindowCursor::setProperty.
Ensure the text does not get clobbered by the subproperty handling.
Reviewed-by: Kai Köhne <kai.koehne@nokia.com>
Task-number: 253278
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | |/ /
| | | |
| | | |
| | | | |
Conflicts:
tools/macdeployqt/shared/shared.cpp
|
| | |/
| | |
| | |
| | |
| | |
| | | |
foo == QString() should be foo.isNull(). Fixes 7 warnings in the Norwegian Breakfast Network
Reviewed-by: Samuel
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Turning on LTCG affected too many projects, where customers applications
would take a long time linking, severly affecting their development time
(even though it was only added for release builds)
We turn it off by default, and add a -ltcg configuration option, and the
possibility to also do CONFIG+=ltcg in projects, should they not want it
for Qt, but in their own projects. (Same, they can build Qt with it, and
do CONFIG-=ltcg for their project)
Reviewed-by: andy
|