BTW, I stupidly had clicked the "don't show me this again" checkbox. Is deleting the foo_spider_monkey.dll.cfg good enough to reset that? It didn't reset the panel configuration so some data is being stored elsewhere at least.

Does that mean you could also hide the dialog again, once things become responsive again, or no?

I'm trying  to process selected files from a playlist. Firstly I want to convert them and I'm using:
fb.RunContextCommandWithMetadb("Convert/mp3 tablet",handle_list);
then I want to embed the album cover. My problem is the the RunContextCommand doesn't block so I need an event that is raised when all the files have been converted. Any ideas?

const handleList= <get handleList>;                                         

fb.RunContextCommandWithMetadb("Convert/mp3 tablet",handleList);
  
const processItem=() => {
  if(!handleList.Count) return false;
      
  const metaDb=handleList[0];

  <do the processing for metaDb>

  handleList.RemoveById(0);

  return Boolean(handleList.Count);
};

() => {
   if(!processItem()) return;
    
   setTimeout(arguments.callee,20);
}();

That seems dangerous to me. You're essentially just guessing that each file will be written in 20ms. If HDDs need to spin back up, or a file is huge, this will fail just like B_O_B_M's original case.

@MordredKLB , I've tinkered around a bit . Regretfully, it seems that it's impossible to make `slow script` dialog asynchronyous (without writing/using a new GUI stack): the problem is that GUI handling/processing is performed on the main thread, so if the main thread is stuck (e.g. in the infinite loop in JS), then no GUI messages can be processed making it impossible to interact with any dialogs (including `slow script` dialog).

While I understand your problem, I just don't know what can be done without removing the `slow script` check. I will try to extend the time limit a bit for the script on fb2k startup (in case there's some async stuff that hogging up the CPU), but it's still won't be a universal solution and it might not help much in your case.

[EDIT] Welp, no idea how to check that fb2k has loaded everything. Hence decided to make `slow script` time limit configurable (Advanced > SMP > Performance > Execution time limit).

It's weird though that SMP can still display the dialog.

Are you saying SMP executes the JS in the main thread then?

In that case I would have thought that the interruption handler wouldn't have been able to work since it's also on the main thread, unless I'm misunderstanding how that even works.

// SM internals
// Everything here is executed on the main thread

void JSMachineRunner()
{
  while (hasStuffToDo)
  {
    auto currentPart = GetNewPart();
    ExecuteJSMaybe(currentPart);
  }
}

void ExecuteJSMaybe(JSPart part)
{
  if (interruptRequested)
  {
    InvokeInterruptCallback();
  }
  ExecuteJS(part);
}

I might try some tests with async/await wrapping includes.

function loadAsyncFile(filePath) {
    return new Promise(resolve => {
        setTimeout(() => {
            include(filePath);
            resolve();
        }, 1);
    })
}

const basePath = fb.ProfilePath + 'georgia\\';

async function includeFiles(fileList) {
    for (let i = 0; i < fileList.length; i++) {
        await loadAsyncFile(basePath + fileList[i]);
    }
}

includeFiles([
    'js\\CaTRoX_QWR\\lodash.min.js',
    . . . // all other files
]);

@wcs13 , it might be possible to implement such logic in the script (ignoring low-res images that is), but I'm currently prioritizing component development over script improvement. In other words it won't be fixed anytime soon, sorry.

	this.update = () => {
		this.image = 0;
		this.files = [];
		this.images = [];

		let tmp = _getFiles(this.folder, this.exts, this.properties.sort.value == 1);
		tmp.forEach((item) => {
			let img = gdi.Image(item);
			if (img && img.Width >= 500 && img.Height >= 500) {
				this.files.push(item);
				this.images.push(img);
			}
		});
		
		this.size(true);
		window.Repaint();
	}