Bug 244214 - desktop grid - clicking on empty region could switch to a different activity
Summary: desktop grid - clicking on empty region could switch to a different activity
Status: RESOLVED DUPLICATE of bug 242555
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-11 13:18 UTC by FiNeX
Modified: 2010-07-11 13:44 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
example of grid using activities (427.68 KB, image/jpeg)
2010-07-11 13:24 UTC, FiNeX
Details

Note You need to log in before you can comment on or make changes to this bug.
Description FiNeX 2010-07-11 13:18:02 UTC
Version:           unspecified (using Devel) 
OS:                Linux

The desktop grid effect doesn't display windows if not in the current activity (correct), but when you click on an area which could contain a window from another activity, it switch to that application.

Reproducible: Always

Steps to Reproduce:
Tested on 4.5 RC2 - Steps to reproduce:


1) add a second activity
2) open some apps (call them A and B) in the same virtual desktop.
3) set A to be displayed on the first activity and B on the second
4) activate the desktop grid on the first activity

-> you will see all the apps (A) from the current activity

5) click on an empty space (which could contain the B app if you would have activated the grid on the second activity)

Actual Results:  
you will switch to the second activity

Expected Results:  
The correct result should be to doesn't consider application on other activities at all

Sorry for the big screnshot, I'm using a dual monitor setup.
Comment 1 FiNeX 2010-07-11 13:24:01 UTC
Created attachment 48777 [details]
example of grid using activities
Comment 2 Martin Flöser 2010-07-11 13:44:15 UTC
marking as duplicate of the same issue for Present Windows

*** This bug has been marked as a duplicate of bug 242555 ***