Hi,
I noticed that in the preview mode WB (2011) returns to the top of the page every time the switch is made from Code Editor to Preview. Even if nothing is changed in the code. That is very awkward. I'm actually using another code editor if I have to write lengthy texts. I know that I can use the split function where the page position is retained, but I don't like working that way because the views get too small.
Therefore the request to make WB remember its preview page position, if possible.
Page position memory in preview mode
Moderator: kfury77
Forum rules
Please follow these guidelines when posting feature requests. This will help to increase the value of your contribution.
Please follow these guidelines when posting feature requests. This will help to increase the value of your contribution.
- Do not create new topics for already requested features. Add your comments to the existing feature request topics instead;
- Create separate topic for each feature suggestion. Do NOT post a number of non-related feature suggestions in a single topic;
- Give your topic a meaningful title. Do NOT create topics with meaningless titles, such as "My Suggestion" or "My Problem".
Page position memory in preview mode
Last edited by FrankC on Mon Sep 05, 2011 1:04 pm, edited 1 time in total.
Re: Page position memory in preview mode
Hi!
I wonder if the new feature added in version 2011 "cursor-preview synchronization" solves this problem at least partially for you?
I wonder if the new feature added in version 2011 "cursor-preview synchronization" solves this problem at least partially for you?
Kind regards,
Gatis Avots
Gatis Avots
Re: Page position memory in preview mode
I'm afraid not, Gatis. That only solves the problem of the disappearing cursor/caret upon return to the Code Editor pane. Which would have been another Feature Request, but now that that is solved in IE preview I will let it be for the time being.
I think that the page position memory in the preview mode should be at the top of your to-do list. Like I said, I now have to use a different code editor (with internal preview) if I'm creating a page that is substantially longer than the preview window, which happens very frequently. Especially if it is much longer, I just cannot work with WB anymore -- it's too awkward to have to scroll down every time to see the result.
I think that the page position memory in the preview mode should be at the top of your to-do list. Like I said, I now have to use a different code editor (with internal preview) if I'm creating a page that is substantially longer than the preview window, which happens very frequently. Especially if it is much longer, I just cannot work with WB anymore -- it's too awkward to have to scroll down every time to see the result.