Quote:
Originally Posted by Turtle91
The current (pre- RC) takes you to the top of the xhtml page corresponding to the line which you double click on. It has been that way for as long as I can remember.
The request, Post #46 in the Suggestions for Sigil Improvements thread, and your reply in post #48 mentioned:
and your reply:
ctrl-clicking on the class name in an xhtml will take you to the css location (if it is linked and it can find it) on the stylesheet.
double-clicking on the Classes Used takes you to the top of the xhtml page referenced on the line you click on.
I use this functionality all the time when I am cleaning up classes with nonsense names. When I find a class that is a simple style (eg. italic, or bold) then using find/replace is usually the best answer. However, if there are more complex classes - especially when used relative to surrounding classes - then I like to see how the style is presented by going to the actual xhtml page. So the above request to go to the first occurrence of the class on the xhtml xhtml page makes more sense.
I do like the idea of being able to go directly to the css occurrence, so using ctrl-click on the Classes Used page would be consistent with that functionality when used in the coding view. Perhaps using right-click on the class name to highlight the name (or automatically place it in the Find field) would be helpful as well. |
If you look at my reply you quoted:
Quote:
|
3. You can already right click in a class in the editor and Sigil will take you directly to it in the css. I will look into allowing the Classes Used Report to do the same.
|
I said I would make the Classes Used double-click take you to the directly to it IN THE CSS (emphasis mine). And that is what I did.
So you are saying they wanted to instead go to the first occurrence of that class being used in just one of the files it was found in?
If so that was very unclear and no one complained throughout the entire Beta series.
It is a little late to change that now especially given I am still unsure that isn't what they asked for.
All of this is done using the table's built-in double-click event handler. There are no event handlers for ctrl click, built into that class.
Let me see, what it would take to make it find the first use of the class on that page.