Author Topic: Creating a Delay before initiating another plugin script  (Read 1149 times)

keilmillerjr

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 950
    • View Profile
Re: Creating a Delay before initiating another plugin script
« Reply #15 on: December 31, 2018, 06:02:45 PM »
It could be the system call. Try using the program background command. Not sure of official name. Out with family and kids driving me nuts. Let me know if it work. Happy New Years!

Edit: the pause on the front end is because your returning in a transition. If this is undesirable, toggle a Boolean class variable to start a class function counting a ticks callback. Let me know and I can work with you on this tomorrow.
« Last Edit: December 31, 2018, 08:21:33 PM by keilmillerjr »

spud1

  • Full Member
  • ***
  • Posts: 40
    • View Profile
Re: Creating a Delay before initiating another plugin script
« Reply #16 on: December 31, 2018, 10:05:18 PM »
Thanks for your help.  Hope the kids haven't driven you bananas.

I replaced the system call with
Code: [Select]
fe.plugin_command_bg( "/home/pi/.attract/plugins/AutoFavorites/update.sh" );
However, the same error appears. Not sure why line 50 would be so important.

I'm fine with how the bash scripts are operating at present.  There's no real transition delay as long as I've got them set up the way I've got them setup ie one bash script leading into another.