Lemma Soft Forums

Np, I came into this relatively recently and am learning better ways of doing things every day, mostly from seeing good examples lying around.

That's likely it, a label is a label, and a labeled menu is still a label. It's worth noting that in the code you posted, I don't see any reason for you to name the menus in the first place. You don't have to, and you don't seem to call them directly. You could maybe streamline it a bit like this: l...

Well, that's sort of plan B, the problem is that it would be a very big, complicated composite, since the shot would involve what are already complicated composites, and would need to duplicate several dozen variables just to store the alternate states to create that state. So figuring out a way to ...

I'm wondering if something is possible; Can you take a screenshot without actually showing the player that screen as it's taken? What I want to do is "build" a shot, with a given background, complex sprites, etc., exactly as if in normal gameplay, and then make a "permanent" saved image of that scen...

Interesting. The ones in question are all created at runtime, during the start label. I don't know the higher level stuff either, so maybe this would do nothing, but have you tried defining them using default? Like "default rovers = []"? That's how I define my lists and haven't noticed any issues y...

because we switched to a different condition, $ a = 1 will work again! so if you are not looking to reset two or three times in the row, you do not even need a second reset condition at all. Same thing counts for everything else but not really relevant (since pausing two times without resuming is m...

I've added new always_reset kwarg there but it's just for fun or in unlikely event that you wish to reset on every interaction. Proper way to cause resets is to add two different conditions that do the same reset effect and use them one after the other as required. Obviously if you change the condi...

On some more playing with it, it seems like maybe the buttons do the wrong things. I made the following test case: image test_case = DisplayableSwitcher(displayable={"test": "TestAnimatedImage"}, conditions=(("a == 0", ("test", )), ("a == 1", ("test", "reset")), ("a == 2", ("test", "pause")), ("a ==...

I am not sure that I follow :( Ok, basically, the code you wrote works 100% fine when I use it on your original examples. But take your original example, and take: image TestLC = LiveComposite( (100, 100), (0, 0), ConditionSwitch( "True", "test_case", ), #and then put THAT inside another LC. So if ...

Ok, after a great deal of trial and error, I've located the problem circumstance, but don't yet have a solution to it. The problem comes up when I am trying to use the surrounding LC with condition switches. Here is a simplified example: image TestLC = LiveComposite( (100,100), (0, 0), "LC1", (0, 0)...

Ok, I'm still troubleshooting. I loaded up your exact test case as you had it with the meows, and that did work just as you said, so it's something about the interaction of my images and your code that is causing issues. Now I'm going to try turning various bits of mine on and off and see what works...

No, in this case at least, the "images" are all just direct links to a png file, and they all display properly, move properly, do everything right except the "resume" function. I'll keep playing with it though, try to troubleshoot a case where it definitely does work or doesn't work. Don't worry abo...

It is working for me :) I actually expected some issues when thinking about the design but last version just worked for me without hiccups with new conditions added. This new testcase only has half second of movement in it, maybe you're clicking to continue when the movement is done? Try adding rep...

Wow, that was fast. I've got it tentatively working, doing what I'd intended. I need to play with it some more to figure out the best ways to apply it, but it's very cool. One minor issue, which may just require playing around with it, is that the pause function works, but the "resume from pause" th...

This will not work any longer. It could be a potential start point when looking into how option 2) could be achieved. You could look into variant 1), if you understand the Switcher I wrote, it shouldn't be hard to have it work of a local, easy to access scope, then everything could be declared as i...