Martin Gräßlin 7073b0af40 Export workspace as global property on ScriptEngine in QML bindings ... If workspace is exported as a context property there seem to be issues with the signals which are not bound to a property of WorkspaceWrapper. This problems seems to be fixable by exporting the workspace property as a global property on the script engine. As a side-effect this also resolves the issue with the clientList, so we can drop the hack again. REVIEW: 104682		2012-04-21 15:34:37 +02:00
..
documentation-global.xml	Documentation for global JavaScript methods/properties	2012-04-10 20:41:57 +02:00
kwinscript.desktop	SVN_SILENT made messages (.desktop file)	2012-04-02 10:09:26 +02:00
meta.cpp	Unexport TabGroup property on Client for scripts	2012-04-21 12:19:52 +02:00
meta.h	fix tabbing	2012-02-11 16:30:22 +01:00
scriptedeffect.cpp	Global Shortcut support for KWin scripts and scripted Effects	2012-03-30 08:20:10 +02:00
scriptedeffect.h	Global Shortcut support for KWin scripts and scripted Effects	2012-03-30 08:20:10 +02:00
scripting.cpp	Export workspace as global property on ScriptEngine in QML bindings	2012-04-21 15:34:37 +02:00
scripting.h	Global Shortcut support for KWin scripts and scripted Effects	2012-03-30 08:20:10 +02:00
scriptingutils.h	Global Shortcut support for KWin scripts and scripted Effects	2012-03-30 08:20:10 +02:00
timer.cpp	Simplify the Timer in scripting	2012-01-22 13:02:34 +01:00
workspace_wrapper.cpp	Export workspace as global property on ScriptEngine in QML bindings	2012-04-21 15:34:37 +02:00
workspace_wrapper.h	Export workspace as global property on ScriptEngine in QML bindings	2012-04-21 15:34:37 +02:00