Unknown warning in device console.

Solar2D General Questions/Discussion
#1

I was just testing my app on a device, and the app malfunctioned weirdly. It didn’t crash, but, for example, my score counting system didn’t work. This may well be due to some fault of mine, but I see that I got this warning in the console:

: Warning: Libinfo call to mDNSResponder on main thread

What is this warning? Could it possibly have any effect on the functioning of my app? I doubt it does, but I don’t know for sure.
Does anyone know anything about this? [import]uid: 38000 topic_id: 21386 reply_id: 321386[/import]

#2

I am not familiar with that error but if the score counting system doesn’t work then I’m guessing that may be the cause.

My suggestion would be to comment out anything related to score, build and test. If the error is gone you know you need to take a close look at how you’ve set up scoring and modify it.

Could you do this and let me know results? If the error persists I’d be happy to talk to some other members of the team and see if they have experienced it previously.

Peach :slight_smile: [import]uid: 52491 topic_id: 21386 reply_id: 84738[/import]

#3

Right now, it seems that the problem is caused by the line:
[lua]local widget = require’widget’[/lua].

My score system uses the following code:
[lua]local scoreText = display.newRetinaText( “Score: X ft”, 15, 5, “Palatino”, 22 )
group:insert(scoreText)
scoreText:setReferencePoint( display.TopLeftReferencePoint )
scoreText.x = 20
scoreText.y = 5 + display.screenOriginY
points = display.newRetinaText ( “Bonus Points: 0”, 140, 5, “Palatino”, 22 )
points:setReferencePoint( display.TopCenterReferencePoint )
points.x = 230
points.y = 5 + display.screenOriginY
group:insert(points)

local total = display.newRetinaText( “Total: 0”, 335, 5, “Palatino”, 22 )
group:insert(total)
total:setReferencePoint( display.TopRightReferencePoint )
total.x = 430
total.y = 5 + display.screenOriginY
gameTime = 1
totalScore = 1
function timerUpdate( event )
–print(“score updating”)
gameTime = gameTime+1
scoreText.text = “Score: “…gameTime…” ft”
totalScore = gameTime + score
storyboard.GameScore = totalScore
total.text = "Total: "…totalScore
end
scoreTimer = timer.performWithDelay(100, timerUpdate, 0)[/lua]
When I comment out the widget line, the scoring works fine. But when that line is not commented out, it the timer updating function won’t update.

Please help! I was planing on submitting this week, so I need to figure this out soon!
Thanks
Peter

EDIT: It works fine as long as the widget line hasn’t been called anytime before in the runtime of the app. So, if the widget line is commented out in the play screen, but was called earlier while on the menu screen, the score updating won’t work. [import]uid: 38000 topic_id: 21386 reply_id: 84817[/import]

#4

By the way, it seems like the warning in the console was totally unrelated. It only appears once in a while, and doesn’t seem to affect the app. [import]uid: 38000 topic_id: 21386 reply_id: 84818[/import]

#5

I also just found another problem that occurs if I have previously used the widget line. I have a store page with description text that should update when one of my item buttons is pressed, but if the widget line has been called, those don’t work. I might just have to switch my app back to ui.lua for my buttons for now if this won’t get fixed soon, but I hope I won’t have to.
Does anyone know of a ui.lua version without package.seeal? That was the biggest reason I switched to widget - I’m under the assumption that the widget library is more efficient. Is that correct? [import]uid: 38000 topic_id: 21386 reply_id: 84825[/import]

#6

Apologies, we have a time difference.

That does sound very odd - would you be able to file a bug report with a sample to run, please? [import]uid: 52491 topic_id: 21386 reply_id: 84885[/import]

#7

I’ll do that. [import]uid: 38000 topic_id: 21386 reply_id: 85048[/import]

#8

After some more testing, I see that it seems to cause the “text” property of display.newRetinaText to not work. I also see that the “text” property doesn’t work in other places in my app, after loading the widget library. Do you have any idea why that may be? Could that have something to do with the widget library?
(I haven’t submitted a bug yet, especially since I might be on to something)
Thanks for your help!
Peter [import]uid: 38000 topic_id: 21386 reply_id: 85052[/import]

#9

OK! I just got it working by using object:setText() instead of the ‘text’ property! I’m not exactly sure why the property didn’t work, but it does’t really matter too much. (However, I would recommend mentioning this in the docs, or just depreciate the ‘text’ property to read-only.)
Thanks for all your help peach!
Peter [import]uid: 38000 topic_id: 21386 reply_id: 85084[/import]

#10

Stupid time difference! Sometimes it is convenient and lines things up well, other times like this I get back and feel bad I’ve missed what is going on. (I’d never leave the forum if it were up to me ;))

I’m very happy to hear you got this resolved although you’re right, this is worth mentioning somewhere - would you perhaps be able to submit a bug report outlining it? It may be something better addressed than avoided. (I’m not the one to make that call.)

Peach :slight_smile: [import]uid: 52491 topic_id: 21386 reply_id: 85121[/import]