Hi.

Here some issues I found with the local web server.

1. I find it's best to leave the local web server in an inactive state when
clicking Run to ensure that all changes made to the form(s) are picked up
and displayed correctly. If the server is left running it seems to ignore
recent changes and only shows what appears to be cached data. This doesn't
happen straight away but starts to occur as more controls are added.
Particularly noticable when multiple forms are involved.

2. Would like to see a full-screen mode for the local browser when clicking
Run.

Thanks.

--
Rick

Rick,

<< 1. I find it's best to leave the local web server in an inactive state
when clicking Run to ensure that all changes made to the form(s) are picked
up and displayed correctly. If the server is left running it seems to ignore
recent changes and only shows what appears to be cached data. This doesn't
happen straight away but starts to occur as more controls are added.
Particularly noticable when multiple forms are involved. >>

This is a bug, and has been fixed already.  When the help browser was
included, the embedded IE seems to trigger additional navigations to
"about:blank" that screwed up the existing web browser handling code.

<< 2. Would like to see a full-screen mode for the local browser when
clicking Run. >>

Noted.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:16D6BD1F-8E5F-4459-94C8-193BF0EFE83B@news.elevatesoft.com...
>
> << 1. I find it's best to leave the local web server in an inactive state
> when clicking Run to ensure that all changes made to the form(s) are
> picked up and displayed correctly. If the server is left running it seems
> to ignore recent changes and only shows what appears to be cached data.
> This doesn't happen straight away but starts to occur as more controls are
> added. Particularly noticable when multiple forms are involved. >>
>
> This is a bug, and has been fixed already.  When the help browser was
> included, the embedded IE seems to trigger additional navigations to
> "about:blank" that screwed up the existing web browser handling code.
>
>

Tim, was this issue with the local server supposed to be fixed in the May
3rd build? I'm still experiencing the problem.

--
Rick

Rick,

<< Tim, was this issue with the local server supposed to be fixed in the May
3rd build? I'm still experiencing the problem. >>

It's fixed, so I'm not sure what you're seeing.

Anyone else still seeing this ?

Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:F354D063-C38D-4713-A39E-8169B5611CD3@news.elevatesoft.com...
> << Tim, was this issue with the local server supposed to be fixed in the
> May 3rd build? I'm still experiencing the problem. >>
>
> It's fixed, so I'm not sure what you're seeing.
>
> Anyone else still seeing this ?
>

Tim, this is now fixed in the June 28 build. Continually running the
internal web server appears to no longer cache pages incorrectly.

Thanks.

--
Rick