Hi Kirk,

Thanks for your input.

We generate html on the fly, with data retrieved by queries on the database
I preferably don't want to store these temp html files on disk, ending up with 
cleaning up a lot of temp pages

As said, on 4Dv17R4 32-bit, WA SET PAGE CONTENT works fine with the embedded 
rendering engine (I also use css and javascript in the html)

Maybe you, or someone else, know of good reasons why this shouldn't work with 
Blink on 4Dv17 64-bit?

Gr,
Piotr


> Piotr,
> I use web areas quite a lot. WA SET PAGE CONTENT is tricky to make work if
> it's not initialized and generally not on the first page. I create pages on
> disk instead in a WA folder I setup in Resources. This also gives me a
> place to store Assets (CSS, JS, etc.) I use in the pages. Writing the pages
> to disk also lets you troubleshoot them in an actual browser which can be
> helpful during development. It also gives you the option to design a
> default page for your web areas.


Van: Piotr Chabot Stadhouders <[email protected]>
Verzonden: dinsdag 7 mei 2019 19:21
Aan: 4D iNUG Technical <[email protected]>
CC: Piotr Chabot Stadhouders <[email protected]>
Onderwerp: Webarea Embedded rendering engine show blank pages in 64-bit

Hi,

Tested on Windows

In 4Dv17R4 32-bit I have some html pages that are shown in a Webarea
Because I need "Access 4D methods", I use the embedded rendering engine
Also, I like to use the embedded rendering engine in 64-bit because of Blink

However, when using embedded rendering engine, the pages (that work in v17R4 
32-bit) don't show in 4Dv17R5 64-bit
When NOT using the embedded rendering engine the pages show up, but I can't use 
the "Access 4D methods"

What could be the problem?

Thanks,
Piotr

**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to