Bug 317928 - Desktops signals in workspace are not triggered...
Summary: Desktops signals in workspace are not triggered...
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: scripting (other bugs)
Version First Reported In: 4.10.2
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-06 14:24 UTC by Michail Vourlakos
Modified: 2021-12-04 04:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michail Vourlakos 2013-04-06 14:24:22 UTC
I use the following code in a kwin script:

    property int currentDesktop: workspace.currentDesktop
    property int numberOfDesktops: workspace.desktops

but both currentDesktop and numberOfDesktops are not update when they are changed from Plasma e.g. from the Pager. The issue is I think that the following signals are not triggered in kwin scripting:
onCurrentDesktopChanged
onNumberOfDesktopsChanged

Reproducible: Always
Comment 1 Martin Flöser 2013-04-06 14:52:05 UTC
please try again with master - Virtual desktop has been refactored.
Comment 2 Michail Vourlakos 2013-04-06 16:35:46 UTC
Tried in master the following:
////////
    property int currentDesktop: workspace.currentDesktop
    property int numberOfDesktops: workspace.desktops

    onCurrentDesktopChanged: console.log(workspace.currentDesktop);
    onNumberOfDesktopsChanged: console.log(workspace.desktops);
////////////////
in order to debug, no change.....

adding desktop from pager or activating a desktop from pager doesnot trigger any changes in this above....
Comment 3 Andrew Crouthamel 2018-11-10 03:23:48 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-21 04:42:41 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 kde.org 2021-11-04 22:51:35 UTC
This bug report is quite old. Can you still reproduce this issue with KDE 5.23?
Comment 6 Bug Janitor Service 2021-11-19 04:38:44 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2021-12-04 04:38:33 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!