Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SetColumnsWidth (or SetRowsHeight) vs Frozen #313

Closed
LamerDrv opened this issue Mar 1, 2020 · 2 comments
Closed

SetColumnsWidth (or SetRowsHeight) vs Frozen #313

LamerDrv opened this issue Mar 1, 2020 · 2 comments

Comments

@LamerDrv
Copy link

LamerDrv commented Mar 1, 2020

Hi. When grid has frozen rows or frozen columns then SetColumnsWidth or SetRowsHeight scrolls grid to start position despite the focused cell.

Steps to reproduce the behavior:
This behavior can be seen in demo project.

  1. Start "ReoGrid Demo"
  2. Go to "Top" subsection in "Freeze to Edges" section (in tree on left side)
  3. scroll grid down and focus cell (for example focus cell "G60")
  4. change width any column or height any row
  5. grid auto-scroll to start and current cell is out of visible area (but scroll bars position stay corectly)

Expected behavior
Current cell stay in visible area

may be same as #172

@LamerDrv
Copy link
Author

LamerDrv commented Mar 1, 2020

I had tried to track down the issue. And I had come to this fragment inside ViewControl.cs:

85: if (this.IsFrozen)
86: {
87:   this.FreezeToCell(this.FreezePos, this.FreezeArea);
88: }

I had tried comment out line 87 (just to see what will happen) - and get expected behavior.
I understand that solution can't be so easy :)))) (most certainly removing this string will lead to negative consequences). But I hope this info helps.

@jingwood
Copy link
Member

jingwood commented Mar 6, 2020

duplicate of #151

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants