All Answers

There is one small issue left: A large page seems to be automatically scrolled to the bottom of it at first load.
Can this be prevented or scrolled back to the top of the page by code ?

You are calling scrollTo on the wrong element. The window is the entire browser window. And document.body.scrollHeight is the height of the document body.

Please contact us directly at support@wisej.com.

Scrollbars and the other properties work at design time too. You can place controls anywhere outside of the page and get the scrollbars.

Wisej controls are HTML widgets. There is no drawing to bitmap supported by any browser.

You can try the Html2Canvas extension. It lets you “capture” an image rendering of a specific control or of the entire page. It also works with async code.

Thank you very much for your answer Luca. Setting AutoScroll to True does what I need.
The only open question is how pages with a large height can be designed in the VisualStudio designer at best ?
I can find no possibility to get scrollbars displayed to scroll down or set the height for a page…

Wisej.Web.Page fills the browser. The content can be much larger. Set AutoScroll to true. You can also use AutoScrollMargin to create a blank bottom, right area when scrolling, it basically increases the “clearance”. And AutoScrollMinSize, which sets the minimum size of the content that triggers the scrollbars. There is also the ScrollBars property that lets you suppress either scrollbar.

The same properties are available for Panel, Forms, TabPage, UserControl, basically most containers can scroll or crop their internal content.

Hi Andrew,

Please have a look at Wisej-Extensions repository at GitHub and check whether the updated source code for GoogleMaps extension solves the issue you reported.

Hi Neil,

Feel free to fork Wisej-Extension repository at GitHub and submit a PR.

Have you had much luck with your service worker? Tested it out much?

I tried using a service worker with my WiseJ progressive web app, but it resulted in all of the files being cached permanently. Even when I would rebuild and publish to server, clear browser cache, etc, it will still show up as old versions of the file.  When not configured fully and properly, SW can be very problematic if you end up caching a resource that you then update. And your clients will be stuck on the old version until they unregister the faulty SW.

regards,

Andrew

Hi Mark,

Can you attach a sample?

Eccellent! I just do a test

Hi wzhou,

I can not reproduce. The Text property always show dark. What shows in gray is the Watermark. That’s the usual way of showing watermarks.

Hi Frank,

I tried disabling the “Edit and Continue” feature (on the debuggers tab of the main project properties) but this didn’t seem to do anything.

As a better work-around, I’ve taken and modified the code here:

https://stackoverflow.com/questions/4772092/starting-and-stopping-iis-express-programmatically

I’ve made a little .exe that closes the tray icon correctly by sending a WM_QUIT to that process and then kills the IISExpress worker process.

This works fine, and I no longer get an accumulation of ‘dead’ IIS tray icons either.

Probably do for now!

Regards,
Mark

I do a test with the responsive sample and PWA standard! Very good!!! Now don’t need to create native app 😀

Test pwa link https://www.eprime.it/pwa

Thanks

Regards

Cristian

Hi Guadalupe,

In our Wisej-Examples GitHub repository there is an example ComponentMixin that intends to show how to use mixins with custom appearance names for Component. For now it covers just the TreeNode case.

HTH

Hi Nic,

Thanks for your collaboration. I’ll have a look at the proposed changes.

Hi Tiago,

Regards,
Mark