Code Editor

[masteralone]

I have done a lot of work using html editors throughout the years. One feature most of them have is Line numbering. So if I am working on a large project and it turns out that I have an error and it is reported back by line number, I can be easily find it and correct it.

Speaking for myself, and probably 99% of the people using the code editor, I sure would appreciate a simple little thing like Line Numbering in the code editor so when I get an error msg referring to line xx and the definition extra characters, I can find the one to which it refers.

I, for one, don't know how the lines are counted. Are dimmed lines counted? are blank lines counted? etc.

Any other thoughts on this?

[Peter.Greulich]

Is this what you are referring to? - see attachment

[masteralone]

yes!!!!!!!

[Peter.Greulich]

I'll send you my bill in the morning. :D

[masteralone]

Lol, bill for what? all I see is the thumbnail, how do you turn on line numbering? grins, or did you do a little image editing?

[Peter.Greulich]

In the code editor, right click, near the bottom there is the line number option. It's also in another menu somewhere. Doesn't work in the interactive editor.

[Peter.Greulich]

See attached...

[urbanski]

OPen an a5w page, click on source on the bottom tabs, RIGHT click in an open space and select line numbers.


Jim

[masteralone]

Thank you so much Peter. Now I wonder why it isn't a default setting rather than an option since you can get an error message while compiling and the compiler will only give you the line number and error msg.

Laughs, yes, I would complain if I was being strung up with a brand new rope.

[Tom Cone Jr]

Re: Code Editor

Oran,

For future reference, open the Help file. Choose Search tab. Search for "line numbering". 4th entry returned "Using the Xbasic Code Editor". You'll find line numbering in the grid describing the editor's functions. . There's also an entry in the Index under Code Editor. It's called "Displaying Line Numbers".

Incidentally, the current line number also displays in the status bar at the bottom of the editor window. I've used this for years to find lines referenced by error messages, without ever enabling line numbering generally

-- tom

[masteralone]

Re: Code Editor

Thanks Tom, I learn something new everyday about this beast. I have to admit I never looked at the status bar while in the code editor, guess I was concentrating on what I was doing. And I have given up on trying to find minor stuff in help like line numbering because I don't think like Alpha Software. I seem to find a lot of the 'methods and functions' by rummaging around in help for a while on what I can find in related issues and finally come across something that gets me where I want to go.

[Cheryl Lemire]

Re: Code Editor

Oran,

I have given up on trying to find minor stuff in help

It is never a good idea to give up. The more I search in the help files, the better I understand how the indexing works and the easier it is for me to find things in the future.

[masteralone]

Re: Code Editor

Hi Cheryl,

I am one of those people that has much better luck researching a hard copy of a users manual or xbasic reference guide than I do using onscreen help. With a book, I am quickly able to figure out the mindset, philosophy, logic or whatever you want to call it, of the person/people that wrote it.

When I bought A5V4, since I didn't have a duplex laser printer, I spent the time figuring out how to do it with my old panasonic so that I had prints on both sides of a single sheet of paper and it was numbered sequentially. This gave me a hard copy of the users manual and the xbasic reference guide.

I didn't upgrade until A5V6 and only then because of the free upgrade to V7 that came with the purchase.

The more I try to use the onscreen help, the more frustrated I become when I know the answer is in there but I can't find it unless I spend a lot of time in it and find it by a sideways attempt rather than being able to type it in the index search part of help.

An example, yesterday, while reading posts on forum, I wanted to look up in help 'mode_get'. I finally found it by looking under mode, then looked at get form mode under that (which isn't what I wanted after alll) then noticed Form Functions and Methods under See Also, found .mode_get(), clicked on it, and finally found what I was looking for. Or so I thought. Out of curiosity, I then went back to index search, typed in .mode_get(), hit enter and a popup box comes up with the choices of <Field_rules>.mode_get, <OBJECT>.Mode_Get(), and <TBL>.Mode_Get().

In looking through these 3 .mode_get) choices, I still haven't envisioned the use in a field rule, discovered that <OBJECT> returns one of 5 char strings (view/change/enter/query/find) and that the <tbl> version still returns a numeric value and is limited to view/change/enter. Actually, the object version is a little ambiguous, it doesn't say it returns a char or a number, just has "View" = 0, "Change" = 1, and so on. Will play with it to find out if it returns a char or number in the interactive window.

Ok, enough about all this. I think now you may understad where I am coming from. I do not have the philosophy of "if all else fails read the manual". I just prefer a hard copy manual over onscreen. And if it is like my old V4 printouts in document protectors in a binder, I can pull them out and have them side by side for comparison viewing. ;)

[Tom Cone Jr]

Re: Code Editor

Good morning Oran.

The reality is that the size of the documentation has grown to the point where it's almost unmanageable in hard copy format. Furthermore, the help file is dynamic, changing frequently. Printed manuals are static. For example, you could relate your recent struggle to Ed Larrabee at Alpha Software (he's the chief technical writer). He's very responsive to suggestions for improvements, and they can be integrated into the CHM rapidly. This is not possible with printed manuals. If you have ideas for improving the index, or requesting more examples for specific funcitons or methods, let Ed know.

I have grown to like the CHM format after struggling with it for quite a while. In the Index, the first tier entries are almost always nouns. Second tier entries include entries that sometimes begin with nouns and sometimes verbs. So, I begin an Index search by thinking of a category or topic name, and then visually scan for action words (like "get" or "set") that pertain. Obviously, nomenclature is a problem for beginners. But using the CHM is the best way to become familiar with the terms Alpha uses. Cheryl's advice is sound. Force yourself to keep using it. When the frustration level gets too high, post a note here and we'll see if we can't refer you to the correct section or topic. -- tom

[csda1]

Re: Code Editor

I don't care for the windows help search engine, and find it misses pages of the help information all the time. I often use the PDF version to search, however, that is not as up-to-date. I'd love to see a better, or alternative search engine for the help.

After discussing it with Ed and Selwyn, a good solution is to use Google Desktop search, or the regular google search engine. For the regular Google search engine, go to the advanced search, Set Domain: to Only and the Site/Domain next to it to http://support.alphasoftware.com/alphafivehelp

While not perfect, it seems to find all references that meet the search criteria.

I hope this helps!