Lightning Heroes

Every slice always has a parent. lt is impossible for a slice not to have a parent. By default, if you have not manually patented a slice, it's parent will be the sprite layer.

All of the slices in a collection are children of a container



the above example frees the entire collection.

As for the rectangle that won't move, can I see a code example?

Oh, I didn't know freeing slices worked with collections already.

As for the rectangle,


That is really absolutely all that's going on. No loops, no conditions, nothing fancy. I've tried the same thing with sprites and text and they both worked perfectly, I see no reason why the rectangle would be of an exception. But it is.

Can you export the slice collection to a file and send it to me?

Also, I am curious what happens if you do this:

I'll need your E-Mail to send you the slices. (Yes, I'm really THAT lazy. :p )

I tried the show value command, and It did indeed change. So i'm assuming everything's working fine but for some reason the graphics aren't updating to show the box's new position?

Edit: I changed from -50 to -60, and it looks like It's creating a new slice in the new position on top of the old one, which is why It looked like it wasn't moving. ( The portrait hid the borders when it was at -50)

Free slice (Collection) Did not free the collection. I'm just curious, but has anybody else had any of these problems?

did you use the collection ID number? That won't work. If you used the variable that holds the return value from "load slice collection" that should work.

No, I used the variable.

There's another problem I'm having, too: Whenever I use a door, or teleport to map 7 from map 8, the screen becomes completely black. But the menu still looks fine, and opening the map reveals that I am indeed at my target destination, and I can still move around. Prior te recently, doors worked absolutely fine. I still need to test it, but I think using the door via scripting's presenting the problem, and if I used it manually It should work fine.

Downloaded the demo yesterday. The maptiles are great.

---

<TheGiz> oh hai doggy, oh no that's the straw that broke tjhe came baclsb

Curious.

Here are some questions that might help me understand what is going on:

* What is the purpose of the slice collection you are loading?
* When exactly do you load it?
* What do you do with the slice collection while it is loaded?
* Why do you (want to) free the whole collection at once?
* When exactly do you attempt to free the collection?



Since you can still see the menu, I don't think this is related to the fade-out-fade-in of moving from map to map.

The tag debug screen (F10) will tell you what scripts are running. I am wondering if the map autorun for map 8 is interfering with the completion of the script that takes you from map 7 to map 8...

The slice collection is just something that I want to come up when the menu does, to show you your HP and MP without you needing to go to the status screen.

It's loaded on keypress esc, to go with the menu.

While It's loaded, It doesn't do anything.

I want to free it all at once, with the close menu prompt, so that it doesn't stay there when the menu's closed.



The F10 screen says the only running script is the map autorun scrript. The autorun script is a while loop that I use to get the clouds scrolling across the map. The script also loads the proper palette for that map.

If the While loop is really stopping the transition, would simply walking the player to the door fix the problem?

That sounds pretty simple.

I am wondering if the slice handle that you are getting from the "load slice collection" call is getting clobbered somehow... Try this



And let me know if you see the same value right after loading the collection and right before freeing it.

Oh, also it would be helpful to know if you are reparenting any slices, and if so which ones and why.



In the script that causes you to use the door from map 7 to map 8, is anything supposed to happen after the "use door" command? If so, the while loop would be preventing it from happening.

Actually, if you can spare one of your timers, you can eliminate your loop entirely.




The above example uses timer#5 to repeat scroll clouds script once every tick without blocking other scripts until you leave map 8.

How exactly would I move clouds? For the While loop all I did was set the parent's X/Y position and then increment the variables I used. For the timer, this isn't working, and it's slowing down the game to about 13 FPS.

The script doesn't have anything happening after using the door, either. Although I certainly plan on adding things, so sticking with the timer's best.

For the Values of the collection, It's definitely getting clobbered. It opens up as a fairly random number, and increases by set increments every time I close and re-open it.

Can I see the whole code of the while loop in the map autorun on map 8?

As for the collection, is it possible that you might accidentally be loading the collection twice? Then the second copy would be unloaded, but it would look like nothing happened because the first copy is still there.

It's very possible that I could be loading the collection twice. It's summoned on keypress esc, and because that's what you use to close the menus, wouldn't it be opening it again?

But the problem is, when I first started getting this problem, I tried assigning closing the interface to a menu item, and it still wouldn't unload. I'll try again, to be sure, but even if it is being summoned twice, I'm not sure if that's the whole problem. If it is, though, would it be possible to just free it twice? I did try that and it said it was already deleted.

As for seeing the while loop; I'll put it up when I get to re-writing it.

The "trace" command can be even more useful than the "show value" command in situations like this. Trace a string right after the "load slicde collection" command, and then check your g_debug.txt file to see how many times it happened.



That can't work if both handles are getting stored in the same variable. The second handle would clobber the first.