aboutsummaryrefslogtreecommitdiffstats
path: root/src/plugins/qmlprofiler/qmlprofilersettings.h
Commit message (Collapse)AuthorAgeFilesLines
* ProjectExplorer: Remove direct runconfig dependency from ISettingsAspecthjk2018-09-111-2/+1
| | | | | Change-Id: I5d8a6a31f6bf97c34163b64b8d37f9ea070717ba Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
* QmlProfiler: Use override consistentlyTobias Hunger2018-05-071-3/+3
| | | | | | | clang-tidy fixes from modernize-use-override check. Change-Id: Ide82798f95e07be6c842a1c2fcf28573d9c635ed Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
* ProjectExplorer: Keep RunConfiguration in ISettingsAspectUlf Hermann2018-04-271-2/+1
| | | | | | | | | | | | | Any SettingsAspect that doesn't refer to the global settings has a specific RunConfiguration it is about. This can be very handy to know when constructing the actual settings. Right now there is no way to find out about it. Drop the clone() and create() methods. They weren't used anywhere and a proper implementation should take care of the runConfiguration member. Change-Id: Ie505a9b19707f8a1b6bf9cae73513cd3c30d0bca Reviewed-by: hjk <hjk@qt.io>
* Wholesale conversion to #pragma oncehjk2016-03-301-4/+1
| | | | | | | Kudos to cgmb and https://github.com/cgmb/guardonce Change-Id: Ifa8970734b8d43fd08c9260c645bdb0228633791 Reviewed-by: Tobias Hunger <tobias.hunger@theqtcompany.com>
* Update License according to agreement with Free Qt FoundationTobias Hunger2016-01-191-17/+12
| | | | | | | * Update files in src/plugins Change-Id: Ia5d77fad7d19d4bb3498e78661982f68729adb22 Reviewed-by: Tobias Hunger <tobias.hunger@theqtcompany.com>
* QmlProfiler: allow for multiple sequential traces to be aggregatedUlf Hermann2015-11-191-0/+4
| | | | | | Task-number: QTCREATORBUG-13317 Change-Id: Ic7d1d5c94d8d522741b6c4207a21a43f521da5fb Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>
* QmlProfiler: Persist the last trace file loaded or savedUlf Hermann2015-09-151-0/+4
| | | | | | | This is quite handy if you keep all your traces in one directory. Change-Id: I09842404493c02fb0ca9c4a328950f7b6dcb5be0 Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>
* QmlProfiler: Expose flush interval to userUlf Hermann2015-08-311-0/+70
Flushing data while the application is running can distort the results because the flushing itself takes time. However, not flushing leads to longer load times in the end and higher memory usage. The best strategy depends on the application being analyzed and the users should decide if they want to flush or not. The settings infrastructure also paves the way for preserviing the layout of the timeline and statistics views as well as the category filters across sessions. Change-Id: I2cdc37c7fc7eb9b05b6870955ddffaa712d6c956 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com> Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>