Page 7 of 7
Re: 6.11 Development
Posted: Tue Jun 29, 2010 1:02 am
by PyTom
Just to bring people up to date on this - I think we're a few days away from the pre-release. Testing revealed two bugs and a performance issue that I'd like to try to address before people get to tear the thing apart.
6.11 is a huge release. I just checked, and over 10,000 lines of Python and Ren'Py code have been added, moved, or changed since 6.10.2d. (That's about a quarter of the size of Ren'Py, in total.) So it's no wonder that it's taking forever to get things tested and ready to go.
Re: 6.11 Development
Posted: Tue Jun 29, 2010 7:53 am
by jack_norton
Looks like this will be one of the biggest updates in Renpy history ?
Re: 6.11 Development
Posted: Fri Jul 02, 2010 12:00 am
by PyTom
So, just to touch base - I was testing on windows, getting ready for a release, and I noticed a little bit of pausing when showing a screen language screen. Out came the profiler, and I'm realizing the screen language interpreter function is taking 3ms - which is an eternity. So I'm going to be code-generating instead of interpreting code myself.
Might take a couple days to get this finished, but it will be worth it, I think.
Re: 6.11 Development
Posted: Sat Jul 17, 2010 3:51 am
by Ixis
PyTom wrote:So, just to touch base - I was testing on windows, getting ready for a release, and I noticed a little bit of pausing when showing a screen language screen. Out came the profiler, and I'm realizing the screen language interpreter function is taking 3ms - which is an eternity. So I'm going to be code-generating instead of interpreting code myself.
Might take a couple days to get this finished, but it will be worth it, I think.
Hey, anything to give me more time to finish some stuff I'm doing before applying a huge update!
Re: 6.11 Development
Posted: Wed Aug 25, 2010 10:27 pm
by Alter
PyTom wrote:Well, the general idea is that the ATL and Screen language will be the preferred way of doing things, in most cases...
Sorry for the stupid question, but how can I apply ATL on Screens? Can't understand where ATL statements should be inserted.
Also, didn't find it in documentation.
Need something like that, but applied on Screen
Code: Select all
show pic:
xalign 0.0 alpha 0.0
linear 1.0 xalign 0.5 alpha 1.0
Thanks.
Re: 6.11 Development
Posted: Wed Aug 25, 2010 10:41 pm
by PyTom
You define an ATL block separately, using a transform statement, and then apply it using an at property. For example:
Code: Select all
transform appear:
xalign 0.0 alpha 0.0
linear 1.0 xalign 0.5 alpha 1.0
screen my_button:
textbutton Test action Return() at appear
Re: 6.11 Development
Posted: Wed Aug 25, 2010 10:53 pm
by Alter
Thanks! ^^