display.newText bug

Other
#1

Version 3055 has a “bug” with text objects (this may have been introduced in version 3052 as that had changes in this area) and it is very inconvenient.

For example this code no longer works

local aVar = 100 display.newText({text = aVar, x = 100, y = 100, width = 100, font = "arial", fontSize = 12, align = "left"})

and now throws an error

ERROR: display.newText() invalid 'text' parameter (expected string but got number)

I cannot think of one number that cannot be represented as a string so why force developers to coerce all our numbers into strings to be displayed as text objects?

It is such a common use case for games to display numerical data.  Please revert this change.

Thanks

Adrian

#2

Gotta file a bug man:  https://developer.coronalabs.com/content/bug-submission

They don’t really watch for bugs in the forums.

PS - It is cool to make a post and file a bug too however.  That way others know you’ve done it and don’t file their own.

#3

I’m not sure bug reporting is working…  I get no tracking number or email confirmation.  It just says this…

Corona Issue/Bug Submission

Thank you for your submission. We will do our best to evaluate your case and respond as quickly as possible.

Go back to the form

#4

I’ll ask around (I’m not an employee, but I know a few doors to knock on).

#5

Cheers Ed.  Rolled back to 3049 and things work as expected

#6

We do have a problem with our bug reporting form and the fix is in testing. For now, please email support@coronalabs.com, attach your .zip file with your demo project to the email and put in all the content you would have put into the forum into the email.

Thanks

Rob

#7

Email sent and 2/3 days still later zero response… yet another daily build has managed to ship?  How are devs supposed to know if the bug has been fixed?

Ticket is #8239870

#8

Not to be difficult here, but the bug didn’t get into our system until yesterday morning. It will take a bit more time before this gets looked at and assigned to an engineer. 

Rob

#9

Hi @adrianm, I asked the engineers to directly look into this. Thanks for flagging it.

Brent

#10

This issue should be fixed in daily build 3059 or later.

Take care,

Brent

#11

Cheers Brent… Try not to break core functionality again :wink:

#12

Gotta file a bug man:  https://developer.coronalabs.com/content/bug-submission

They don’t really watch for bugs in the forums.

PS - It is cool to make a post and file a bug too however.  That way others know you’ve done it and don’t file their own.

#13

I’m not sure bug reporting is working…  I get no tracking number or email confirmation.  It just says this…

Corona Issue/Bug Submission

Thank you for your submission. We will do our best to evaluate your case and respond as quickly as possible.

Go back to the form

#14

I’ll ask around (I’m not an employee, but I know a few doors to knock on).

#15

Cheers Ed.  Rolled back to 3049 and things work as expected

#16

We do have a problem with our bug reporting form and the fix is in testing. For now, please email support@coronalabs.com, attach your .zip file with your demo project to the email and put in all the content you would have put into the forum into the email.

Thanks

Rob

#17

Email sent and 2/3 days still later zero response… yet another daily build has managed to ship?  How are devs supposed to know if the bug has been fixed?

Ticket is #8239870

#18

Not to be difficult here, but the bug didn’t get into our system until yesterday morning. It will take a bit more time before this gets looked at and assigned to an engineer. 

Rob

#19

Hi @adrianm, I asked the engineers to directly look into this. Thanks for flagging it.

Brent

#20

This issue should be fixed in daily build 3059 or later.

Take care,

Brent