Game Demo

[SilverWarior]

Just tested it out and I experienced the same problem of invisible borders being very close to starting position (not the whole window) same as de_jean_7777 reported. I'm using Google Chrome. But when I refreshed the web page using F5 key the invisible borders disappeared and I could move across the entire window.

After some further testing I noticed that I if I open your link using right click and "Open in new tab" I always end up with invisible borders. But if I open your link normally with left click (still opens a new tab for me) there aren't any invisible borders present.
So I'm assuming that when you open some link in new tab Chrome actually does some re sizing of web window area which then results in smaller game area being set as the web window dimensions are retrieved to quickly.

[czar]

Thanks for the feedback

I think it has to do with the resizing and when that takes place. I will see about fixing the demo.

[phibermon]

Resizing and window dimensions can be handled well across all the main browsers but it's my understanding that it still requires some javascript stub code in order to have predictable/repeatable behaviour across most browsers.

SMS I assume generates Javascript from pascal code - I'm also assuming that it has at least a rudimentary, static Javascript API - an ideal fix might come from altering the javascript API rather than coding around it in the pre-translation pascal code.

for a simple solution, you may want to run a timer that fires every second or so that manually queries and compares the screen dimensions. This way if they're not updated correctly in the normal chain of events on a given browser - it will 'correct' a moment later - this technique is evident on many sites that have elements that seem to be delayed in their re-positioning after a resize.

It's not problematically ideal - but it works - if you delay initial rendering (just black out the window) for a couple of seconds on load - then any 'ugly' snapping of dimensions will be hidden.

[czar]

The bug was my mistake not SMS. I set the width initially when the form object hadn't been finalized yet. I have moved on. I am converting some of our software to see what works and what is challenging.

Here is a conversion of a game I wrote in 2001 - I have updated it with some newer graphics. The gameplay still needs a bit of tweaking. Typically our games are designed to be completed in about 60-70 seconds.

http://numberworksnwords.com/cloud/j...aos/index.html