| Summary: | Plasma script can't move panel to another screen | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | puggan <from_kde> |
| Component: | Panel | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | justin.zobel, kde, pmdumuid |
| Priority: | NOR | ||
| Version: | 5.5.1 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| URL: | http://superuser.com/questions/1081120/how-do-i-move-a-kde-plasma-panel-from-commandline-scripts | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Q_PROPERTY(int screen READ screen) is read only. *** Bug 367981 has been marked as a duplicate of this bug. *** If this is the resolution, can the documentation, at https://userbase.kde.org/KDE_System_Administration/PlasmaDesktopScripting#Activities_and_Panels please be updated so that "screen" be moved out of the dot pointed list prefixed with "as well as the following read/write properties:" and into the list above it starting with the sentence "Activity and Panel objects, once created by the script, or as returned by activityById, activityForScreen, or panelById) provide the following read-only properties:" .. I'd suggest that "version" is probably supposed to be "read-only" as well and should also be moved to the list above it. David is this still relevant? If so and the "Q_PROPERTY(int screen READ screen)" is still a read-only variable can we please have this documented as requested. 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! 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! |
after running `panel.screen=0;` the panel.screen is still 2. Reproducible: Always Steps to Reproduce: 1. Have multiple screens connected. 2. starta a plasma-console: `qdbus org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.showInteractiveConsole` Run the script: var panel = panelById(panelIds[0]); print('before, panel.screen: '); print(panel.screen); panel.screen=0; //panel.location='top'; panel.location='bottom'; print('after, panel.screen: '); print(panel.screen); Actual Results: Executing script at fredag 27 maj 2016 kl. 14:20:30 CEST before, panel.screen: 2 after, panel.screen: 2 Runtime: 1ms Expected Results: Executing script at fredag 27 maj 2016 kl. 14:20:30 CEST before, panel.screen: 2 after, panel.screen: 0 Runtime: 1ms I can move the panel using mouse, and the panel.screen ends up as 0, 1 or 2. I can move the panel to another edge on the same screen (top, bottom). The most annoying is when i move the laptop, to somewhere where i don't have 3 screens, and it stays on the 3th screen. May be related to 362910 and 356225, but this problems also accures when all screens are connected, and the panel is visible.