Positioning font work slightly jumpy
Steps to Reproduce:
1. Open the attached file
2. Drag the fontwork on the second page slightly up where the K slightly below the top page border. It will jump to the previous page.
3. Now drag Fontwork down, where F of font hits the border (nothing happens)
Inconsistent behavior. Dragging down to page bottom is no issue. There is even resistance preventing to go further down (moving the next page) Dragging up to top of the page and it instantaneously snaps to the previous page
Slightly more resistance
User Profile Reset: No
Version: 184.108.40.206.alpha0+ (x64)
Build ID: 7ae9c9572ccac55c0926b8a9779bb63c4236291c
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win;
Locale: nl-NL (nl_NL); UI-Language: en-US
Created attachment 159132 [details]
I can't confirm with
Version: 220.127.116.11.alpha0+ (x64)
Build ID: 1c9ced04189c9d23ffea05d5570960b54b05ef28
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win;
Locale: de-DE (de_DE); UI-Language: en-GB
Created attachment 159172 [details]
Screencast made it more clear to me, thanks. Fontwork jumps to second page, if the whole fontwork is on second page. Or more general: Fontwork jumps to the next/previous page, if anchor jumps to the next/previous page. I don't want to assess, if this is a bug or not. So what is the expected or desired behaviour?
(In reply to Dieter from comment #4)
> Screencast made it more clear to me, thanks. Fontwork jumps to second page,
> if the whole fontwork is on second page. Or more general: Fontwork jumps to
> the next/previous page, if anchor jumps to the next/previous page. I don't
> want to assess, if this is a bug or not. So what is the expected or desired
If it where up to me.. more 'resistance' before the anchor is moved to previous page. Similar as the other way around
(In reply to Telesto from comment #5)
> If it where up to me.. more 'resistance' before the anchor is moved to
> previous page. Similar as the other way around
Same behaviour with images and shapes. So it's a broader issue. I would also expect, that behaviour is the same in both directions. I've changed bug summary a bit, to make the problem more clear
cc: Design-Team for further input and decision.
I vaguely remember to had this before. Let's just define the desirable behavior:
* moving the object up to 1/3 of the object out of the page boundaries makes it jump to the top or bottom respectively
* moving the object further makes it jump to the bottom of the previous page or the top of the next page
This behavior would be independent from the anchoring type, which remains on moving beyond page boundaries.
Is that what you would expect, Telesto?
Looked again into the example document and cannot see anything suspicious. The rightmost ascender of the k quickly moves out of page so the anchor switches to the previous page. Moving the object down from there requires as much space on top as needed previously - in other words you move a a few pixel but down the whole image to not overrun the upper border. => NAB