1. RE: Nexus v1.0.0
Don Phillips wrote:
> Just uploaded to RDS the first version of my Nexus code editor.
> (12pm Thurs)
>
>
Excellent start. At the moment, the things that would prevent me from
using it for day to day coding are:
-- You can't open more than one file at a time.
-- If you close down the program, or open another file, whatever file
you already have open is instantly gone forever, saved or not.
That simply makes it too dangerous to use for serious work.
The other feature I would love to see is the ability to list functions &
procedures and jump to them...
2. RE: Nexus v1.0.0
--0-1365688213-1035068500=:23509
> Excellent start. At the moment, the things that would prevent me from
> using it for day to day coding are:
Thanks =)
> -- You can't open more than one file at a time.
Thats on my list of things to do. Also one of the reasons why I am putting my
controls into rebars. Easy to show / hide them.
> -- If you close down the program, or open another file, whatever file
> you already have open is instantly gone forever, saved or not.
Yes, this is actually first on my list. Its very easy to implement so you
should see this in the near future. I am also changing the way the "execute
program" button functions. Most of this is already coded.
> The other feature I would love to see is the ability to list functions &
> procedures and jump to them...
Ahh, hmm. I will think about how best to add this to the editor. It should not
be very hard at all.
Thanks for the input in any case. The multiple files open issue will take awile
to implement and will need alot of testing from me. Things like associating the
tool button states to each window open will need to be addressed and such. If
there are any more issues let me know.
Don
<P>> Excellent start. At the moment, the things that would prevent me
from <BR>> using it for day to day coding are:<BR>Thanks =)</P>
<P>> -- You can't open more than one file at a time.<BR>Thats on my list of
things to do. Also one of the reasons why I am putting my controls into
rebars. Easy to show / hide them.</P>
<P>> -- If you close down the program, or open another file, whatever file
<BR>> you already have open is instantly gone forever, saved or not.<BR>Yes,
this is actually first on my list. Its very easy to implement so you should
see this in the near future. I am also changing the way the "execute
program" button functions. Most of this is already coded.</P>
<P>> The other feature I would love to see is the ability to list functions
& <BR>> procedures and jump to them...<BR>Ahh, hmm. I will think
about how best to add this to the editor. It should not be very hard at
all.</P>
<P>Thanks for the input in any case. The multiple files open issue will
take awile to implement and will need alot of testing from me. Things like
associating the tool button states to each window open will need to be addressed
and such. If there are any more issues let me know.</P>
<P>Don</P><p><br><hr size=1>Do you Yahoo!?<br>
<a href="http://webhosting.yahoo.com/ ">Y! Web Hosting</a> - Let the expert host
your web site
--0-1365688213-1035068500=:23509--
3. RE: Nexus v1.0.0
> When I first ran Nexus, I got the following:
>
> Nexus.exw:743 in procedure FindHelpFiles()
> subscript value 1 is out of bounds, reading from a sequence of length 0
> ... called from Nexus.exw:1282 in procedure onOpen_Nexus()
> ... called from g:\euphoria\include\Win32Lib.ew:7773 in function
> invokeHandler()
>
> ... called from g:\euphoria\include\Win32Lib.ew:23455 in procedure
> openWindow()
>
> ... called from g:\euphoria\include\Win32Lib.ew:23702 in procedure
> WinMain()
> ... called from Nexus.exw:1289
> --> see ex.err
>
> I fixed this (I think!) by changing the line:
>
> if DirectoryList[ListIter][2][1] = 'd' then
>
> to:
>
> if find('d', DirectoryList[ListIter][2]) then
> ----------------
> The error would not occur if ALL directory entries had at least
> one attribute:
> e.g. "a". Check to see if this is the case in your EUDIR.
Hmm. I will definately have to take a closer look at this. According
to your dump the fix is trivial. Thanks for pointing this out to me so
I can correct this in my next release.
> Also, when the option to "Fixup text case while typing language
> keywords" was checked with Nexus.exw loaded, the variable name "Type" in
>
> "atom Type" was fixed to "type"
> causing this error when Nexus,exw was next run:
>
> g:\download\in\nexus>exw Nexus.exw
> Nexus.exw:323
> a variable name is expected here
> atom type
> ^
> in GetProfileBin().
>
> Keep up the good work,
>
> Bob
Yes, I was wondering if this was going to be a problem. The exact same
thing happened to me using the editor not 2 days previous when I was
testing it. I have renamed that variable to better reflect what it is
doing in the function.
Don
