Bug 132759 - Allow to scroll beyond image borders
Summary: Allow to scroll beyond image borders
Status: RESOLVED DUPLICATE of bug 189541
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
: 196176 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-08-21 21:23 UTC by Thomas Zander
Modified: 2010-07-14 08:37 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Zander 2006-08-21 21:23:37 UTC
Version:           1.5.90 (1.6 Alpha 1) (using KDE 3.5.3, compiled sources)
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.17.6pavilion

In a discussion on IRC someone (Heikki Ulmanen) came with the suggestion that its often usefull to start a brush-stroke just outside of the canvas and move the brush into the canvas with the right pressure etc.
In order to do that you would always need some space between the canvas and the rulers, which is normally not available at lower zoomlevels.

The suggestion is to make the scrollable area a bit bigger than the canvas so the user can move the scrollbars and get the requested 'blank' space.

I suggest (using XDPI) to supply 2cm on each canvas edge as an 'expansion' area.
Comment 1 Bart Coppens 2006-08-21 22:09:30 UTC
SVN commit 575636 by coppens:

Due to popular request: allow freehand painting strokes to start outside the image area. This would be especially handy together with wishlist item 132759

CCBUG:130481
CCBUG:132759

 M  +4 -2      kis_tool_freehand.cc  


--- branches/koffice/1.6/koffice/krita/ui/kis_tool_freehand.cc #575635:575636
@@ -81,9 +81,11 @@
 
     if (e->button() == QMouseEvent::LeftButton) {
         
+        // People complain that they can't start brush strokes outside of the image boundaries.
+        // This makes sense, especially when combined with BUG:132759, so commenting out the
+        // next line makes sense.
+        //if (!m_currentImage->bounds().contains(e->pos().floorQPoint())) return;
         
-        if (!m_currentImage->bounds().contains(e->pos().floorQPoint())) return;
-        
         initPaint(e);
         paintAt(e->pos(), e->pressure(), e->xTilt(), e->yTilt());
 
Comment 2 Halla Rempt 2006-12-07 10:54:48 UTC
I still have a bug here: when I do that with the tablet stylus, krita gets confused and thinks the mouse is the stylus and the stylus the mouse and neither can paint anymore -- until I restart my X11 session.
Comment 3 Sven Langkamp 2009-06-12 21:31:38 UTC
*** Bug 196176 has been marked as a duplicate of this bug. ***
Comment 4 Halla Rempt 2010-07-14 08:37:36 UTC

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