display.newImage() resizes images larger than the screen dimensions?!

Solar2D General Questions/Discussion
#1

I have an image that is 1743x890 pixels that I’m going to use as a moving backdrop…but after calling display.newImage() I was surprised to find that it had been resized to 626x320! 2 questions:

  1. Is there any way around this behavior in Corona?
  2. Why is this the behavior?

thanks
[import]uid: 4044 topic_id: 530 reply_id: 300530[/import]

#2

YIKES ! Bug !

We are going to be adding tiling support in 1.2.

One way you can do it is by breaking up the image into 320*480 regions and load on demand. (or load them ahead and just moved them into place).

we are thinking of doing

display.newImage(“myImage.png”,0,0,true) last parameter here would be scale to screen size or not.

c [import]uid: 24 topic_id: 530 reply_id: 1061[/import]

#3

thanks for the response…yeah as a workaround i just settled for breaking the image up into 320x480 regions and moving them into place… [import]uid: 4044 topic_id: 530 reply_id: 1062[/import]

#4

make sure not to load them all at once and dispose what you don’t use as the open gl texture buffer will get taxed and consume memory.

C [import]uid: 24 topic_id: 530 reply_id: 1063[/import]

#5

thanks for the tip! [import]uid: 4044 topic_id: 530 reply_id: 1069[/import]

#6

hey, I just ran into this issue also, by any chance, has it been addressed yet?

thanks [import]uid: 10767 topic_id: 530 reply_id: 11141[/import]

#7

hi ansca,

please do you think you could expand on “tiling support”? … as you may know Graham has been working on a tilemap parser but the whole display routine method hasn’t been finalized yet. It would be good to know what features are coming so that the developers here can concentrate on elements that won’t end up part of Corona API anyway.

Or is it a suprise? :wink:

thanks
J [import]uid: 6645 topic_id: 530 reply_id: 11143[/import]