weathereffect handle loading

[sethmachine]

Hi,

So I read through the return bug tutorial, and unfortunately it says this:

The rest can't since there are no hashtable functions for them. However, this system can help fix that problem, for most of them (except weathereffect and terraindeformation ):

I need to cast a handle id into a weathereffect . How can I do this?

 

[chobibo]

You can use a struct wrapper and use a hashtable for indexing, I guess.

struct
 weathereffect wfx
 terraindeformation tfx
endstruct

 

[Pharaoh_]

I'm not sure I got that right. You mean how can you save and load a weather effect through a hashtable?

I'd go with integers:

call SaveInteger (h, GetHandleId(r), 0, 'Rahr')

 

[chobibo]

I thought he meant the instance, I think I got it wrong too.

 

[sethmachine]

I want to save an instance of a weather effect so I can later destroy it.

i.e.

call RemoveWeatherEffect(newTable.weathereffect[...])

 

[Ceday]

I can think of only this solution now.First you need to create a global weathereffect variable with array,

globals
    weathereffect array WE
endglobals

Lets say you want to save a weather effect, instead of saving weather effect to hashtable directly, you will save its integer index of array.

 

[sethmachine]

This I thought about Ceday, but if I want to bind the weather effect to another handle, e.g. a rect, then an array would get an out of bounds error most likely.

Why? Well weather should easily be turned on and off in a rect, because it's a rect field/property (high level). I think it's silly there's no natives that remove weather from a rect and also clean up the old handle. Or maybe I just didn't find it/look hard enough?

i.e. this is what I wanted to do

call RemoveWeatherEffect(newTable.weathereffect[GetHandleId(myRect)])

I was thinking of creating a data structure like you mentioned to manage weather effects. My need is not huge anymore, since the solution I used retrieves the weather effect's instance by binding the rect handle to a struct.

 

[Ceday]

Not sure how table works, but this should with hashtables I think, you can convert.You won't need more than 8000 weathereffects anyway.

globals
    weathereffect array WEATHERS
    integer WEATHERINDEX = 0
endglobals

function SaveWeathereffect takes hashtable h, integer parent, integer child, weathereffect we returns nothing
    call SaveInteger(h, parent, child, WEATHERINDEX)
    set WEATHERS[WEATHERINDEX] = we
    set WEATHERINDEX = WEATHERINDEX + 1
endfunction

function LoadWeathereffect takes hashtable h, integer parent, integer child returns weathereffect
    return WEATHERS[LoadInteger(h, parent, child)]
endfunction

function DestroyWeathereffect takes hashtable h, integer parent, integer child returns nothing
    call RemoveWeatherEffect(LoadWeathereffect(h, parent, child))
endfunction

 

[WaterKnight]

Positive. You rarely need to actually save native handles in a hashtable, you can wrap the handle in a struct and then put the struct instance into the table.