Ghost panels again

[ustk]

@Christoph-Hart I was almost sure it wouldn't work on your side

No the one you have is the good one, in fact nothing changed except this clear btn which has nothing to do...

I do recompile often, because sometimes it just doesn't want to throw a ghost. Also it is apparently not related to the number of children you decide to create (so probably not a cluttering thingy) because I tried with 300 sub children per row with no more statistics...

Could it be more prone to make a ghost on slower computers ? Or a CPU thing ? I guess not because one of my beta tester had the issue on an M1...

I have nothing more to add than "try more", because I can't get a way of increasing the stats.

I tried to make a button that force repaints everything (all parents and children) to see if the ghost repaints, but no. When a ghost is a ghost, it stays a ghost :)

I also tried to check for doublons but it appears ghosts aren't doublons either

So, could it be that the paint routine isn't attached to it ? because the mouseCB is working (click a ghost and you get the ID)
I reckon I asked this a while ago => we don't see the children appearing in the scriptWatchTable, that would allow to check if a paint routine is attached, but I don't know if this is a difficult task...

[ustk]

@Christoph-Hart I've been lucky here, 3 times I got some ghosts...

[d.healey]

@ustk I'm not getting any, but I'll keep trying. Are you using open GL? Clicking on a child gives an error btw. Are you using the latest develop branch?

[ustk]

@Christoph-Hart Youhou!!! I can get as many as I want by stressing the CPU using this method :

Stress Test a Mac by Maxing Out CPU

Stress Test a Mac by Maxing Out CPU

OS X Daily (osxdaily.com)

[d.healey]

@ustk :D progress!

[ustk]

@d-healey yes a recent develop, from around the faust implementation
Yes OpenGL is enabled, I'll try without...

[ustk]

@d-healey Disabling OpenGL doesn't help

[Christoph Hart]

@ustk that yes trick is terrible, I like it!

I also get a few ghosts now.

[ustk]

@Christoph-Hart Welcome to the ghost world

[Christoph Hart]

@ustk I think I've narrowed it down to something. The paint routine gets assigned after the glue object between scripting layer and UI is initialised but at the time setPaintRoutine is called, the initialization is completed and the UI component assumes that there is no paint function.

I'll do some more tests, but it seems to be fixable.

[ustk]

@Christoph-Hart

[Christoph Hart]

@ustk Alright, I've pushed a fix for it. the panel should now notify the UI component when a paint routine is assigned even after the initialization.

With the terminal trick and your snippets I don't get any ghost panels anymore. This was the only issue there, right?

[d.healey]

@Christoph-Hart I don't see the commit.

[Christoph Hart]

@d-healey yeah big brain here forgot to push...

[d.healey]

@Christoph-Hart said in Ghost panels again:

@d-healey yeah big brain here forgot to push...

Thank you, I'll try it out with Greg's snippet.

[ustk]

@Christoph-Hart Awesome ! I'll try that out tomorrow, the compile time on my mac is about 20min against the previous 7min from a few months back...
Yes that was the only thing :)

[Christoph Hart]

@ustk Hmm, that's weird, but I also noticed that the Link time optimization steps takes a bit longer than before. I've updated the asmjit library which has now a few more translation units and of course there are 3 new modules with Faust, but 20 minutes seems very unreasonable (the entire CI script that builds HISE and a test project takes 7 minutes on my M1).

You might get away with disabling Link time optimization in the HISE projucer project if you're regularly recompiling HISE. It will run a little bit slower (and the binary might be a little bit bigger), but for development it should be fast enough.

[ustk]

@Christoph-Hart Using eight yes commands with burning CPU, the house is safe ! Ghosts are out for good !