Bug 276320 - Widget ends in-between screens on dual monitor setup
Summary: Widget ends in-between screens on dual monitor setup
Status: RESOLVED DUPLICATE of bug 183660
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-notes (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-23 12:36 UTC by King_DuckZ
Modified: 2011-12-17 10:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description King_DuckZ 2011-06-23 12:36:03 UTC
Version:           unspecified (using KDE 4.5.5) 
OS:                Linux

If you drag the notes plasmoid from one screen to the other, the part going outside of the screen just disappears instead of appearing on the other screen. Then once the cursor gets to the other screen, the plasmoid is automatically dropped:
* with its left border aligned to the left side of the screen when the cursor went to the right screen
* almost completely out of the screen, on its right side, when the cursor went to the left screen

The actual behaviour of icon plasmoid seems to be correct, and that's what I would expect.

Reproducible: Always

Steps to Reproduce:
* Put a notes plasmoid on a dual desktop configuration (I'm using dual setup with ATI drivers)
* Drag the plasmoid from one screen to the other

Actual Results:  
When the cursor gets to the other screen the plasmoid is automatically dropped in what seems to be a clamped position, depending on whether you were moving it from left screen to right screen or vice-versa.

Expected Results:  
The plasmoid smoothly crosses the "border" between the two screens, being visible on both them when it's in the middle.
The plasmoid can eventually be dropped and left between screens.
The plasmoid is not dropped automatically when the cursor goes from one screen to the other.
Comment 1 Reza 2011-12-17 10:54:08 UTC

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