Futuremark SystemInfo

What's new in this version:

Color picker:
Picking a color from the screen:
- We had to change how the picking a color from the screen works, so that the feature works with floating windows
- Until now, the screen picker was activated by clicking on the icon and then moving the cursor over the Pinegrow window and then clicking to confirm the selection
- Now, the icon is dragged over the Pinegrow window and releasing the mouse will confirm the selection

Using the system color picker:
- Clicking on the color button next to the Picker icon opens up the system color picker

CSS Grid Editor input validation:
- CSS Grid editor now checks the syntax of grid properties. It caches common error like missing “(“ and “)” characters, wrong units and so on
- Only valid values are stored into CSS rules

Attribute editor:
- The element Attribute editor now supports editing values that contain JSON code, for example … Pinegrow will automatically use the right quote for the attribute in HTML: ‘ if the value contains “ and “ for all other cases

More resilient stylesheet loading:
- A lot of templates and projects out there in the real world contain broken code. Browsers are designed to work around such errors instead of complaining about them
- Pinegrow is more sensitive by design, because the goal is to notice and fix errors during development
- Still, we often get support requests with issues that are caused by such errors. One recent case involved a template with a stylesheet that imported itself. Pinegrow now detects and survives such situations
- On a similar note, we also see a lot commercial templates that are loaded with 10s of Javascript plugins. That can easily lead to performance issues when editing such projects in Pinegrow
- One solution is to disable Javascript while editing in Pinegrow, but then you’re often stuck with poorly implemented loaders that rely on Javascript to be cleared from the screen
- That actually makes Pinegrow a good tool for checking how projects behave in various sub-optimal environments, for example in browsers without Javascript

WordPress Theme Builder:
- Apply Master page command takes the current page, opens its master page and applies any changes to areas outside of the Site content
- A while ago we added the “Apply master page to all open files” that does this for all open pages
- Still, on larger projects with multiple templates and potentially multiple master pages, doing that is cumbersome. The easiest way is to open all template files and then run “Apply master page to all open files”

Now, we added two more options:
- Apply master pages to the whole project will go through all template files in the project and apply their respective master pages to them
- Apply master page to related files will do the same but only for project files that use the current page as their master page