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

no viewer update while typing #100

Closed
BsNoSi opened this issue Dec 22, 2013 · 2 comments
Closed

no viewer update while typing #100

BsNoSi opened this issue Dec 22, 2013 · 2 comments
Assignees
Milestone

Comments

@BsNoSi
Copy link

BsNoSi commented Dec 22, 2013

In a longer document editing (starts >2500 words) gets time consuming and obstruct writing, because of the preview update process ( I think this is the reason).

It would be quite helpful, if CuteMarkEd does not update the view while I am typing and stops updating immediately, when I start typing. There should be a configurable delay for viewer update after the last key strike, for customizing it to my individual timing between each keystroke.

@cloose
Copy link
Owner

cloose commented Dec 22, 2013

There is already a delay of 100 ms in the HTML generation to wait if the user is typing more text.

I would like to prevent options that are hard to understand for the user. So I'm thinking about calculating this delay dynamically based on the size of the document with some upper limit (maybe 1 second?).

@ghost ghost assigned cloose Dec 22, 2013
@BsNoSi
Copy link
Author

BsNoSi commented Dec 22, 2013

Currently I have the effect, that it is somehow chewy start typing. It seams to me, that especially after scrolling through the edit window, that it takes some extra moments to switch between scroll/view and edit. I think that's a hindrance.

To increase my working speed, it might be a alternative solution, switching off the preview, simply having the edit window. While typing much text, I do not check the preview continuously, I will/must concentrate to the content. The flickering preview on the right hand sometimes let me flee from CuteMarkEd to use a standard text editor for preparation.

If CuteMarkEd would recognize chances of the saved document from some other applications, this might be a solution, too. But not so nice, is it?

cloose added a commit that referenced this issue Jan 13, 2014
Calculate the delay of the HTML processing based on the
number of characters in the markdown document instead of
a hardcode value of 100 ms.
cloose added a commit that referenced this issue Jan 13, 2014
Do not update the web view when it is not visible.
@cloose cloose closed this as completed Jan 13, 2014
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