Hello
Its probably obvious... and just thought I would ask....
When opening several html files in the CoffeeCup HTML Editor, and scrolling to someplace in one of them, then switching between the open document tabs along the bottom of the editor screen to view another file... CoffeeCup HTML Editor loses the previously viewed files displayed page position.
Meaning that, upon returning to previously scrolled and viewed documents, the files window 'always' opens at the top of the html page, meaning the page has to be scrolled again to get to where I was....
Coffee Cup HTML Editor doesn't seem lock on to the page position 'view' unless I edit the page....
Would it be possible to enable the HTML editor to always display an html page at the 'latest' view..., irrespective of whether or not editing took place...
I know this is a very small thing in the scheme of what you are all doing, but when having many files open, it can a lengthy process switching pages and scrolling back to the previous page location..
The HTML Editor is a great program and I just thought I would ask
Thankyou
Peter
Page Scrolling, 'view' not locked...
I find that if I just position the cursor where I want to return, before I go to a different document, then the view is remembered. I don't need to edit anything, just position the cursor by clicking in the text somewhere.
Per
www.mingas.com
www.mingas.com
I'm not seeing this problem (unless I'm misunderstanding the problem) on the BETA version in works now. So, hopefully it will be a short lived problem for ya.
Until the release, Per's idea should be a quick work-around.

Living the dream, stocking the cream

Thankyou for your replies, Yes I know about the cursor and clicking on the page,
just........... I forget to do that sometimes...
If its fixed in a latest beta version, then WooHoo, THAT really is good to know
Thanks for the heads up, I shall keep watching for the new release.
Only a small issue I guess, but a neat one nonetheless
Regards
Peter
just........... I forget to do that sometimes...
If its fixed in a latest beta version, then WooHoo, THAT really is good to know

Thanks for the heads up, I shall keep watching for the new release.
Only a small issue I guess, but a neat one nonetheless
Regards
Peter
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.