| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This takes care of many common 2D and 3D use cases, and probably other
scenarios with QObjects too:
- root can be any QObject
- different shapes for Items, Handlers, 3D objects, QAIM and
DeliveryAgents
- shows objectName, text/label/title
- shape (outline) color can correspond to item (fill) color if desired
- several new working examples
Change-Id: Ica9a312ee6ad7e49c872ea52e6e8ab03fc41bc63
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| |
|
|
|
|
|
|
|
| |
The plan is to add more code to generate other types of UML diagrams.
They can probably all be in the same module, because you anyway need to
instantiate MessageTrace or something else to instrument the application.
Change-Id: I602dea7fdfce57b5e1f05c9a43c25d5eb73f0a5d
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| |
|
|
|
|
|
|
| |
...and use that by default. QML can be obtained by setting the new
MessageTrace.outputFormat property.
Change-Id: I9a8a8caa8ed2c993c8681bfd50be74f1ec99738c
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
|
|
A utility to be instantiated in the application-under-test, which will
install itself as the message handler, parse the output of the requested
logging categories for tracing, and generate a message trace in QML.
Change-Id: I3961c27d00ecead5a1204cb2f6928af4f9da26aa
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
