Engine.createGlobalScriptLookAndFeel not work

[Mike]

@d-healey no - only one -and actually I just want to try the look and feel functionality!

[d.healey]

@Mike Are you using git to manage versions?

[Mike]

@d-healey nop

[d.healey]

@Mike So you deleted the previous copy of the source code you had when you downloaded the scriptnode branch, correct?

[Mike]

@d-healey I downloaded the version HISE-Master from Github and installed it after your video "Install HISE on Mac OSX Mojave". Works also so far. Otherwise I did nothing!

[d.healey]

You need to delete that and use the scriptnode branch

GitHub - christophhart/HISE at scriptnode

The open source framework for sample based instruments - GitHub - christophhart/HISE at scriptnode

GitHub (github.com)

[Mike]

@d-healey Ok - Thank you very much - I will try it

[Mike]

@Mike Everything worked out - Great - Thanks David

[Gabriel Strozi]

Sorry for re-opening this Topic (is it better to open a new one when it happen?)
I have the same problem with Engine.createGlobalScriptLookAndFeel.

@d-healey said in Engine.createGlobalScriptLookAndFeel not work:

You need to delete that and use the scriptnode branch

GitHub - christophhart/HISE at scriptnode

The open source framework for sample based instruments - GitHub - christophhart/HISE at scriptnode

GitHub (github.com)

I tried to delete all inside HISE-Master folder and past all that I downloaded on link above, but it didn't work.

Any suggestions?

[DabDab]

@Gabriel-Strozi Which branch are you using?

[Matt_SF]

@Gabriel-Strozi The scriptnode branch was the one at that time, but now use the 'develop' branch (new_layout is the latest but Christoph's still working on it).

[Gabriel Strozi]

@DabDab said in Engine.createGlobalScriptLookAndFeel not work:

@Gabriel-Strozi Which branch are you using?

I'm using the scriptnode branch as suggested!

I'm downloading all the code from the link @d-healey sent:

Then extracting and replacing all the Hise-master folder content with this new code. Am I doing something wrong or too much newbie? haha.

Thank you guys for the patience!

[Gabriel Strozi]

@Matt_SF said in Engine.createGlobalScriptLookAndFeel not work:

@Gabriel-Strozi The scriptnode branch was the one at that time, but now use the 'develop' branch (new_layout is the latest but Christoph's still working on it).

I'm downloading the delvelp branch right now to test! I tell you with it works!

[Gabriel Strozi]

Ok, I tried to replace Hise-Master folder with develop branch content and still Engine.createGlobalScriptLookAndFeel not found and not listed in API Browser. :/

Any other suggestions?

[DabDab]

@Gabriel-Strozi Both Develop Branch and ScriptNode Branch I use .. Work Perfectly (y)

Today I gave a try for Layout Branch.. OMG.. Insane. Every time it got crashed. Tomorrow I will post the screen recording. :anxious_face_with_sweat:

[d.healey]

@Gabriel-Strozi said in Engine.createGlobalScriptLookAndFeel not work:

I tried to replace Hise-Master folder

What did you do exactly, step by step?

[DabDab]

@Gabriel-Strozi @d-healey is the real Manager of HISE. Being a Developer and Founder(@Christoph-Hart ) it is difficult to answer users difficulties and problems. Most of the time I have seen Mr Healey helps at his best. When he suggested to use ScriptNode branch go for it.

[Gabriel Strozi]

@d-healey said in Engine.createGlobalScriptLookAndFeel not work:

@Gabriel-Strozi said in Engine.createGlobalScriptLookAndFeel not work:

I tried to replace Hise-Master folder

What did you do exactly, step by step?

Step 1 - downloaded develop-branch:

Step 2 - extracted HISE-develop.rar

Step 3 - deleted all the current HISE-master folder content:

Step 4 - copied and pasted all the HISE-develop content into HISE-master folder

I did the same try with scriptNode branch!
Is it better to just redirect HISE-master folder to HISE-develop folder in the HISE preferences?

[DabDab]

@Gabriel-Strozi No Delete master. Only use scriptNode

[d.healey]

As DabDab says, delete the HISE master entirely.

You missed out the most important step though, recompile HISE.

Is it better to just redirect HISE-master folder to HISE-develop folder in the HISE preferences

No that's only relevant for exporting plugins. The best solution is to use git.