Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #27648
    Yutaka Emura

    Today, we are releasing EmEditor v21.0 beta 9 (20.9.909).

    Updates from beta 8 include:
    – Added the Macro text box, button, the Set Repeat Count check box, the Run the macro against each opened document check box, the Name list box, the Add button, the Delete button, the > button, the Save and close each document after running the macro check box, and the Save options check box to the Macro Temporary Options dialog box.
    – Added the SelectColumn method to the Selection object.
    – The new version adds the command name as a comment to each editor.ExecuteCommandByID method when saving/editing a recorded macro.
    Fixed a pre-v20.9 issue of additional GDI object leaks, especially when the Very Dark (beta) option is set.
    – Fixed a pre-v20.9 bug where EmEditor could crash while showing a Minimap.
    – Fixed a pre-v20.9 bug where EmEditor could crash on the Combine Lines command if inconsistent number columns were detected in a CSV document.

    Please see EmEditor v20.9 New Features for details and screenshots.

    Notes: Beta versions are updated frequently. If you use the installer version, please select Customize Update Checker on the Help menu, and set the Include beta versions in order to update automatically to future beta versions. Beta versions can also be downloaded at Previous versions.

    Please post any questions or comments in this forum, or Contact us.
    Thank you for trying EmEditor beta!

    ▲ Is it possible to implement the two suggestions now (in the new “Macro Temporary Options” dialog box)?

    Is it possible to make EmEditor accept the clipboard content (or a selection of text) as the temporary macro?
    I know a macro can do this and I made one. But how about making it as a native feature?

    Is it possible to implement this:

    Thank you.

    Yutaka Emura

    I will consider those feature requests on v21.1. Thank you.

    Yutaka Emura

    v21.1 beta 2 (21.0.902) supports hopefully all those feature requests.

    This version supports Get/Write QWord integers.

    Since JavaScript numbers don’t support 64-bit integers, you will need to use GetProfileString/WriteProfileString, and these methods can now read/write 64-bit integers as hexadecimal strings.

    To write QWord integers, you can write:

    nLow = 0x02000183;
    nHigh = 0x00000004;
    s64 = "0x" + nHigh.toString(16) + ("00000000" + nLow.toString(16)).slice(-8);
    editor.WriteProfileString( eeRegCommon, "", "FindFlag", s64, eeRegQWord );

    To read QWord integers, you can write:

    nHigh = 0;
    nLow = 0;
    s = editor.GetProfileString( eeRegCommon, "", "FindFlag", "0" );
    if( s.length == 18 && s.substr( 0, 2 ) == "0x" ) {
    	nHigh = parseInt( s.substr( 2, 8 ), 16 );
    	nLow = parseInt( s.substr( 10, 8 ), 16 );

    I hope this works for you.


    Thank you!
    Works as expected in simple tests.
    I will use it further in practice.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.