Beta 1.50

[JJK]

bug fixes

bugs fixed

Not the same thing.
Never Alex said that all the bugs were fixed, only some bug fixs in 1.50 development snapshot.

Wait still. Alex is working 

[alex]

Hi Arthur,

yes, guys are right. This is alpha development version, and it full of bugs and incomplete features. I provide it only to show you the progress and prove that I am still working . So bug reports are not really helpful here. Everything can change and there are too much of them that I need a reports - most of them I can see by myself

But nevertheless there are some people, who uses this version productively (while I suggested to no do so). For such cases, I need to fix at least crashes, because it is pity if people lose their work. This is what I meant under "bugs fixed or bug fixes etc". I do not care about performance, not implemented features or bugs which are not crashes (or seldom crashes). The real beta is 1.49, see corresponding topic.

1) Why do I see two same spell check buttons? Neither work - does not correct my misspelled words.

buttons are not the same - images are different, names are different (see tooltip). One opens interactive checking dialog, another controls background checking. Misspelled words are not corrected automatically: you need to trigger action or with context menu for background checked words (wave underlining) or select Change in interactive dialog. First button. Of course your document should not be read only, and misspelled words should be inside.

2) I always opt to install the Full HE, the book mark manager though is not checked in the installer;

In my case in Full installation is checked (but not in Custom). But does not matter, this is not a final state, I will check this later.

3) If you have White Space turned to be seen, if I say resize the Project Pane/File Explorer the last that weird char becomes hidden, besides it is strange that is being controlled via White Space, because it is actually not, it is a LFCR combo, any thought?

This is at all unclear. Screenshot will help.

4) Macros!! Finally, thank you, but why to run them it runs so slow? Edit does not work, Convert to Script does not work. Save as wants to save my file instead.

This is not yet finished. I will check this once more after scripting ready.

Best regards,
Alex.

[Arthur]

re #3:
The functionality name is misleading, it says "show white space", but the line end chars are not white space.
The screen-shot is not necessary, produce a long, long line of text, enable show White Space (err to see the line endings) and resize (width) the project explorer back and forth until you will notice the top right margin hidden burying the end of line chars.

[alex]

The functionality name is misleading, it says "show white space", but the line end chars are not white space.

Ok, but until now nobody complain and I thought that is us clear that line ending is also meant (generally, line breaks is also a white space between lines ). I do not want to create additional setting for line ending only (think it is too much), so if you have another well known SHORT term I can change this. Otherwise I think it is OK like now. In MS Word there is also only one switch for all formatting symbols.

Unfortunately I was not able to recreate an example (did long line and have done resizing). I my case all was drawn correctly. So, I will appreciate screenshot, because I am not sure that I got you right.

[Arthur]

Show all symbols I guess is a meaningful extension.
Here is the screenshot. Make a note: if you move the hor bar it does not reveal the line endings (were enabled before, text line length = 150 chars). Even if I click End on the keyboard the cursor does not move past that point, so I do not see if there is a line ending or not.

[alex]

Hi Arthur,

Show all symbols I guess is a meaningful extension.

Yes, the name is OK, and probably I will do this, the only problem, that there is a command View.WhiteSpace already exist. And I need also to rename it to be consistent. This will lead to the fact that users who have mapped a shortcut to it ill lose it. But OK, hope there are not too many of them and this will not be painful. But in any case I will do this only for 1.50. Such change (not from technical point of view) is not acceptable for a minor update.

Here is the screenshot.

Thanks! Now I have understood what you meant... Yes this is rght. And this is not 1.50 relevant but also should happen in 1.48-1.49. Line ending "characters" is not taken into account when calculating as optimum position as scrolling positions, because they treated as virtual (visualization only)... That is why you are not bale to scroll there.
Yes, probably we can recognize this as bug, but I will not give this too high priority: you have workaround - just do screen wider or enable word wrap and you will see them. And effort for me to fix this rather big. So, I will note it but will fix this as far I will do something in this area or will have more important topics finished. Until then - it will be a known bug .

Best regards,
Alex.

[cmwade77]

Currently I have no idea.
I am busy with bug fixing for 1.42 (this is more important to me) and some website work for publishing syntax bundles.
When I got a free slot I would start with 1.50.

I would recommend working on 1.50 and fix the bugs that were found in 1.42 in it, this way both are completed at the same time.

[JJK]

Yes, Alex has already published r 1.48, and, sure, he has fixed many anterior bugs.

There are also already test versions of future r 1.50.

In the first post of this section, Alex said :
You can check current state with this installer (only Unicode version), but remember this EVEN NOT AN ALPHA, just an current development snapshot: with bugs, crashes and incomplete features. So do not use it productively and do not report bugs.

[alex]

Thanks JJK.
Yes, the work on 1.50 is in progress and I publish intermediate version from time to time.
And of course I do the double maintenance and bugs fixed first in 1.50 and then downported to 1.4x branch.

[Arthur]

I propose we get a New Year present in form of a new build with more production grade features!

[alex]

Beta 1.50 was updated:
- correction for editing functions which now uses position and range objects. See updated heapi.chm. For example see edit.hejs from scripting examples.
- WScript emulation, which allows usage of scripts written for WSH directly on HE without modification. Not all properties are supported bu most. Missing will be added on demand. For example see scripts from 1.50: scripting first test -> wscript_test.js.
- new controls added to XML dialogs as datatime for selecting of date/time, color_browser for color selection and font_browser for font selection. See updated dialog_test.hejs and dialog_actions.hejs.

[alex]

Beta 1.50 was updated (722):
- multi key keyboard shortcuts added.
- local search for search results added.
- new control added to XML dialogs - history_edit, same as edit but with history of inputs. Only single line. See updated dialog_test.hejs.
- new stuff for scripting. See now already useful script remove_empty_lines.hejs
All scrips can be found here 1.50: scripting first test.

[alex]

1.50 alpha updated. Looks that I have forgotten to increase build number, so it is still 722, so do be surprised

main new feature is script plugins.
For me now scripting story looks to be more or less architecturally complete. There are some things that should be added, but I do not plan any big changes. Just some missing functionality and bug fixes. Also, I still need to add converters, that migrate macro to a script. Maybe some shell apis would be necessary.

[alex]

1.50 alpha updated to build 724.
Mostly extension for scripting (outlining data is exposed), bug fixes, updated syntax schema for hejs, recent scripts etc.
New script plugin for testing outlining data.

[alex]

1.50 turned to beta.