-
All my fonts got bigger… !!!
-
following lo longer work
// mainLayout.dhxWins.enableAutoViewport(false);
// mainLayout.dhxWins.attachViewportTo(mainLayout.cells(“a”));
// mainLayout.dhxWins.setImagePath(imgPath);
HELP!!!
Hi
-
What exactly?
We increased some fonst and spaces, but what exactly don’t you want to use? -
Read docs carefully, please
enableAutoViewport() - is deprecated
attachViewportTo(mainLayout.cells(“a”).cell);
setImagePath() - is deprecated
Hy Darla!
-
My problem is that I have a project with about 60 .js files, opening grids, lists, windows, etc… and now all the fonts are too big, the info doesn’t fit in the columns, etc…
How can I get back the font sizes of the previous version?? -
I’m not too sure about what you are telling me with your example “attachViewportTo(mainLayout.cells(“a”)”
- We need a direct link to see your application - we will try to suggest you something (it will be better if you open ticket if you have PRO)
- Have you try it?
[code] myLayout = new dhtmlXLayoutObject(document.body, “2U”);
myLayout.cells(“b”).cell.style.backgroundColor = “#00CED1”;
dhxWins = new dhtmlXWindows();
dhxWins.attachViewportTo(myLayout.cells(“b”).cell);
w1 = dhxWins.createWindow("w1", 420, 65, 320, 200);
w1.center();[/code]When you use it the way it was recommended in previous version:
dhxLayout.dhxWins.attachViewportTo(dhxLayout.cells(“a”).cell);
and you have:
dhxLayout.attachFooter(“footerDiv”)
the cell a will be stretched a little. Viewport will work but layout will go on the footer.
You can check it here: dev.esos.net.pl/test
Tested on Chrome and FF.
I hope to explain my problem with a very simple example:
These are two screenshots of the same, very carefully designed form (it took about 2 days).
As you see in “example previous” all the text fits nicely and so do the buttons
on “example V4” instead, everything overflows, to the point that the form itself needs to be scrolled.
WHAT is an easy fix for this…Is it just a template problem? The project has about 200 forms, I am NOT going through all of them!!!
fdl333
If you use the PRO Edition and you have active support subscribtion, please create a ticket in the online support system and link to this topic.
klysiak
How can we test it? Do we need to login? We can’t see any dhtmlx windows…
It’s an enormous project… you’re welcome to login if you wish… or I can just do a simplified version… the only difference between these two samples is the version of DHTMLX behind!..
I though maybe there was a nice simple global parameter that would reset the fonts to the sizes they were before v4!!!
Hi
the simplest solution is to add some overriding css rules for form and grid. if you 're interested - please send to support@dhtmlx.com email with:
- separate demos where grid and form used, with a struct exactly like your app has
- screenshots to compare 3.6 and 4.x versions (to know desired height)
several forms will enough, please make sure you used thye same types of items in a demo like in your real app used.
then you will get from our support team updated demo with:
- css rules with comments and explanations where to change and what effect will (i.e. you will able to change manualy)
- js changes if required (for example grid needs to know row height for smart rendering mode, are you using it?)
Windows are not neccessary. Just look to the bottom and see that BleskSoft footer is like on the attached scrren (incorrect_footer) and when I remove the attachViewport line the second screen will be, and this one is correct.
Anyone, anything about it?
We need more information, as Andrei wrote. Picture is not enough
Daria,
the question is that when I use attachViewPort to layout’s cell (
dhxLayout.dhxWins.attachViewportTo(dhxLayout.cells("a").cell);
) - the cell exceeds its normal size. When I attach the footer, the cell of the layout is on this footer.
Without attachViewPort same cell behaves correctly.
You can see both of the behaviours on the following pages:
http://dev.esos.net.pl/test/worksbad - incorrect behaviour
http://dev.esos.net.pl/test/worksgood - correct behaviour
The only difference between them is this line:
dhxLayout.dhxWins.attachViewportTo(dhxLayout.cells("a").cell);Andrei,
in the demo you gave the windows’ viewport is attached to a div object that is attached to the layout’s cell. What is the sollution when I attach grid to the cell and still want to attach viewport to the same cell?
all is possible 
[code]// init layout
var myLayout = new dhtmlXLayoutObject({
parent: “layoutObj”,
pattern: “3L”
});
// first attach grid
var myGrid = myLayout.cells(“a”).attachGrid();
myGrid.setImagePath(“path/to/imgs/”);
myGrid.loadXML(“some_data.xml”);
// then init windows
var dhxWins = new dhtmlXWindows(); // or use existnig myLayout.dhxWins
// and attach viewport to grid’s parent container
dhxWins.attachViewportTo(myGrid.entBox);[/code]
Andrei, in the scenario you described I used dhxLayout.dhxWins object like in this link:
http://dev.esos.net.pl/test/worksgood - this time does not work good 
Unfortunately it causes the same misbehaviour of the Footer as previously
Besides now, when I added toolbar the Viewport is only the size of the grid, not the whole Layout’s Cell.
.
I checked that this happens on Windows machines. On MacOS I cannot see the issue.
I use Win 7 with Chrome and Win 8.1 with Chrome and Internet Explorer.
You asked for grid - you got it
please create complete demo and send it to support@dhtmlx.com (of if std version like in link - you can attach it here). also cerate step-by-step description of awaited and current behaviour. I will add corresponding changes into your demo.
Andrei,
complete demo available under the following link:
http://dev.esos.net.pl/test/worksbad
Please click on ‘window’ button - it will open the window. It’s viewport is attached to layout’s cell.
Please notice what happens with the page footer - it appears on the grid.
Additional issue is that when the viewport is attached strange things happen with grid reload and progress action of the cell. To see the result close the opened window.
When we remove viewprot attaching -all works correctly - except that window can be maximized to full browser size.
http://dev.esos.net.pl/test/worksgood
I tried your suggestion with attaching viewport to grid - it causes exactly same issue.