New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Must exit, restart for recipe changes to take effect #317

Closed
KentuckyFreudChicken opened this Issue Jan 12, 2019 · 4 comments

Comments

Projects
None yet
2 participants
@KentuckyFreudChicken
Copy link

KentuckyFreudChicken commented Jan 12, 2019

Describe the bug
Any edits I make to a recipe require a full exit and restart of the program to take effect.

To Reproduce
Steps to reproduce the behavior:

  1. Modify any recipe (add, change, remove ingredient -- they all cause same effect)
  2. Save updated recipe
  3. Trigger recipe with hotkeys
  4. Note that the recipe which was loaded before your updates is what plays. The updates didn't take effect.
  5. Exit MaxTo
  6. Start MaxTo back up, try the recipe again using hotkey, and note that the updated recipe now plays.

My Example: I changed a recipe (and then saved the changes) from opening notepad (%WinDir%\Notepad.exe) to opening any other program and, until I exited and restarted MaxTo, the hotkey for that recipe would still open Notepad, not the updated target. After exit/restart, the hotkey now triggers the updated target program.

Expected behavior
Edits to recipes will immediately take effect.

System information:

  • Windows version: Win 10, ver. 1809
  • MaxTo version: 2.0.0-beta6

@vegardlarsen vegardlarsen added this to the 2.0.0 milestone Jan 15, 2019

@vegardlarsen vegardlarsen self-assigned this Jan 15, 2019

@vegardlarsen vegardlarsen added the bug label Jan 15, 2019

@vegardlarsen

This comment has been minimized.

Copy link
Member

vegardlarsen commented Jan 15, 2019

Sorry for the slow response time on this. I can verify that I have been able to reproduce this, and will look into it before 2.0 goes final.

@vegardlarsen

This comment has been minimized.

Copy link
Member

vegardlarsen commented Jan 15, 2019

I found the fix for this quite easily, and this will be fixed for the next beta release (or final release if we think we are ready).

@KentuckyFreudChicken

This comment has been minimized.

Copy link
Author

KentuckyFreudChicken commented Jan 15, 2019

Thank you -- you're the best!

@vegardlarsen vegardlarsen modified the milestones: 2.0.0, 2.0.0-beta.8 Jan 18, 2019

@vegardlarsen

This comment has been minimized.

Copy link
Member

vegardlarsen commented Jan 18, 2019

This fix is out today in beta 8. Have a good weekend!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment