Hollywood forums

My suggestion to you is this: write the interpreter using nested tables first. You can export your table format to a JSON file later to see what it looks like and use the JSON importer to read your changes back in. The only problem I can see with using JSON is that Hollywood uses tables to represent...

Running the script will require the array to be formatted as line number as a key and command table as a value. The command table will have the keyword string as the key and the parameter array as a value. The parameter array can contain expressions or terminal values but still use the parameter ord...

ReadTable and WriteTable will help with serialization of your language assuming it's formatted as a dynamic Array.

Rnd(1) gives 1 possible integer value of 0

Rnd(2) gives 1 of 2 possible values: 0 or 1. This is due to the range select value being applied as a modulo operation.

sashapont wrote: ↑

Sun Sep 22, 2019 12:01 pm

Now we will wait for RapaGUI for iOS!

And please give full working example with interaction Hollywood and standard iOS interface.

Even if a RapaGUI XML to XIB conversion would help. Do you know if the XIB file specification is available?

Internally, I think string keys are made lowercase if you use the dot notation. You're using the dot notation to try to look at a table element that is uppercase. Try either using the square brace notation in your lookup or make the keys lowercase in your assignment.

What version of Raspbian are you running? (Or are you using another Linux?)

I've been told that Hollywood wrapping with other programming languages is against the Hollywood license. I wanted to wrap Hollywood with a graphical syntax and that's the answer I got.

Sounds to me like the locale support is kicking in.

What's wrong with a preprocessor macro for the different OS's serial devices?