Ren'Py Gripes

[FragmentedBergyo]

I'll look into making the autohinter optional.

You're the best, and I appreciate it greatly, pytom!

[Shakezula]

Speaking of the documentation, I'm curious why the wiki was abandoned. Or can it still be updated by the community?

[PyTom]

The answer is that the wiki was a spam-magnet. The amount of time required to maintain the wiki exceeded the number of contributions by many orders of magnitude.

That being said, the docs are maintained on github, if you want to send me a pull request.

[Kia]

Hi Tom, I found a little glitch I think you want to look at ^_^ http://lemmasoft.renai.us/forums/viewto ... 67#p376467

[xela]

Maybe something can be done to allow this and similar functionality in screens without having to show/reshow the screen:

http://lemmasoft.renai.us/forums/viewto ... 15#p376481

===
We may be missing something but it is very difficult to use (in screens) ATL that have a beginning and end states and should not be interrupted by events. This is often very frustrating When ATL can be repeated or is an offset, it is easier but animations/filmstrips/atl image declarations and some transforms are close to impossible to work with without creating spaghetti code.

[Kia]

exactly what I was thinking, if only we had direct access to events in ATL life could be much easier. something like this.

Code: Select all

transform trans1:
    on hovStart:
        linear 1 alpha .5
    on fadeOut:
        linear 1 alpha .0
        action Start()
#....
    button:
        xysize (100, 50)
        hovered e("hovStart")
        action e("fadeOut")

but I never found the suggestion box to post it there >_<

[nyaatrap]

Speaking of ATL event, on activated (clicked) event is useful.
http://lemmasoft.renai.us/forums/viewto ... =8&t=32667
I've tried to implement it in the past, but it seems there is no simple way.

[Kinsman]

Would it be possible to create a renpy.return() statement, similar to the Python equivalents for jump and call?

Right now, you can fake it like this:

Code: Select all

    
label re_turn:
    $renpy.set_return_stack(renpy.get_return_stack()[:-1])
    return

label story:
    "Hello World."
    $renpy.call("re_turn")
    "You'll never see this line."
    return

But I worry about possible side effects in future versions.

[jack_norton]

Can't you just use renpy.pop_return() ?

[Kinsman]

Can't you just use renpy.pop_return() ?

Sorry no, pop_return() is just a synonym for pop_call().

[PyTom]

I added this as renpy.return_statement(), since return is a Python keyword and can't be used as a function name.

[Kinsman]

I added this as renpy.return_statement(), since return is a Python keyword and can't be used as a function name.

Thanks, Tom!
I really love Renpy's flexibility when it comes to more meta stuff.

[nyaatrap]

Passing arguments from the menu statement to the choice screen is possible? For example:

Code: Select all

label X:
    menu(argX=Z):
        ...........................

screen choice(items, argX=None):
    if argX=Z:
         ..................

Currently, I'm using store.variable to change the style of the choice menu, but it's not a smart way.

[xela]

Passing arguments from the menu statement to the choice screen is possible? For example:

Code: Select all

label X:
    menu(argX=Z):
        ...........................

screen choice(items, argX=None):
    if argX=Z:
         ..................

Currently, I'm using store.variable to change the style of the choice menu, but it's not a smart way.

I'd most definitely support adding more options and convenience for menus. Right now it's either working through globals or making own menu functions and creating them with python

[trooper6]

Passing arguments from the menu statement to the choice screen is possible? For example:

Code: Select all

label X:
    menu(argX=Z):
        ...........................

screen choice(items, argX=None):
    if argX=Z:
         ..................

Currently, I'm using store.variable to change the style of the choice menu, but it's not a smart way.

I'd most definitely support adding more options and convenience for menus. Right now it's either working through globals or making own menu functions and creating them with python

I'd also add in the ability to pass args, not only with the menu statement, but with the choices as well.

So for example,

Code: Select all

label x:
    menu meaningful:
        "What do you do?"
        "Kick the puppy."(moral=evil, clicked=False): 
            self.clicked=True (some way to change the args from in here would be good too).
            "You kick the puppy."
            jump meaningful
        "Save the puppy."(moral=good, clicked=False):
            self.clicked=True
            "You save the puppy.'
            jump meaningful
        "Notice the puppy and move on.":
            "There is a puppy...what does that have to do with saving the universe, you wonder?"

screen choice(items, *args):
        for label, action, chosen in items:
            if item.moral == evil:
                use the red text style
            if item.moral == good:
                use the blue text style
            if item.clicked is False:
                 show the item
            else:
                don't show the item

Something like this? Basically something to pass and play with args not only of the menu as a whole but also the individual choices themselves?