- AuthorPosts
- August 21, 2017 at 3:03 am #22289skyParticipant
Macro “Runs at Events” doesn’t work after v17.0.0
v16.9.3 is OK.August 21, 2017 at 3:11 am #22290Patrick CParticipantYep – same here, just wanted to post the issue as well ;)
Macro “Runs at Events” doesn’t work any more on my computer either.August 22, 2017 at 9:34 am #22295Patrick CParticipantFollow up question for Yutaka:
How are the macro settings in versions 17+ now accessed from within a macro?
Before v17 it was
sMacro1 = editor.GetProfileString(eeRegMacros, “”, “Macro1”, -1);Consequently
https://www.emeditor.com/forums/topic/macro-menu-toggle-runs-at-events-option-for-macros/
will probably have to be re-written.August 25, 2017 at 2:41 pm #22303Yutaka EmuraKeymasterI will fix the “Runs at Events” bug on the next version.
As for how to run a macro within a macro, please use ExecuteMacro Method:
http://www.emeditor.org/en/macro_editor_editor_executemacro.html
Thanks!
August 26, 2017 at 2:04 pm #22308npnilssonParticipantjust wanted to post the same issue. macro “runs at events” does not work on my system as well…is there any way to downgrade to the last version that it worked until the bug is fixed?
August 27, 2017 at 8:44 am #22311Patrick CParticipantI also tried downgrading – but at a price. The reason is that Emeditor transfers certain settings from version 16.9.3 to version 17. Those settings cannot be recovered when downgrading – except if you didn’t run “Delete old settings”. In my case I made a mess with my settings (own fault, I didn’t realise at first).
In any case, if you didn’t run “Delete old settings”, then you can give downgrading a try (at your own risk):
http://files.emeditor.com/emed64_16.9.3.exeAugust 27, 2017 at 8:55 am #22312Yutaka EmuraKeymasterHello,
I am sorry for inconveniences. The Runs at Events issue will be fixed on the next version (v17.1.1). Meanwhile, you can work around by adding a new registry value:
UsedEvents
as REG_DWORD at HKEY_CURRENT_USER\Software\EmSoft\EmEditor v3\Common, and set the value as 0xffffffff in hexadecimal (or 4294967295 in decimal).
Notes that this workaround will NOT be needed anymore once v17.1.1 is released and installed.
Thanks,
August 28, 2017 at 1:16 am #22317Patrick CParticipantYutaka’s workaround works on my machine :)
Thank you!!! Presently I do need this feature quite often.
- AuthorPosts
- You must be logged in to reply to this topic.