Bug SS-3500
1 vote
vote

Simple Drag of regions adds spurious offset to target position in margin preview mode
Created by Martin Kraska on 2/16/2018 5:23 PM Last Updated by Martin Kraska on 2/16/2018 8:14 PM
%
 (hrs)
Logged: 0   (hrs)

 Description

SMath Studio: SMath Studio Desktop 0.99.6611.22150, portable, x64
OS: Microsoft Windows NT 6.1.7601 Service Pack 1 (Windows 7 Professional Service Pack 1, x64)
Screen: 1920x1080 px, 96x96 dpi, 96 GP.DPI, 1 GP.SRF
Localization: separator=<semicolon>; decimal symbol=<comma>; system decimal symbol=<comma>; language=GER
Frameworks: CLR 4.0.30319.42000

    installed versions:
    v2.0.50727    2.0.50727.5420 SP2
    v3.0    3.0.30729.5420 SP2
    v3.5    3.5.30729.5420 SP1
    v4    
        Client    4.7.02053
        Full    4.7.02053
    v4.0    
        Client    4.0.0.0

 

Similar to https://smath.info/bts/Issues/IssueDetail.aspx?id=3495

but for simple drag (move, not clone), regardless whether a blue highlight region is dragged or the frame of a region with focus is dragged.

 

I mark a region in blue and pick it for dragging

Then I drag it to the previous page (the blue frame indicates the landing position)

Actual landing happens above the first page of the document
Skip Navigation Links

    Martin Kraska (Friday, February 16, 2018 8:14 PM) #

I understand you want the user to work with page layout view because this more eagerly reveals bugs. I am fine with that but would not recommend that to non-die-hard  users.

To add to your list of progress: Now font scaling and zooming have stabilized a lot. This was nearly unusable some time ago, such that I had to set the classroom rule "hands off font size settings". However I still vote for not touching font settings till the day where we will have section titles and similar templates.

I am also very happy with italic font having migrated from units to variable names.

Take care!

 

    smath (Friday, February 16, 2018 7:53 PM) #

Thank you, Martin.

The thing is that Pages layout technically is a primary one - classic layout is fully based on it. Classic layout is a Pages layout where all margins and spaces between pages are equal to zero. It is how I have implemented it in code. Currently while I'm working on Pages layout I have found and fixed plenty of bugs in Classic one and even this work is not completed yet.

I need to continue use new Pages layout by default in stable releases because this is the only way to make it as ideal as we want. I need to know everything about all bugs we have in this and all other features as it allows me to be fast in polishing them.

To say truth I'm very excited about tomorrows release as I have fixed all that I planned and even more! Currently I have only two observations related to worksheet layout which is most likely will be a part of the release, but two known issues is actually a very good progress!

Overall performance, stability and number of features are growing from one release to another and this became possible only because a code of SMath Studio is prepared enough to start working on new features. Things like Pages view, renged indexes, unicode in names, equations breaking were absolutely impossible 1-3 years ago. I wanted to implement them but all my attemps failed because of complexity.

Bugs... yeah we always have bugs in the software. It is a life ;)

>I am looking forward to the announced native plot region with ranges control ;-)

Ah yes, almost forgot about it. Will see...

    Martin Kraska (Friday, February 16, 2018 7:32 PM) #

Take the time you need and set priorities to your needs. I am fine with classic mode for now.

However, I'd switch off page layout mode by default if the feature is still experimental. Whenever a document has more than one page, users might be tempted to adjust page break. Thus it is not that far-fetched...

As to stable releases: I am looking forward to the announced native plot region with ranges control ;-)

    smath (Friday, February 16, 2018 7:13 PM) #

Spent some time on it but it looks like this issue is too complex to handle it in 1 day before stable release.

I believe it is not high priority one as it happens only if:

  1. Page layout mode is turned on;
  2. More then 1 page is displayed;
  3. User does move or copy (by Ctrl+drag) of Regions between pages.

And even if all these requirements are followed but height of the page is large enough user will just see that Region appered with a little verticall offset and this will not make a problem.

    smath (Friday, February 16, 2018 6:21 PM) #

Thank you! Issue is reproduced.