- #HTML EMAIL LAYOUT NOT DISPLAYING CORRECTLY IN GMAIL CLIENT 720P#
- #HTML EMAIL LAYOUT NOT DISPLAYING CORRECTLY IN GMAIL CLIENT UPGRADE#
- #HTML EMAIL LAYOUT NOT DISPLAYING CORRECTLY IN GMAIL CLIENT CODE#
16:24 GMT-02:00 Dan Garner did have a thought - when you upgraded your layout did you select theġ080p resolution and is that the resolution you are testing in your player?
#HTML EMAIL LAYOUT NOT DISPLAYING CORRECTLY IN GMAIL CLIENT CODE#
On the clock, something changed in the CMS code to work or function Is perfect in the designer and the client.
#HTML EMAIL LAYOUT NOT DISPLAYING CORRECTLY IN GMAIL CLIENT 720P#
Upon upgrade, selecting the 720P resoluççao and checking the scale option Reply to this email directly or view it on GitHub I will import your layout and explore why the clock does not work. There may not be anything that can be doneĪbout this, other than to enable SENDFILE_MODE so that the web server is I will submit a bug for this - it sounds like a time out serving all of Size of the layout, rather than just taking the size of the designer). That is what the scale button is for (to scale the embedded output to the
#HTML EMAIL LAYOUT NOT DISPLAYING CORRECTLY IN GMAIL CLIENT UPGRADE#
Issue - in fact it is exactly what the "upgrade layout" message warns youīefore the upgrade it was incorrectly presented in the Layout Designer,Īfter the upgrade it was incorrectly presented in the Layout Designer. I understand exactly what you are seeing - but I don't think that is an The scale option should only affect the designer?Ībout the source of feed, there is nothing we can do to automatically The Scale option leaves the embeded with best view, but it is wrong in the The scale factor for most layouts will be 2.4 - but I don't see how we can set that automatically as it won't always be the case. Upgrading a Layout will not automatically try to adjust the items mentioned above - who is to say that changing the font size on the ticker from 20 to 48 is always the right thing to do? If we could always make that decision then we would have upgraded all layouts when the CMS upgrade occurred. Please also remember that Layouts are designed in their native resolution now - meaning 1920x1080 in this case - this means that only the designer is scaling, everything else is native resolution - which should make things much easier to design. I set mine to this and it looked good: style="height:350px width:245px border:0 " scrolling="no" The weather does need some adjustment to scale correctly in the designer and the layout - but I think that is because you have the width and height mixed up. With scale content ticked, it fits nicely in the designer and the client (without any adjustments, because the region is so small). Your clock embedded item doesn't work because you have the in the HTML section and you have EmbeddedInit declared twice (once in the HTML section and once in the script section). Pick one problem at a time (for example the ticker) and focus our attentions there.Before doing anything, export the layout and send.A screen shot of the player output (got this, attached).A screen shot of the Layout Designer before upgrading to 1.7, showing the ticker text.To better understand I think we need a few things: You can therefore "trickle" feed the changes across your network, or only adopt the new format for new layouts. Upgrading the Layout is optional and old layouts should continue playing as before without upgrading. When you are upgrading an old layout, Xibo automatically adjusts the region sizes and positions so they are stored using the new format, but there are simply too many unknowns to upgrade all of the region content. Previously they were stored at the designer resolution of 800 x 450, now they are stored at the display resolution of 1920 x 1080. There has been a massive change to the way the layouts are stored as explained in the release notes. The layout that sent me the UOL, I put the watch otherwise. On the clock, I did not understand the problem, cause the code worked before and not now. I think it would just multiply by a factor of upgrade to get the correct value of the font size. I believe the upgrade function could automatically increase these sources to perform the upgrade. In tests 1.7 RC1, increase needed to stay as before. The tickers used the font size 20 in the version 1.6.4. In the embedded player worked well, without making any changes, MAINTAINING cms in the scale option unchecked. Is there any option to tell the system which the default ZOOM and this adjustment in the layout designer to be representing reality? Only appears with the calendar date.Įmbedded in the designer, without scoring the scala option worked, but need to put in zoom = 1.6 to represent reality, but it was very large and had to use the browser zoom out. Dan, I downloaded the latest version of the GIT repository.Įrror-Clock function in Javascript has problem with the code we used previously.
0 kommentar(er)
