What everyone has to realize is that the buttons in Code View are not the same thing as the buttons in Book View--merely disabled.
The functionality of the buttons in Book View are routines that are provided by Qt. It does all the lifting. The same buttons in Code View are routines that we have to manage to accommodate similar functionality. Except that in Code View, me have to make sure it can be accomplished without polluting the code with inline styles or butchering something else.
When in Code View, we are always running under the assumption that the user wants full control over what code is created. Some of the simpler buttons that can't "screw things up" are still enabled in Code View, but that's about it.
If you need/prefer a lot of automated code generation assistance with your HTML editing, consider setting up some clips, or using the Open With feature of Sigil (right-click on files in the Book Browser) and using a full-featured HTML editor of your choice to do your editing.
Quote:
Originally Posted by carmenchu
2. By the way, I also miss an icon for Preview: of course, F12 does the trick, but when just editing, I am rather a mouse-fiend.
Thanks!
|
View->Preview is, of course, two clicks. But it will keep you away from needing to use the keyboard. To be honest, I never hide Preview anyway. I tab it together with the ToC widget. It's never more than one mouse-click away that way. None of Sigil's dockable Widgets have icons, by the way.