TCAkelPad Lister plugin

[truepatch]

2) Exiting from Listen via Esc key works, but it takes too long, almost 2 seconds
If run it without Listen, the exit is instantaneous.

A new version of the plugin 1.11 will be released soon. Perhaps the described glitches will disappear there. I have now tested your questions. Everything is working correctly for me. If you have any questions, please let me know.
Long-term output may also be associated with the use of some AkelPad plugins. Some plugins cause glitches and crashes.
Please test it with the AkelPad ini files I attached.

I find problem freezing exit:

Code: Select all

AkelPadL.ini
[Plugs]
; Quick exit with my panels, scripts
Scripts::Main=65536
ContextMenu::Main=65536
ToolBar::Main=65536
SpecialChar::Main=65536
Coder::CodeFold=65536
Coder::HighLight=65536

; Slow exit if use any below
LineBoard::Main=65536
SmartSel::NoSelEOL=65536
SmartSel::SmartHome=65536
SmartSel::SmartUpDown=65536
SmartSel::SmartBackspace=65536
Sounds::Main=65536
Speech::Main=65536

It is necessary to apply the same operations for any plugins as for fast plugins, exactly there will be no freezing.

[AkulaBig]

I find problem freezing exit:

; Slow exit if use any below
LineBoard::Main=65536
SmartSel::NoSelEOL=65536
SmartSel::SmartHome=65536
SmartSel::SmartUpDown=65536
SmartSel::SmartBackspace=65536
Sounds::Main=65536
Speech::Main=65536

It is necessary to apply the same operations for any plugins as for fast plugins, exactly there will be no freezing.

Yes, look in my ini files to see which AkelPad plugins work normally with the plugin.

[AkulaBig]

You didn't explain about Ctrl+Alt+T. Whose hotkey is this? Apparently this is your hotkey?

[truepatch]

You didn't explain about Ctrl+Alt+T. Whose hotkey is this? Apparently this is your hotkey?

I answered
viewtopic.php?p=456128#p456128

[truepatch]

I find problem freezing exit:

; Slow exit if use any below
LineBoard::Main=65536
SmartSel::NoSelEOL=65536
SmartSel::SmartHome=65536
SmartSel::SmartUpDown=65536
SmartSel::SmartBackspace=65536
Sounds::Main=65536
Speech::Main=65536

It is necessary to apply the same operations for any plugins as for fast plugins, exactly there will be no freezing.

Yes, look in my ini files to see which AkelPad plugins work normally with the plugin.

I used your ini files, all your latest builds.
Please make it so that any plugins can be either processed or skipped so that there would be no freezes.
Any new plugin if added to the ini it slows down the output from Listen.
Without Listen everything works quickly. Leave it to the user to customize their own AkelPadL.ini.

Scripts don't slow down, forms don't slow down, new plugin or panel functionality is displayed in Listen, but only application exit slows down.

[AkulaBig]

I answered

Sorry, I looked it up.

I apologize a bit mixed up, I assigned it to "Ctrl + Shift + T",

I thought so. Of course, I can’t do anything with user-assigned hotkeys. Only with standard ones.

[AkulaBig]

Please make it so that any plugins can be either processed or skipped so that there would be no freezes.

You should ask the author of AkelPad for this. I do not change the code of the AkelPad program and its plugins. To use them fully, press F4

Leave it to the user to customize their own AkelPadL.ini.

The user can configure viewing modes at his own discretion. But we need to take into account the possibilities of collaboration between AkelPad and my plugin.

[truepatch]

Please make it so that any plugins can be either processed or skipped so that there would be no freezes.

You should ask the author of AkelPad for this. I do not change the code of the AkelPad program and its plugins. To use them fully, press F4

Leave it to the user to customize their own AkelPadL.ini.

The user can configure viewing modes at his own discretion. But we need to take into account the possibilities of collaboration between AkelPad and my plugin.

And what is the difficulty, can't unknown plugins follow the same processing cycle as already adapted plug-ins, but do not apply any operations to them?

While reading a sheet, the user for example wants to see the line numbering (LineBoard.ini), the plugin settings data will get into AkelPadL.ini, and it will start to slow down again. Or he will want to listen to a speaker reading, and again the same problem.

[AkulaBig]

And what is the difficulty, can't unknown plugins follow the same processing cycle as already adapted plug-ins, but do not apply any operations to them?

I haven't adapted anything for my plugin. AkelPad plugins either work with it or they don't. The reason can only be found out from the author. I can't influence this in any way.

[truepatch]

And what is the difficulty, can't unknown plugins follow the same processing cycle as already adapted plug-ins, but do not apply any operations to them?

I haven't adapted anything for my plugin. AkelPad plugins either work with it or they don't. The reason can only be found out from the author. I can't influence this in any way.

"AkelPad does not receive WM_CLOSE, so plugins are not unloaded correctly."

This was written by the developer of AkelPad.
Send this code to the editor after you have processed your plugins.

[AkulaBig]

"AkelPad does not receive WM_CLOSE, so plugins are not unloaded correctly."

I saw this post because I also asked the author about the problem with plugins. All that remains is to understand why some plugins receive the message and others do not. And what does my plugin have to do with it? If the message had not been received by the AkelPad program, it would not have closed. I'm currently working on a new version of the plugin. I'll check this information.

[truepatch]

"AkelPad does not receive WM_CLOSE, so plugins are not unloaded correctly."

I saw this post because I also asked the author about the problem with plugins. All that remains is to understand why some plugins receive the message and others do not. And what does my plugin have to do with it? If the message had not been received by the AkelPad program, it would not have closed. I'm currently working on a new version of the plugin. I'll check this information.

I think it is necessary to choice all loaded plugins and in a loop send them this message WM_CLOSE, without waiting for a response from plugins.

[AkulaBig]

I think it is necessary to choice all loaded plugins and in a loop send them this message WM_CLOSE, without waiting for a response from plugins.

Plugins are managed by AkelPad. My plugin can't manage them.

[AkulaBig]

send them this message WM_CLOSE

I tried directly sending a message to AkelPad. Indeed, the brakes have disappeared. All that remains is to figure out how to send a message from the Lister window when it has focus.

[truepatch]

send them this message WM_CLOSE

I tried directly sending a message to AkelPad. Indeed, the brakes have disappeared. All that remains is to figure out how to send a message from the Lister window when it has focus.

Just monitor this command and send WM_CLOSE to the process that called Command(4109). Regardless of the focus, since the script can execute to start a new AkelPad process and the old one is already sent to close.

Code: Select all

//Script restart.js or AkelPadRestart.js
AkelPad.Command(4109); // Exit