| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Updated version of LGPL and FDL licenseheaders.
Apply release phase licenseheaders for all source files.
Reviewed-by: Trust Me
|
|
|
|
|
|
|
| |
Add missing space to make the warning align with the others. Fix is needed
to let QtCreator detect the warning programatically.
Reviewed-by: Tom Sutcliffe
|
|
|
|
|
|
|
| |
Symbian.
Task-number: QTBUG-18764
Reviewed-by: kkoehne
|
|
|
|
|
|
|
|
| |
Print a warning if the user passes -qmljsdebugger on command line, but
Qt is configured with -no-declarative-debug
Change-Id: I72c9ffad9631ffe8582c13e3a4e798b102d0efad
Reviewed-by: Christiaan Janssen
|
|
|
|
|
|
|
|
|
| |
Allow applications to link against the QDeclarativeDebugService API.
This is needed for on-device debugging of QML. (The removal of
the symbols was a regression in 4.7.2).
Task-number: QTBUG-17503
Reviewed-by: Tom Sutcliffe
|
|
|
|
|
|
|
|
|
| |
On Windows, qmake places the tcpserver.dll in a 'plugins\qmlreleaseging'
folder, which broke remote debugging of QtDeclarative completely. New name
'qmltooling' while being not so specific, avoids the use of 'debug' in the folder name.
Task-number: QTBUG-17360
Reviewed-by: Martin Jones
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| |
| |
| | |
Make sure that e.g. QtCreator compiled with 4.7 can debug a program
compiled with 4.8.
Reviewed-by: Christiaan Janssen
|
| |
| |
| |
| | |
Got added in 5336e1838a95d97.
|
| |
| |
| |
| | |
Reviewed-by: Christiaan Janssen
|
| |
| |
| |
| |
| |
| |
| | |
Move socket handling code out of QDeclarativeDebugServer into a
QDeclarativeDebugServer(Tcp)Connection class.
Reviewed-by: Christiaan Janssen
|
| |
| |
| |
| |
| | |
Move QDeclarativeDebugServer class into it's own files and make the classes
less interdependent.
|
| |
| |
| |
| |
| |
| |
| | |
'client' points to the QDeclarativeDebugConnection object, so better
name it 'connection' then.
Reviewed-by: Christiaan Janssen
|
|\ \
| |/ |
|
| | |
|
| |
| |
| |
| | |
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Tracing for compile time, signal handlers, and deferred
creation.
|
| | |
|
|/ |
|
|
|
|
|
| |
Reviewed-by: Martin Jones
Task-number: QTBUG-13762
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Enable the remote debugging of QDeclarativeEngines only after
QDeclarativeDebugHelper::enableDebugging()
has been called.
Approved by 4.7 Program Team.
Reviewed-by: Alessandro Portale
Task-number: QTBUG-13762
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The qml debugging enabler in QtDeclarative made any Qt app crash
which used QDeclarative. Reason was that QtDeclarative.dll tried
to directly access (private) writable static data from QtGui.dll.
This patch adds an accessor function for the data to QtGui, and
the crash is gone.
Done-by: Kai Koehne
Reviewed-by: Kai Koehne
Conflicts:
src/declarative/debugger/qdeclarativedebugservice.cpp
|
|
|
|
|
| |
Allow QML debug clients to be installed between the connection being
established and the hello message being received.
|
|
|
|
|
| |
Task-number: QTBUG-14041
Reviewed-by: Aaron Kennedy
|
| |
|
|
|
|
|
|
|
| |
Always flush sockets after sending data, and make autotests more robust
by using busy wait.
Reviewed-by: Christiaan Janssen
|
|
|
|
|
|
|
|
|
| |
When statusChanged() is called during handsake state() was not the same
as the argument passed. Fix this by setting gotHello = true _before_
notifying the clients.
Reviewed-by: Christiaan Janssen
Task-number: QTBUG-14087
|
| |
|
|
|
|
| |
Reviewed-by: Christiaan Janssen
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The protocol so far was client->server only. That is, there was no
sane way for a client to check whether a plugin on the server (service)
was available or not. E.g. calling Client::setEnabled(true) 'succeeded',
without a check whether there is actually a service to talk to.
The new protocol replaces this shortcoming by a service discovery
mechanism: Both client & service announce their available plugins at
handshake time, and later on if there are changes. The status is
reflected in Client::status() and Service::Status() , which are either
NotConnected - no network connection, or not registered properly
Unavailable - TCP/IP connection works, but no plugin with the same
name on the other side
Enabled - You can connect to plugin on other side
The status changes happen automatically (no setEnabled() anymore).
Furthermore a version ID was added to the handshake, so that we can
extend the protocol further in the future :)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Add a semi-private API to get QScriptEngine for a QDeclarativeEngine. So far the qmljsdebugger lib in QtCreator
accessed the script engine via QDeclarativeEnginePrivate. Replace this by a minimal API that is still in a
private header, where we nevertheless can make some BC checks/guarantees.
Aaron Kennedy agreed with the idea.
Task-number: QTCREATORBUG-2179
|
|
|
|
|
|
|
|
|
|
| |
Add a semi-private API to get QScriptEngine for a QDeclarativeEngine. So far the qmljsdebugger lib in QtCreator
accessed the script engine via QDeclarativeEnginePrivate. Replace this by a minimal API that is still in a
private header, where we nevertheless can make some BC checks/guarantees.
Aaron Kennedy agreed with the idea.
Task-number: QTCREATORBUG-2179
|
|
|
|
|
|
|
|
|
|
| |
The environment variables do not work for Symbian devices, so
without this change, QML debugging cannot be done on them.
In addition, configure now contains an option to disable qml
debugging entirely, due to it being a major security risk.
Reviewed-by: kkoehne
|
|
|
|
|
|
|
| |
Without this, QML Inspector in Qt Creator gets no error message for
failed connections, which can lead to confusion.
Reviewed-by: ogoffart
|
|
|
|
| |
Reviewed-by: Lasse Holmstedt
|
|
|
|
|
|
|
|
|
| |
object.
Streaming all the properties is too slow, and we do not need them
in the debugger of creator.
Reviewed-by: Lasse Holmstedt
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Else, we can have deadlock in the javascript debugger, which may
start an event loop.
If the javascript execution result from some network command, the
further network command are not processed more
(the ones that exist the javascript debugger event loop)
Having a QueuedConnection there means the network events will not
be blocked by a rentrency in the event loop
Reviewed-by: Lasse Holmstedt
|
|
|
|
| |
QTBUG-11938 and QTBUG-10801
|
|
|
|
|
|
|
|
| |
CanvasFrameRate
This silents a lot of warnings in creator.
Reviewed-by: Aaron Kennedy
|
|
|
|
| |
Reviewed-by: Aaron Kennedy
|
|
|
|
| |
QTBUG-11933
|
|
|
|
|
|
|
| |
The new message currently enables resetting bindings, literal values and
signal handlers (onX: {...}) through the debugger.
Reviewed-by: Roberto Raggi
|