If you have a larger width in the embed tag, you can test an app in a
larger canvas area than the canvas declares. It is likely not
intentional, but it is very useful. I often develop small LZX apps
embedded in a website, but for testing I embed them in larger area of
test files. It is good that the canvas stays the same size, so the
app isn't distorted when I'm debugging -- the larger debugger is key.
Sarah
On Jun 22, 2009, at 12:39 PM, P T Withington wrote:
I'm not sure what you are asking. If you make the debugger wider
than the canvas, doesn't it just get clipped? How is that useful?
On 2009-06-21, at 17:57EDT, Sarah Allen wrote:
I'd like to change this line in debugger.lzx:
super.setAttribute('width', Math.max( 170 , Math.min( w ,
canvas.width) ) );
to
super.setAttribute('width', Math.max( 170 , w ) );
I've done this locally, since I am working with a somewhat narrow
video player and I just stick it into a test html with a larger
width than is defined on teh canvas, so it looks just like it does
on the real site, but I can develop with a larger debugger window.
If no one objects (and someone else approves) I'll file a bug and
check it in. (I can also do the same for the height although it is
not as important)
Thanks,
Sarah
http://www.ultrasaurus.com
