The LineSpace concept addition to SciTE

[Jos]

6 minutes ago, gil900 said:

No. Because #include of "xyz.au3" you can add only once and this you can add as many times you want

Not really? ...  as long as it doesn't contain a ##include-once you can include it as often as you want, anywhere you want.

Just trying to understand how this would make somebodies coding life easier.

Jos

Edited April 22, 2017 by Jos

[Guest]

3 minutes ago, Jos said:

Not really? ...  as long as it doesn't contain a ##include-once you can include it as often as you want, anywhere you want.

Just trying to understand how this would make somebodies coding life easier.

Jos

Try it. it will not work.

And anyway, the important part of my idea is also the sub-editor. open section of code wihout loosing the focus from the main code will make coding life easier

[Jos]

3 minutes ago, gil900 said:

Try it. it will not work.

It works fine...  tested as follows:

Test.au3:

consolewrite( "test 1" & @CRLF)
#include "test2.au3"
consolewrite( "test 2" & @CRLF)
#include "test2.au3"
consolewrite( "test 3" & @CRLF)
#include "test2.au3"

Test2.au3:

msgbox(1,"test","Test")

Jos

Edited April 22, 2017 by Jos

[Guest]

Just now, Jos said:

It works fine...  tested as follows:

Test.au3:

consolewrite( "test 1" & @CRLF)
#include "test2.au3"
consolewrite( "test 2" & @CRLF)
#include "test2.au3"
consolewrite( "test 3" & @CRLF)
#include "test2.au3"

Test2.au3:

msgbox(1,"test","Test")

Jos

In test2.au3 try to write some function..

For example Func Test()

I got the error "Duplicate function name"

[Jos]

As I said... I am probably missing something as to understand how this works when run/compiled.  

Jos

[Guest]

You seem to have misunderstood the idea.
The idea is not to include the same code again. But including it only once and then the rest of the #LineSpace will serve only as links to the same code that included once

[InunoTaishou]

You're not the only one @Jos, I don't understand the benefit of using this directive over just #include "Script File.au3"

#include <Array.au3>

Global $aArray[] = [99, 88, 77, 66, 55, 44, 33, 22, 11, 0]

_ArrayDisplay($aArray)

#include <Array.au3>
#include <Array.au3>
#include <Array.au3>
#include <Array.au3>
#include <Array.au3>

_ArrayDelete($aArray, 0)
_ArrayDisplay($aArray)

#include <Array.au3>

_ArrayDelete($aArray, 0)
_ArrayDisplay($aArray)

Of course Array.au3 has #include-once so it's protected from having all of it's function imported into the main script. Which is exactly what the #include-once directive is there for. Any UDF script should have #include-once at the top to prevent errors in users scripts.

So what's the benefit of #LineSpace compared to the normal #include?

[Guest]

9 hours ago, InunoTaishou said:

You're not the only one @Jos, I don't understand the benefit of using this directive over just #include "Script File.au3"

#include <Array.au3>

Global $aArray[] = [99, 88, 77, 66, 55, 44, 33, 22, 11, 0]

_ArrayDisplay($aArray)

#include <Array.au3>
#include <Array.au3>
#include <Array.au3>
#include <Array.au3>
#include <Array.au3>

_ArrayDelete($aArray, 0)
_ArrayDisplay($aArray)

#include <Array.au3>

_ArrayDelete($aArray, 0)
_ArrayDisplay($aArray)

Of course Array.au3 has #include-once so it's protected from having all of it's function imported into the main script. Which is exactly what the #include-once directive is there for. Any UDF script should have #include-once at the top to prevent errors in users scripts.

So what's the benefit of #LineSpace compared to the normal #include?

I see. Now it does work.
The only advantage is the sub-editor window
I told that my idea was not good enough and I was not going to use it after a second thought.
But I still claim there are some good things in my idea that I recommend adopting in a new idea - the part of the secondary editor window. I also claim that the part of "link to code" is a  domain/area  that there is much to innovate  about..
I said here that better idea then this is to create directive that is link to some region/end region directive , that will open in sub editor the region the link to.. and the sub editor will show only that region..
And about jumping, why not have option to jump but in a way that it will not open in the main editor? think about it.

Edited April 23, 2017 by Guest

[Jos]

There is always something good in having ideas and sharing them like you did. It triggered a lot questions/suggestions etc and that is what this is all about for me when participating in this community! 
There is no right or wrong here either, so keep on sharing ideas when you have them.

Jos 

[mLipok]

And do not worry about shame or mistakes. 

Every body here are human.

It mean all here making mistakes. The most imortant is going forward to finall success.

 

Edited April 23, 2017 by mLipok

[Guest]

36 minutes ago, mLipok said:

And do not worry about shame or mistakes. 

Every body here are human.

It mean all here making mistakes. The most imortant is going forward to finall success.

 

of course. I was not even in the direction.
I did not think for a moment to be ashamed. I see it differently - it was fun to do and it took me about 1 day.

This is just a little story of just one day. Not a big deal at all..  

And in any case there is no reason to be ashamed. I know other people who try and fail. That's how the world works. I decided from my experience to just do what I do for fun at first priority and second or third priority to do it for success

Edited April 23, 2017 by Guest

[InunoTaishou]

I do like the idea of being able to open a second editor jumping to the function I need. Sounds convenient. Perhaps a future implementation in the SciTE editor.

[TheSaint]

Or better still, with a wide screen, two panes side by side. One pane the main script, the other a function pane.