try_bottom for textbox

[GoogleCodeExporter]

Do we need a try_bottom for textbox?

"Sorry for brother you, Saluk. I just want to ask can you make textblock have 
try_bottom. i want to use textblock for both dual and single screen. if i use 
single screen textblock gone and it still at the bottom. and can you make 
rotate for 2d image have x and y axis not only z axis for next upcoming 
casemaker.
right now i making the fangame using your PyWright the coolest casemaker. to 
see my thread just click my signature image. btw do you are involved with 
dragon ball budokai x because the credit has your name."

Original issue reported on code.google.com by saluk64007@gmail.com on 31 Oct 2012 at 8:31

[GoogleCodeExporter]

What happens now:
 * No matter what, a textblock will be displayed
 * If it's on the top screen, it will be displayed in the same spot in both modes
 * If it's on the bottom screen, it will be shoved into the top screen in single mode
 * basically works as try_bottom if y>192

Issues:
 * textblock arguments are already messy
 * current textblock determines which screen on init with no configurability
 * cannot force textblock to only be visible on 2nd screen

Original comment by saluk64007@gmail.com on 31 Oct 2012 at 9:00

[GoogleCodeExporter]

Original comment by saluk64007@gmail.com on 16 Jan 2014 at 11:19

• Added labels: Component-Script

[GoogleCodeExporter]

I need a clean way for coders to define what needs to be on what screen. At the 
same time, it's annoying for coders, and for me, to always have to test all 
these different display types. The new small_bottom_screen mode is compatible 
with all games, requires no custom code, and looks almost as good as 
single_screen. So I'm not going to put more time into single screen errors 
right now.

Original comment by saluk64007@gmail.com on 9 Feb 2014 at 8:12

• Changed state: WontFix