- AuthorPosts
- June 5, 2009 at 11:10 pm #7363blades018Member
I was directed to the alpha version because I wanted to use the outline plugin and not have commented lines collapsible.
Link
It seems like when you have two commented lines together it still gets collapsed. sample code below.
________________
begin// begin
// beginend
________________Thanks
June 6, 2009 at 9:25 pm #7364Yutaka EmuraKeymasterblades018 wrote:
I was directed to the alpha version because I wanted to use the outline plugin and not have commented lines collapsible.Link
It seems like when you have two commented lines together it still gets collapsed. sample code below.
________________
begin// begin
// beginend
________________Thanks
OK. I completely misunderstood your request. Can you please describe exactly what you want EmEditor to do?
June 7, 2009 at 3:10 pm #7365blades018MemberSorry for being unclear. I need to write my own custom outline for the plugin. A very simple case would be Level 1 “begin” and Level 2 “end”. Commented lines should not be collapsed. Using the simple code in the previous thread, the first commented line is still being collapsed.
June 19, 2009 at 1:17 pm #7416blades018MemberDoes this make sense now?
June 19, 2009 at 2:42 pm #7417Yutaka EmuraKeymasterblades018 wrote:
Does this make sense now?It makes sense now, but the current design doesn’t allow a portion of collapsed range to appear. So, it isn’t possible to show only commented lines while all the outside block collapsed.
June 28, 2009 at 12:38 am #7433blades018Memberwe are not on the same page. what i mean is that there should not be a plus/minus on commented lines.
if you throw this code in the editor, it should all make sense
// ##############
begin // there is a minus here, which is correct// begin (there is a minus here, but there shouldn’t be. it is the result of the following line of code)
// beginend
// ##############June 28, 2009 at 5:27 am #7435Yutaka EmuraKeymasterblades018 wrote:
we are not on the same page. what i mean is that there should not be a plus/minus on commented lines.if you throw this code in the editor, it should all make sense
// ##############
begin // there is a minus here, which is correct// begin (there is a minus here, but there shouldn’t be. it is the result of the following line of code)
// beginend
// ##############In the latest version of v9 alpha, you might want to uncheck “Make Comments Collapsible” text box in the Outlint properties. I hope this helps.
June 28, 2009 at 2:39 pm #7436blades018MemberI can see you failed to throw that portion of code in to the editor and play around with it. This is a fairly obvious bug.
Throw away everything from the previous posts.
lets try this again…
scenario 1
//##############
begin // minus here, which is correct// begin (no minus here, which is correct)
end
//##############scenario 2
//##############
begin // minus here, which is correct// begin (a minus now appears because of the comment in the following line of code, incorrect)
// stuffend
//##############on a side note, it seems like you inverted the “Make Comments Collapsible” check box
June 30, 2009 at 4:19 am #7437Yutaka EmuraKeymasterblades018 wrote:
I can see you failed to throw that portion of code in to the editor and play around with it. This is a fairly obvious bug.Throw away everything from the previous posts.
lets try this again…
scenario 1
//##############
begin // minus here, which is correct// begin (no minus here, which is correct)
end
//##############scenario 2
//##############
begin // minus here, which is correct// begin (a minus now appears because of the comment in the following line of code, incorrect)
// stuffend
//##############on a side note, it seems like you inverted the “Make Comments Collapsible” check box
I now understand what you mean. It should be fixed in alpha 33. Thanks!
- AuthorPosts
- You must be logged in to reply to this topic.