Hello Bruceee

Thank you for your reply.

Kind Regards
Ricardo

Just converted my existing web site created from the unstable Web Easy software to SiteSpinner Pro.
Transistion went easily. Some quirky issues with Text placement. (does not shoe the same in preview mode compared to the editor view). But the site is up and running. Great software. (Site is at
http://godisareality.com)

Last post had bad link. it is http://godisareality.com

- Frankie

Hi Derry,
I tried the free trial and see one bug. As I reported in Report suspected bugs, in SS when you cut multiple include objects it cuts them on all pages. In your new version, it cuts them on every page except the one you were trying to cut them on. Still, if I had the money I would buy SSPro today. Y'all do great work over there at VM.
Dan

Hi Dan,

This has been forwarded off to the bug swatters to look into.

Hello Derry,

No bugs to report (I think) with SS Pro, but just a couple of suggestions.

Maybe the tutorial on Behaviours, Sound, Actions etc could be looked at. I tried and tried to get a sound to play when an object became visible. I followed the tutorial religiously several times to no avail. I also tried the same methods in WE which still wouldn't work. That's what led me to believe that it is me (not comprehending the tutorial correctly) and not the program.

In the end, I gave up and achieved the result that I wanted with a few javascript lines of my own.

The other point I would like to bring up (which I also mentioned in a recent post elsewhere on this forum) is that all VM products add an extra letter to the front of an object's name when published.

For example, O for object, G for geography, S for sound etc, is added to the front of the objects name or ID when published.

This becomes very confusing when trying to refer to an object with code or script.

When you open an objects editor, it displays it's name without the leading letter, but when published, myObject becomes OmyObject. So, any code or script especially written to refer to myObject will fail.

I can understand the reasoning for the publishing process to do this, but it would be very helpful if the the final SS Pro could eliminate this problem.

Regards,
Terry