Hollywood forums

Posted: **Sun Jul 24, 2016 10:30 am**

I just ended, once again to the situation where I am making table of "triggers" to 2 dimensional map.

Idea is that I have this:

Code: Select all

Map = {
       [1] = {1, 2, 3}
       [2] = {1, 2, 3}
       [3] = {1, 2, 3}

Then i start making some blocks being triggers:

Code: Select all

Triggers = {
         [2] = { [3] = {trigger} }
               }

Especially when there are several triggers, it becomes bit ugly, hence i would rather just do:

Code: Select all

Triggers = {
       [2][3] = {trigger}
                         }

making code much more readable.

But would it be possible to make Hollywood this way, as automatically defining table Triggers[2], since this is the problem basically that Triggers[2] is not defined when trying to define its index [3].

Posted: **Sun Jul 24, 2016 2:34 pm**

Sorry, don't understand what you want to reach.
Could you describe the problem a bit more?

Posted: **Sun Jul 24, 2016 4:36 pm**

This is at wishlist. Currently this is not possible, hence it is feature suggestion to Andreas, but thanks for trying to figure out a solution anyway.

Posted: **Sun Jul 24, 2016 11:35 pm**

This looks like much too specific for a VM feature... I doubt that there are other people who'd be looking for the very same thing

Posted: **Tue Jul 26, 2016 1:06 am**

Bugala wrote:This is at wishlist. Currently this is not possible, hence it is feature suggestion to Andreas,...

I did not even know about this method of addressing a table element.
Triggers = { [2] = { [3] = {trigger} }}

Thanks!

Posted: **Sat Jul 30, 2016 5:01 am**

It's all in the doc

Hollywood forums

possibility to use [1][2] in table definings

possibility to use [1][2] in table definings

Re: possibility to use [1][2] in table definings

Re: possibility to use [1][2] in table definings

Re: possibility to use [1][2] in table definings

Re: possibility to use [1][2] in table definings

Re: possibility to use [1][2] in table definings