Tenorshare ReiBoot 歷史版本列表
更新時間：2020-10-12
更新細節：
What's new in this version:
Fixes the problem of low success rate of iTunes installation
更新時間：2020-10-12
更新細節：
更新時間：2020-09-27
更新細節：
更新時間：2020-09-25
更新細節：
What's new in this version:
- The setting menu bar has newly added guidelines for manually entering Recovery mode and DFU mode
- Enter DFU mode and change to countdown
- Added support for the latest iPad device models
更新時間：2020-09-25
更新細節：
更新時間：2020-09-25
更新細節：
What's new in this version:
PhpStorm 2020.2.2
- Fixed: No tests executed when running PHPUnit tests with WSL interpreter (WI-54615 +21)
- Fixed: Exception is thrown on editing code and warnings are stuck (WI-53963 +18)
- For remotes with github.com GitHub account now used and login is not requested (IDEA-248658 +15)
- DB connection configuration dialog takes into account ssh tunnel (IDEA-247277 +10)
- Fixed: File Watcher Not Running Properly for Sass @Use/@Forward (WEB-42904 +7)
- Custom inspection severities are now rendered correctly (WI-52633 +6)
- Fixed: Auto-completion for double underscore functions (WI-54771 +5)
- Fixed: Loading composer packages update availability runs forever with private repositories (WI-54105 +1)
- Extract class refactoring now makes properties typed for PHP > 7.4 (WI-53412)
PhpStorm 2020.2.1
- Change log not available for this version
PhpStorm 2020.2
- Change log not available for this version
PhpStorm 2020.1.4
- Fixed: Cannot open context menu in project view (IDEA-242047 +24)
- Fixed: IDE doesn’t start after update to 2020.2 EAP2 (202.5103.13) (IDEA-242552 +7)
PhpStorm 2020.1.3
- Change log not available for this version
PhpStorm 2020.1.2
WSL 2 Support:
- WSL 2 is a new version of the Windows Subsystem for Linux architecture that allows Windows to run Linux binaries. PhpStorm has supported WSL 1 since v2019.3, and now it supports WSL 2 as well
- You can run PhpStorm on a Windows machine and target Linux environments without any hassle
- To get started, make sure you have enabled WSL on your Windows 10 version 2004 machine, and also make sure you have the Linux distribution of your choice installed. See the installation guide.
- After installing PHP in your WSL environment, you’re ready to set up PhpStorm. Add a CLI interpreter under File | Settings | Languages & Frameworks | PHP
- Once this is done, you can use the specified interpreter to run and debug any scripts and to execute Composer commands, PHPUnit tests, and quality tools
- One thing that’s still missing is support for Docker via WSL 2
Other notable changes:
- Fixed: Idea freezes with AppleSystemUIFont when Event Log is opened (MultilineTreeCellRenderer takes a lot of time doing stringWidth)
- CSS/SCSS formatter need is now aware of CSS3 grid-layout properties
- Fixed: Some text in “IDE and Plugin Updates” popups in dark themes is gloom
- Fixed: Wrong project name and path when opening project with shell script
- Fixed: Scanning node_modules directory with many files freezes IDE on project open
- Fixed: Next/Previous occurrence actions don’t work when Find Usages is open and the focus is in the editor
- Navigate to File now honors the Sources directories first
- Fixed: High CPU usage on editing
- Fixed: Incorrect inspection for trait collision for PHP > 7.3
- Fixed: Memory leak / code analysis never finishes for a certain project
- Fixed: Fail to parse validation script output on reload php info for vagrant remote interpreter
PhpStorm 2020.1.1
Fixed:
- Find Usages does not prompt when method overrides/implements base method
- Can’t validate PHP XDebug >= 2.9 configuration
- Command Line Tools fails on PHP 7.4
- Broken update artisan commands for Tools based on Symfony console
- Matching braces highlighting is incorrect
- a pair of issues involving external tools
- Color customization for @param tag (WI-50427 +4) – the last missing part to disable PHPDoc highlighting if you didn’t like it
- We started to roll out the WSL 2 support (WI-51942), so if you are a Windows user, we’d be happy to hear your feedback
PhpStorm 2020.1
Out-of-the-box composer.json support:
- All dependency management actions are now available directly as you edit the composer.json file
- You can create a new file composer.json from the context menu or by pressing Ctrl(⌘)+N. The template of this file can be found in Preferences/Settings | Editor | File and Code Templates.
Add package as a dependency:
- To add a dependency, simply start typing a vendor and a package name, and PhpStorm will suggest appropriate options
- The version field will offer the available versions of this package. For now, you’ll have to add caret or other symbols for the version range manually, but in the next releases, we will implement this too.
- Autocompletion will also work if you need to specify the required version of PHP and extensions.
- In the popup for packages, you can find information from packagist.org about the number of downloads and stars. All the information about packages and their versions is taken from packagist.org and cached.
Install and update packages:
- If there is no composer.lock file and no packages are installed, PhpStorm will highlight the require and the require-dev section names. You can click the Install button in the toolbar above the editor. Or you can use the intention by pressing Alt(⌥)+Enter and choosing Install packages.
- And if only some of the packages are downloaded, PhpStorm will highlight those that are not yet installed. By pressing Alt(⌥)+Enter over them you can choose Update package or Update all packages.
- Next to the version requirement, the currently installed package version will be indicated in grey.
Navigate to files and folders:
- You probably know that with Ctrl(⌘)+Click or Ctrl(⌘)+B you can go to entity definition or search for usages
- In the composer.json it’ll work too. If you Ctrl(⌘)+Click a package, the corresponding directory will be highlighted in the Project Tree. And if it’s a file, then it will be opened in the editor.
- Ctrl(⌘)+Click or Ctrl(⌘)+B on any link in the composer.json will open it in your browser
Autocompletion in autoload(-dev):
- Autocompletion works for namespaces and folder paths based on information from classes and directory structure of the project
- [email protected]
- Ctrl(⌘)+Click and Ctrl(⌘)+B to navigate to files and folders also works here
Improvements for scripts:
- First of all, navigation to files/folders/methods also works. Secondly, aliases for commands are supported. And third, scripts can be run from the editor by pressing the gutter_play_tr button near the script name.
This automatically creates a Run configuration. It means that you can re-run the script by a shortcut Ctrl(⌃)+R, which is quite convenient for debugging:
Code Quality Tools:
- If there is a FriendsOfPHP/PHP-CS-Fixer in the dev dependencies, PhpStorm will check whether the corresponding inspection is enabled and if the ruleset is set. If not, you can call Alt(⌥)+Enter to fix it:
Improvements to PHP type inference:
- The type inference engine is the core of PhpStorm, and several noticeable changes were made to it
Highlighting redundant @var tags:
- Adding @var tags is a good way to suggest PhpStorm the variable’s type. But since we are constantly improving the type inference, some of such declarations may well be redundant because PhpStorm already knows the type. Such cases will be highlighted and they can be removed using the Alt(⌥)+Enter and “Remove @var” quick-fix.
- Tracking null types is a tough task, and there were places where PhpStorm failed. In 2020.1 PhpStorm knows when a variable can be null and when not. Check these examples.
Code Completion for an initialized array:
- Suppose you have an array with known elements, and later you try to iterate through it. The code completion didn’t work here before, because information about the type was lost. Now in 2020.1 everything works.
Code completion in array_map/filter:
- Now there is completion for array items in the body of the closures passed to array_map() and array_filter()
Code coverage with PCOV and PHPDBG:
- You can get a code coverage report by using Xdebug. But since it is primarily a debugger, it has a significant overhead. To speed up reporting of coverage, you can use lighter tools such as the krakjoe/pcov extension or PHPDBG which is built-in with PHP 5.6+.
Both are now supported in PhpStorm. You need to create a Run configuration for tests and select the desired coverage driver in the settings. And then run tests with coverage report by clicking run_coverage_tr:
- Read more about the differences in coverage reporting between Xdebug, PCOV, and phpdbg in README of PCOV
PHPUnit Toolbox:
- In the recently released PHPUnit 9, many features have been removed or declared obsolete. To speed up migration and prevent errors, we have added lots of inspections and quick-fixes.
- Also, you can now create a new test for a class very quickly by calling Alt(⌥)+Enter on the class declaration and selecting Create New PHP Test.
Metadata:
- Advanced Metadata allows you to provide PhpStorm with additional information about your project and thus improve code completion and inspections. For example, this feature is used in the Symfony plugin and in Laravel IDE Helper.
- A number of improvements for metadata have been added to PhpStorm 2020.1
- The parameter index in override, map, and type directives
Previously, it was possible to adjust the behavior of the first argument of functions using override(), map(), and type(). In PhpStorm 2020.1, you can now specify an arbitrary parameter index:
- If you’re trying to access properties through the magic __get() method, the information about the type is lost. You could use additional @var or @property tags, but that didn’t always work. Now you can specify everything through metadata.
Completion for keys to the objects implementing ArrayAccess:
- Metadata supported ArrayAccess objects, but only suggested the type of values. Now the available keys can also be autocompleted
Custom output points:
- PhpStorm considers functions like die() and exit() or throwing exceptions as terminating execution. But applications may have more complex exit points, for instance, a simple dd() or a trigger_error() with an E_USER_ERROR argument.
- In PhpStorm 2020.1, you can mark any functions as exit points and this will correct the control flow analysis accordingly
Icons for functions with changed behavior via metadata:
- Functions whose behavior was changed using override(), exitPoint(), or expectArguments() will now have an icon in the gutter. Clicking the icon will open the .phpstorm.meta.php file where the behavior was modified.
- You can hide these icons under Preferences/Settings | Editor | General | Gutter Icons
Machine Learning-assisted ranking for code completion:
- Ranking suggestions using machine learning makes it possible to sort the list of suggestions in a more optimal way
How to see ML in action?:
- By default, the ML-assisted ranking is disabled. We don’t want it to take our jobs! To enable it, go to Preferences/Settings | Editor | General | Code Completion and turn on two options: Rank completion suggestions based on Machine Learning and PHP.
- If you enable the option Show position changes in completion popup, then the autocompletion list will show how the order of items has changed
- We plan to prevent AI takeover to continue to work on this feature in the upcoming releases
New inspections:
- A private property can be replaced with a local variable
- The definition of a property will be highlighted if it is used in only one method and is overwritten immediately. In such cases, you can call the “Replace property with local variable” quick-fix with Alt(⌥)+Enter.
Unnecessary property initialization:
- Let’s assume that a private property has a default value in a class, but some other value is immediately assigned to the property in the constructor. In this case, the default value is redundant and only adds noise.
- Unused initializations will be highlighted and can be removed by using the “Remove redundant initializer” quick-fix with Alt(⌥)+Enter
- Change the property type according to the default value in PHP 7.4
- - [email protected]
- Redundant ternary operator:Phpstorm highlights trivial ternary expressions, and you can replace them with simpler ones using the Alt(⌥)+Enter quick-fix
- Using a pass-by-ref may have unexpected consequences, and this is one of the reasons Nikita Popov proposed to Allow explicit call-site pass-by-reference annotation in PHP.
- In the meantime, PhpStorm 2020.1 will highlight parameters that are declared as pass-by-ref but are not used as such. They can be safely removed with a quick-fix with Alt(⌥)+Enter.
The same will work for arrays with a pass-by-ref in foreach loops:
- Removing an unnecessary PHPDoc block that only has type declarations is now easy thanks to a corresponding quick-fix
- Note that by default the inspection is at the Info level, which means that it will not highlight anything. If you want redundant PHPDoc blocks to be highlighted, set the severity level for the Redundant PHPDoc comment inspection to Weak Warning or higher in Preferences/Settings | Editor | Inspections.
Updated “Move method” refactoring:
- Sometimes it makes sense to transfer a method to another class. If this method is used many times throughout the project codebase, PhpStorm can help you.
- Previously, it was necessary first to make the method static, and then to call another action to move a method. In PhpStorm 2020.1, the “Move method” refactoring is redesigned into one atomic action. Unnecessary operations and popups have been removed and everything is done in a single step.
- Put the cursor over the method and press F6 (or Ctrl(⌃)+T, 3). Then select a destination class and you’re done.
PHP Debug in HTTP Client:
- You no longer need to bother with parameters or install the extension in your browser to start debugging. All you need to do is create an HTTP request in an .http file and execute it by running the PHP Debug command, which is available under the Alt(⌥)+Enter menu, or by clicking the play icon gutter_play_tr. As a result, an XDEBUG_SESSION cookie will automatically be added to the request.
And a few more little things for PHP:
- @deprecated elements are displayed as strikethrough in the Structure tree view
- Ctrl(⌘)+F12
Lexer customization for Twig:
- Sometimes you may need to change the tag characters for Twig templates, for example if you are using Angular, which has the same syntax
- You can now do this under Preferences/Settings | Languages & Frameworks | PHP | Twig
IDE:
- Advanced spell checker and grammar corrector
- The Grazie plugin is included in PhpStorm out of the box. It checks your text not only for spelling errors, but for grammar and style errors, too. Grazie supports 16 languages, and all checks are performed locally without sending your data to third parties.
- By default, checks are enabled for text files
- You can also enable Grazie for all string literals, comments, PHPDoc blocks, and commit messages
- For PHP, you can turn Grazie on under Settings/Preferences | Editor | Proofreading | Grammar
LightEdit Mode:
- Sometimes you may need to quickly look through or fix a file. In these cases, opening a whole IDE for a single file seems like overkill, but you still want to make use of highlighting and other helpful features you are used to. That is precisely what LightEdit mode is here for.
- It works like this: if you open a file from the command line or OS context menu and PhpStorm is not running, the file will open in LightEdit. Note, though, that if a full-fledged instance of PhpStorm is active, the file will just open in it.
JetBrains Mono is now the default font:
Zen Mode:
- This mode combines Distraction Free and Fullscreen modes, allowing you to take a deep dive into your code without any distractions
- Enable it under View | Appearance | Enter Zen Mode
Split terminal sessions:
- Instead of opening new tabs and switching between them, you can now split the window and open several sessions in one tab. To do this, select Split Horizontally / Vertically from the context menu.
IntelliJ Light theme:
- The light theme has been updated. It is now unified to look the same on all operating systems, and its name has been changed to IntelliJ Light
Customization of the status bar:
- From the context menu, you can select which information to display on the status bar at the bottom right-hand corner of your IDE window
Configuration:
Unified SSH configuration:
- Previously, you had to reconfigure your SSH connection each time you reused it in the deployment, Remote interpreters, or SSH terminal
- You can now add or edit all SSH connections in a single place under Preferences/Settings | Tools | SSH Configurations and then use them wherever, and as often as, you need them.
- The path to IDE configs has changed;
- Previously, Run Configurations were stored in the .idea folder, which many people add to .gitignore in its entirety (there is a better alternative though). Now you can choose any location to save the Run configuration and share it with your teammates through your VCS. This can be especially convenient when onboarding new employees: pull the project, open it in PhpStorm, and run it with a single click.
- To do this, select the Store as project file option in the Run/Debug configuration dialog, and then click on the gear icon to select the desired path in the project.
- run-configurations_share
- Version Control
- New Commit tool window
- The Commit window is available in non-modal mode and is displayed on the left. This way, it does not keep you from viewing and working on other files while the commit is being prepared. This also allows more information about changes to be displayed on the screen.
- The new Commit tool window is enabled by default for new users but disabled for those who previously had PhpStorm installed.
- You are welcome to activate it with the option Use non-modal commit interface under Preferences / Settings | Version Control | Commit.
- commit_flow
- Improved Git branches workflow
- The current Git branch is specified in the bottom right corner of the IDE window. If you click on it, the window will open the VCS | Git | Branches dialog.
- We’ve added a search bar here. The Refresh button updates the list of remote branches. And we’ve added an indicator for each commit: incoming (blue) or outgoing (green).
- git_branches
- Installing Git from IDE
- When you clone an existing Git repository, PhpStorm will look for the Git executable on your machine, and will offer to download and set it up for you if the IDE can’t locate it.
- Reworked Interactive Rebase workflow
- Git Rebase allows you to rewrite commit history. Now you can quickly get rid of “temporary” commits, correct a message, or rearrange the order of the commits. Of course, you can do all this manually from the terminal, but in PhpStorm you can also see the content of the commit and the diffs.
- To start, you need to select the desired base commit in the commit history. Then select Interactively rebase from here from the context menu.
- git_rebase
- Database Tools
- PhpStorm includes almost all the features of DataGrip out of the box. You can check out What’s new in Database tools for an overview from our colleagues about its new features.
PhpStorm 2019.3.4
- Change log not available for this version
PhpStorm 2019.3.3
- Change log not available for this version
PhpStorm 2019.3.2
- DB Console: Execution of stored procedures
- Fixed: Customize Menus – Navigation Bar popup menu items are not saving
- Fixed: Switch tab shortcut skips one file with Tab limit = 1
- Fixed: Start tag has wrong closing tag
- Fixed: Unable to remove Services tool window from panel
- Select on Zerofill column
- Fixed: PHPUnit: Invocation with class name is deprecated
- Fixed: UnsupportedOperationException when trying to open Xdebug snapshot
- Fixed: PHP 7.4 fails on a quality tools due to the conflict with libraries (PHPMD)
PhpStorm 2019.3.1
- Change log not available for this version
PhpStorm 2019.3
- Change log not available for this version
PhpStorm 2019.2.5
- Change log not available for this version
PhpStorm 2019.2.4
- Change log not available for this version
PhpStorm 2019.2.3
- Change log not available for this version
PhpStorm 2019.2.2
- Change log not available for this version
PhpStorm 2019.2
- Change log not available for this version
PhpStorm 2019.1.3 Build 191.7479.51
Notable changes:
- Added support for AngularDart
- Fixed: Changes to my Environment Variables in Configurations aren’t saving
- Fixed: Cmd+E/Ctrl+E doesn’t work for iterating recent files after Recent/Recent edited files union
- Fixed: Pressing the down key in the floating navigation bar closing it, but should show siblings in a popup
- Added warning against usage of private fields in Angular Templates
- Fixed: Performance problem with suggestions and completion in project with redux-saga
JBR 8 was updated to v1.8.0_202-release-1483-b58:
- Fixed the issue with the IDE hanging after logging in on macOS
- Fixed the rotation of fonts with embedded bitmaps
PhpStorm 2019.1.2 Build 191.7141.52
Support Docker for Composer execution:
- The usage of containerized environments by PHP developers is steadily growing by roughly 12% each year – from 18% in 2017, to 30% in 2018, to 42% in 2019, according to The State of Developer Ecosystem Survey. While PhpStorm supports PHP interpreters via Docker and Docker-compose, it still had some parts missing. One of these is Composer integration. You needed a local PHP setup in order to run it. But it could be that this differs from the one you have in your containerized dev environment, or you might not even have a local PHP interpreter at all both of which might cause problems.
- In PhpStorm 2019.1.2, this is finally solved. You are now able to run Composer via any Docker image
- Under Preferences | Languages & Frameworks | PHP | Composer you can find a new Docker radio button option, where you’ll be able to configure the Docker server (this is not a PHP server), as well as provide an image, the Composer executable name, and the container options.
- This feature is a subset of a broader request to support Composer via any remote PHP interpreter (WI-23544). According to the survey and stats, the main use-case is Docker, which is why we have started with this first. We would like to hear from you on how you like the current implementation, then based on this feedback we will try to improve and expand it to the other use-cases
Support new format of Blade debug info:
- We’ve added support for debugging Blade templates in PhpStorm 2019.1. Due to a bug, the debug info format, which is needed for PhpStorm to map compiled files to original templates, since a change was made in Laravel 5.8.11. The current PhpStorm build brings debugging Blade templates experience back (WI-46191) for Laravel 5.8.11+
Other notable changes:
- Fixed: Open recent menu doesn’t display project group if any
- Fixed: Move Caret to Matching Brace moves to wrong position
- Fixed: Terminal tabs can’t be reordered
- Fixed: High CPU usage, code analysis never completes when resolving references from “reselect” module
- Fixed: JDK 11: Response handler doesn’t work (Nashorn is removed)
PhpStorm 2019.1.1 Build 191.6707.66
- Change log not available for this version
PhpStorm 2019.1 Build 191.6707.42
- Change log not available for this version
PhpStorm 2019.1 Build 191.4212.35
- Change log not available for this version
PhpStorm 2018.3.3 Build 183.5153.36
- Change log not available for this version
PhpStorm 2018.3.2 Build 183.4886.46
- In the second minor update for the PhpStorm 2018.3, we are happy to bring you DQL Autocompletion! The release also has some bug fixes and improvements for PHP and the Web, and takes on the latest improvements in IntelliJ Platform.
Autocompletion for DQL:
- In the recently released PhpStorm 2018.3, we introduced advanced support for Doctrine Query Language. Continuing to improve the DQL experience in PhpStorm, this time we give you autocompletion for classes and fields.
- It works the same way as autocompletion for PHP. You need to inject DQL language into a string and start typing. PhpStorm will suggest you to a way to complete your statements on the go.
- If you need to call autocompletion manually, just hit Ctrl+Space and see a list of suggestions popping up next to the caret.
- Autocompletion works with class names and fields, inside SELECT/UPDATE/INSERT/DELETE queries, with SQL function calls, and so on.
- We plan to improve the injection mechanism and work on other improvements. Please let us know how you like the DQL support and what you’d want to see improved.
Other updates worth noting:
- Fixed: IDE hangs when searching in Hebrew+English (IDEA-199367 +28)
- Fixed: MySQL datetime incorrectly shows (DBE-69 +21)
- Fixed: Editor Search/Replace and Find/Replace in Path: font for text input fields is too small (IDEA-106651 +20)
- Fixed: Project update over SSH fails if there are many repositories (IDEA-203005 +7)
- Fixed: IDE hangs indefinitely on PhpDoc auto-generation (WI-44525 +1)
PhpStorm 2018.3.1 Build 183.4588.67
- Change log not available for this version
PhpStorm 2018.3 Build 183.4284.150
- Change log not available for this version
PhpStorm 2018.2.4 Build 182.4505.42
Notable bug fixes:
- When working with tasks and contexts and switching between tasks, IDE will now restore VCS branch and workspace correctly (IDEA-184079 +21)
- Fixed in XML: IDE marks “Element is not allowed here” an Element which is allowed to configure (IDEA-195872 +18)
PhpStorm 2018.2.3 Build 182.4323.68
- This build delivers new features, bug fixes and improvements for PHP and the Web, and takes on the latest enhancements in IntelliJ Platform.
PHP 7.3 Support:
- The first release candidate of PHP 7.3 is already released. The GA of the new version of the PHP interpreter is expected somewhere in mid-December.
- PhpStorm is continuing to add support for new PHP features (WI-42883).
Support for list reference assignment:
- PHP 7.3 introduces the enhancement for list() construction, which allows using references
- You may use the short syntax [] as well
Support for literals as the first operand of instanceof:
- In PHP <7.3 this would cause the “instanceof expects an object instance, constant given” fatal error. In PHP 7.3, the result is always false.
Trailing comma in function calls:
- For a long time in PHP you could add a trailing comma in an array
- In PHP 7.3 it is possible to do same thing for function arguments list
- This works for method calls and closures as well
- This is especially handy when viewing diffs with every parameter located on a new line.
- Note that this only works for function calls, but not function definitions, so the following is not possible
Quick-fix for adding a missing extension to composer.json:
- In PhpStorm 2018.2 we’ve added the new Extension is missing in composer.json inspection. It detects the usages of functions, constants, and classes that rely on PHP extensions not currently listed in composer.json.
- Now, starting from 2018.2.3, you’ll be able to run a quick-fix for such issues: PhpStorm will add the corresponding extension record to composer.json for you.
DQL Support:
- We plan to fully support Doctrine Query Language (DQL) (WI-9948) in the upcoming PhpStorm 2018.3 major release. You may check out initial support in 2018.3 EAP. Meanwhile, in this release, injections of SQL inside text literals will be automatically disabled for strings with DQL identifiers. This will eliminate false positives and make your files clean from warnings.
Notable bug fixes and features worth mentioning:
- Fixed: LoginToGithub dialog invoked from CloneRepository dialog hides immediately
- Fixed: Vue.j SFC not resolving @ alias with @vue/cli 3 if vue is installed in a subfolder
- More options creating Angular Cli project
- Fixed: Cannot attach to remote nodejs after upgrade to 2018.2
PhpStorm 2018.2.2 Build 182.4129.45
Platform updates:
- The database tools now support ClickHouse out of the box
- Fixed a couple of performance issues related to VCS (file scanning)
Notable bug fixes and features worth mentioning:
- PHPUnit: rerun failed tests now works for “defined in configuration file” run configuration
- Debugging maximum simultaneous connection configuration setting is now set to 3 by default
- Fixed completion for interfaces
- Fixed “Deployed file is on server removed” stuck since update 2018.2
PhpStorm 2018.2.1 Build 182.3911.43
- Change log not available for this version
PhpStorm 2018.2 Build 182.3684.42
Completion:
Custom postfix completion templates:
- Postfix code completion has existed in PhpStorm since version 9, but only provided a limited number of predefined templates. PhpStorm 2018.2 takes postfix completion to the next level by allowing you to add custom postfix completion templates. Create templates to match your project and your personal coding style!
FQCN Completion:
- Completion now matches the namespace in addition to the element name. You don’t have to type or invoke completion for each part of IlluminateAuthEvents anymore – just type IAuE instead.
Refactorings:
Move Instance Method Refactoring:
- PhpStorm already the Pull Up/Push Down and Make Static/Move Static Method refactorings that help you move methods around. For handling the methods that cannot be made static or moved across the class hierarchy, PhpStorm 2018.2 introduces a refactoring that allows for moving an instance method to a parameter class or to a field class. Simply invoke the Move refactoring on a method declaration, and, if the new refactoring can be applied, you will see a dialog prompting you to choose the target class.
PHP Language:
Structural Search and Replace:
- In PhpStorm 2018.2, we’ve completely reworked Structural Search and Replace for PHP, which offers lots of new capabilities and greatly simplifies patterns creation. Now you can specify the type of Structural variable, which lets you, for example, find a call to the specific method where the first parameter is a string. You can use a simple pattern to find a foreach loop with an unconditional return statement, or even create your own inspection that will capture an unnecessarily double-quoted string, if your code style enforces this
Improved SQL Injections:
- In version 8, PhpStorm introduced basic support for string concatenations in Language Injections. The dynamic nature of the resulting strings and the strictness of the SQL parser caused a lot of false positive errors in SQL. In PhpStorm 2018.2, we’ve eliminated most such errors and introduced some new features, too. PhpStorm can now substitute the values of constants directly within the injected string, so you can run a query without copy-pasting their values. In addition, we’ve added support for SQL strings that use sprintf parameters
New Inspections and Quick Fixes:
PhpStorm 2018.2 delivers handy new inspections such as:
- Extension is missing in composer.json reports usages of classes/functions/constants from PHP extensions which are not specified in composer.json
- Non-canonical order of elements in PHPDoc reports tags such as @property, @param, @var, etc. that use a non-canonical order of elements e.g. name Type instead of Type name.
- Optional parameter before required parameter detects situations when an optional parameter appears before required parameters in a function/method declaration.
Web Technologies Support:
New JavaScript Intentions:
- To make you even more productive when working with JavaScript and TypeScript, PhpStorm has a bunch of new intentions that are available when you press Alt-Enter. Here are just some of them: Implement interface, Create derived class, Implement members of an interface or abstract class, Generate cases for switch, and Iterate with for..of.
Completion for events in Vue.js:
- In Vue templates, PhpStorm now provides code completion for events. Event names are suggested after v-on: or if you use the shorthand notation @event. There’s also code completion for event modifiers.
- As usual, all the features and improvements of WebStorm are available in PhpStorm, either out of the box or with free plugins available in the repository. Other noteworthy web-related features include TypeScript 2.9 and 3.0 support, the new Code Coverage feature that helps to find unused code, extract and convert React component refactoring, new integrations with Angular CLI, global file watchers, rerun failed tests and other.
IDE Improvements:
Updated UI:
- We’ve rolled out brand new icons and dark title bars on macOS. Furthermore, PhpStorm 2018.2 brings support for the MacBook Touch Bar! Run and debug your project, commit changes, and update the project right from the Touch Bar
VCS:
Version control comes with the following changes:
- Easier resolve of merge conflicts
- Enhancements in VCS Log tab
- Browse repository at revision
- Multiple GitHub accounts
- Skip the Push dialog
Database Tools:
Database tools in PhpStorm have been improved thanks to our colleagues from the DataGrip team:
- New SQL formatter
- Source code migrations
- Query plan diagram
- Custom data source
Other improvements:
- Customizable value for $_SERVER['DOCUMENT_ROOT']
- Simple CodeSniffer/MessDetector setup
- The new presentation for Quick Documentation
- Allow renaming old style constructor to the new style
- New Add @method tag quick fix for Undefined method
- Add method quick fix now inserts parameter type hints
- PHPUnit composite configuration
- Jump outside closing bracket/quote with Tab
- HTTP Client: Support environment variables in the request body
- HTTP Client: Support formatting of POST request body
- Docker: navigate from compose nodes and containers
- Docker: wrapping words in Docker logs
PhpStorm 2018.1.6 Build 181.5281.35
- This build fixes the issue with the Register action: IDEA-193747
PhpStorm 2018.1.5 Build 181.5281.19
- Change log not available for this version
PhpStorm 2018.1.4 Build 181.5087.24
- Fixes for PHP Remote Interpreters (Docker/Docker-Compose and Vagrant)
- Compiling PL/SQL code with actual errors
- Support of conditional compilation flags in pl/sql code
- Show inferred type in Flow in Brief Info
PhpStorm 2018.1.3 Build 181.4892.97
- This build delivers new features, bug fixes and improvements for PHP and the Web, and takes on the latest improvements in IntelliJ Platform
Notable bug fixes and features worth mentioning:
- void return type is not autocompleted WI-41850
- Find in Path” shortcut (Ctrl+Shift+F) not working in “Find in Path” preview window IDEA-189447
- Replace all’ confirmation popup is out of focus IDEA-186587
- Run configuration drop down menu does not show the full name of the test being selected IDEA-182763
- Wrong commit and push buttons rendering IDEA-190206
- Don’t add renamed or moved files to git index unless configured to do so IDEA-118140
- Default run/debug configurations are not saved IDEA-189444
PhpStorm 2018.1.2 Build 181.4668.78
Syntax Highlighting in Quick Definition:
- Using the Quick Definition popup became more convenient: with added syntax highlighting, you can now read what exactly a function or a class is doing, without losing your current context.
- Flexible configuration of imports from the global namespace
- In the previous versions of PhpStorm, you could choose to either import everything (functions, classes, constants) from the global namespace or use FQN for functions and constants. We’ve listened to your feedback and realized that more flexibility is sometimes required. In PhpStorm 2018.1.2, you can control auto-import separately for classes, functions, and constants
- For classes, you can choose between “insert FQN” and “prefer import” (PhpStorm will insert import if this doesn’t result in a conflict). For functions and constants, the options are “insert FQN”, “prefer import”, and “prefer fallback” (you can refer to the PHP documentation for its exact meaning)
Notable bug fixes and features worth mentioning:
- Collapsing tree node does not collapses all subnodes (regression)
- Command Line Tools Console – Cursor Not In Run Box
- Incorrect variable name during phpDoc generation for field in case inferred type in constructor $this
- Goto definition’ on ‘new expression’ targeting parent class __construct instead of referenced class
- Provide the ability to disable tooltips in editor without disabling inspections
- Subversion File History not working for links with spaces
- Typescript readonly type inference from const
- Add option to omit JsDoc types for TypeScript code
PhpStorm 2018.1.1 Build 181.4445.72
File-level suppression to PHP inspections:
- PhpStorm provides a lot of inspections to catch all sort of errors in your code, but it may occur that some particular code shouldn’t follow the standards set for the whole project. In previous PhpStorm versions, you were able to suppress a warning for a particular statement or declaration. PhpStorm 2018.1.1 brings the ability to suppress an inspection for the whole file: just add /**@noinspection <inspection_name> */ right after the first opening PHP tag or press ALT+Enter on the inspection warning and select Suppress for file in the submenu. You can also use /**@noinspection ALL */ to suppress all inspection for the file.
Required plugins for a project:
- Suppose you’ve found an essential plugin that would help a lot with developing your project (Symfony or PHP Annotations plugins are good examples of such plugins), and you want to make sure that everybody on your team is on the same page. Previously there was no way to let your colleagues know about the plugins without talking to them or writing the readme file. PhpStorm 2018.1.1 introduces Required plugins, which you can locate under Preferences | Build, Execution, Deployment | Required Plugins. You can specify the plugins and their exact versions as the project’s requirements. After you’ve set them, PhpStorm will notify if the required plugins are missing or need an update.
Go to Type action:
- You might have already used the Navigate | Type declaration action when working with JavaScript or when using our other IDEs. It lets you navigate to the type declaration from any expression, and now it is available in PHP, as well.
Notable bug fixes and features worth mentioning:
- Incorrect ‘find usages’ / refactoring of __constructor of parent class WI-19518
- Indexing of large files WI-41378
- Deployment: context menu is missing if no default server is selected WI-40826
- Docker-compose: output isn’t shown WI-41002
- Keystrokes lost during freezing IDEA-186636
- CommonJS: properties of function object returned by exported module not resolved WEB-24161
- DESC/DESCRIBE in read-only mode DBE-397
PhpStorm 2018.1 Build 181.4203.565
PHP Language:
- Inline function/method refactoring
- Refactor your code to functional style
- Configurable unchecked exceptions
- Goto Symbol navigation improvements
- Hierarchy checks for class aliases
Testing:
- Creating class from test
- Codeception: code coverage
- Better @covers support
- Gutter icons for running tests
HTTP Client:
- Assertions support
- Simplified first start
PhpStorm 2017.3.6 Build 173.4674.46
Bug fixes and features:
- PhpStorm v2017.3.4 & Codeception v2.4.0 incompatibility WI-40950
PhpStorm 2017.3.5 Build 173.4674.45
- Notable bug fixes and features worth mentioning
- Fixed: Built-in SSH: does not support strong security ciphers – Cannot negotiate, proposals do not match IDEA-140196
- PhpStorm v2017.3.4 & Codeception v2.4.0 incompatibility WI-40950
- Fixed: Multiple “Updating indices” bg tasks after external file system changes IDEA-123287
- Fixed: Autocomplete too fast and leads to errors when inputting a number DBE-4965
- Fixed: Hide MySQL Collations & Schemas DBE-5557
- Fixed: Database Console name in Files have turned into guids DBE-5904
PhpStorm 2017.3.4 Build 173.4548.32
Fixed:
- Allow UI scale exceed 2x
- Multiple “Updating indices” bg tasks after external file system changes
- Evaluate window: cannot TAB from expression into results tree
PhpStorm 2017.3.3 Build 173.4301.34
REST Client: Auto-formatting of responses:
- In this build, we’ve implemented one of the new REST client’s most voted features: auto-formatting of request results. PhpStorm analyses Content-Type and formats the response accordingly. If type detection has failed for some reason, you can still choose between JSON, HTML and XML formatting manually. To see the original response, you can select the View as Text formatting type
Highlighting call-site in case of pass-by-reference:
- PHP 7.3 may introduce “Explicit call-site pass-by-reference” (RFC) that will allow prepending of a call-site argument with &. This should help to understand the code and notice possible unexpected changes of a variable. It’s still a year till the 7.3 release, but why wait?
- In this build, we’ve extended parameter hints with pass-by-reference visualization that will help you find a function or a method call that has reference declaration in a parameter. The new parameter hints will be shown for all arguments that are actually passed by reference. Please share your feedback about the new feature!
Notable bug fixes and features worth mentioning:
- Fixed: Short syntax array destructuring does not allow skipping values: WI-34517
- Fixed: Unhandled exception: doesn’t analyze “new MyClass” (constructor) expression: WI-37946
- Fixed: Broken “Change to” spelling quickfix in the Commit dialog: WI-39142
- PHP New Class now saves previously selected template: WI-39427
- Fixed: “Can’t run 32-bit version on Windows”: JRE-590
- Fixed: All run configurations lost after upgrade to 2017.3: IDEA-182966
- Fixed: Tool Window docking issue IDEA-149061
- Fixed: FETCH ALL IN returns error org.postgresql.jdbc4.Jdbc4ResultSet: DBE-2465
- Fixed: DataGrip does not recognize Redshift’s WITH NO SCHEMA BINDING clause: DBE-5404
PhpStorm 2017.3.2 Build 173.4127.29
Notable bug fixes and features worth mentioning:
- Unhandled exception shouldn’t be reported for tests with @expectedException
- Improved discoverability of Recursive Search in Find Window
PhpStorm 2017.3.1 Build 173.3942.32
- Support custom templates variables in ‘new class’ dialog
- Fix “Structure view is always collapsed”
- Fix Tool Window docking issue
- Fix “Unable to update issue state from Open Task dialog”
PhpStorm 2017.3 Build 173.3757.138
- Brand new editor-based REST client. With the new REST client, all the powers of the PhpStorm code editor are now available for your REST requests.
- Significant performance improvements. Typing latency in very complex PHP files has decreased significantly. We've examined typing latency in the mPDF main file, which is a 38k-line-long mix of PHP, JS, and HTML, and it is down by 75% in PhpStorm 2017.3!
- New inspections for exception handling. Three new inspection Unhandled exception, Redundant @throws and Redundant catch clause with corresponding Quick Fixes will help you take exceptions under your control!
- Test generation improvements. Now you can create Codespec and PhpSpec classes and create test methods!
- Improved Twig support. We've implemented language injections for Twig custom tags and named blocks as well as improved Twig formatting that can now handle complex structures.
更新時間：2020-09-25
更新細節：
更新時間：2020-09-17
更新細節：
What's new in this version:
Significant New Features:
- New Eye Dome Lighting settings in the 3D viewer help improve visual display of vector and lidar data
- A new tool for simplifying loaded meshes or TINs
- A new Spatial Operations tool to find the intersection of two vector layers
- A new Analysis menu option to find the overlap (both percentage and graphical) between two or more Lidar, raster/image, and/or terrain layers
- An update to the Raster Reclassify tool that allows it to work with continuous data (terrain/slope, single bands of imagery).
- A new sweep selection tool for working with vector data in the 3D viewer
- Dramatically faster rendering of tiled online sources, especially in 3D.
- Support for creating point, line, or area features from a list of coordinates in an MS Excel (.xls/.xlsx) file.
- A new Digitizer menu providing convenient access to all Digitizer functions.
- A tabular preview showing the first ten lines of an imported ASCII or Excel file.
- Significant New LiDAR Module features:
- A new Terrain Paint tool for manipulating elevation values in a free-form way using an interface similar to MS Paint, Photoshop, etc. [Item #GM-1126]
- A new algorithm that improves building classification results on all types of point clouds. [Item #GM-9434]
- Improved building extraction with better 3D shape simplification, including generating building footprints. [Item #GM-2889]
- A new option to generate a process summary report when using Pixels to Points [Item #GM-7612]
- An update to the underlying libraries used in the Pixels to Points process resulting in improved output with certain image data sets. [Item #GM-10386]
- Two new lidar draw modes: [Item #GM-10148]
- 'Color by Source Layer' (allowing easy display of lidar point clouds using a different color for each layer)
- ‘Color by Scan Angle’.Supports for sorting exported LAS/LAZ files by one or more fields (.X, Y, Z, class, GPS time, etc.).
- Dramatically faster rendering of lidar path profiles with a large number of points.
- New Supported Formats:
- [LIDAR MODULE ONLY] Added support for exporting Lidar data to the Leica PTS format. [Item #GM-10284]
- Added ability to import and export Mapbox Vector Tile data sets. [Item #GM-3900]
- Added support for the XTide .dat file format [Item #GM-9424]
- LiDAR Changes
- [LIDAR MODULE ONLY] The export to Lidar LAS/LAZ files now supports sorting the data by one or more fields (i.e. X, Y, Z, class, GPS time, etc.). A new Sorting tab on the Export dialog and a new SORT_FIELD parameter for the EXPORT_VECTOR command. [Item #GM-10697]
- [LIDAR MODULE ONLY] Added new Lidar draw mode 'Color by Scan Angle' to color Lidar point clouds by scan angle. [Item #GM-10834]
- [LIDAR MODULE ONLY] Added a new option to allow selecting Lidar points at least some distance from other Lidar or line features to the existing 'Select Lidar by Distance' feature. [Item #GM-10994]
- [LIDAR MODULE ONLY] Fixed issue with updating the return number/count of Lidar points when deleting other Lidar points in the pulse. [Item #GM-10838]
- [LIDAR MODULE ONLY] Fixed an issue with bin-gridded Lidar data being a fraction of a pixel off from its correct location in the grid. [Item #GM-10917]
- [LIDAR MODULE ONLY] Poles that are extracted now have a height attribute [Item #GM-10820]
- [LIDAR MODULE ONLY] Pole extraction will now use the workspace projection correctly. [Item #GM-10653]
- [LIDAR MODULE ONLY] Pole extraction now handles poles that have a negative elevation [Item #GM-10708]
- [LIDAR MODULE ONLY] Fixed an issue where the method that retrieved the nearby points could return no points. This affected pole classification and an other lidar operations that used this method [Item #GM-10868]
- [LIDAR MODULE ONLY] Lidar cropping based on selected features now uses the feature bounds instead of a rectangle [Item #GM-10997]
- [LIDAR MODULE ONLY] Corrected Lidar spatial thinning when keeping or removing every Nth point. It was off by 1. [Item #GM-10838]
- [LIDAR MODULE ONLY] Fixed issue with image masks not working correctly on the Pixels to Points dialog if the images have been resized prior to loading in the P2P dialog. [Item #GM-11071]
3D Viewer Changes:
- Repair the rendering of 3D vector area features in some contexts. [Item #GM-11267]
- Repair the rendering of 3D vector line (twisting) features in some contexts. [Item #GM-11083]
- Fix a variety of issues in 3D vector feature editing. [Item #GM-11108]
- 3D Sweep Selection [Item #GM-4088]
- New Eye Dome Lighting settings in the 3D viewer help improve visual display of vector and lidar data [Item #GM-9276]
- 3D lines now have constant width. [Item #GM-6847]
- Fixed 3D display and gridding of vector layers that have unit names representing something other than meters or feet (like '500 cm'). [Item #GM-10826]
- Path Profile/Line of Sight Function Changes:
- [LIDAR MODULE ONLY] Dramatically sped up the render of Lidar path profiles with large numbers of points. [Item #GM-10825]
- Made path profile save to CSV use Position Display Format setting for Latitude/Longitude values. [Item #GM-11011]
- Fixed issue with perpendicular path profile not aligning with main path if Bearing Sense was not Grid North. [Item #GM-10809]
Analysis Function Changes:
- Add new option to find the overlap (both percentage and graphical) between two or more Lidar, raster/image, and/or terrain layers. The new option is under the Analysis menu. [Item #GM-10367]
- Fixed issues calculating area volumes. [Item #GM-10614]
- Added features to the Raster Reclassify tool to work with continuous data (terrain / slope). Other new features include creating a spread of output values, Improved diagnostic messages, creation of ranges with equal but opposite ends, and allow multiple transparent colors. [Item #GM-10734]
- Added a new option to simplify when generating a 3D model (mesh) from a loaded terrain surface. [Item #GM-7358]
- Added more output options to Raster Reclassification. It includes palette image, elevation (8-bit integer), elevation (16 bit integer), and an option to set unspecified input values to the transparent color.Raster Reclassification now allows non palette based layers such as elevation and image data. [Item #GM-10842/GM-10816/GM-10843]
- Fixed incorrect units on min/max points while generating contours. [Item #GM-10684]
- Reworked View Shed algorithm to use Measure->Bearing Options to calculate angles. [Item #GM-8409]
- Allow view sheds with over 512 million samples. Users are now prompted to allow the specified size or to automatically increase the Sample Spacing to get the sample count to a reasonable level. [Item #GM-10921]
Digitizer Tool Changes:
- Added a new option to simplify the geometry of 3D models (meshes). The new option is in the Digitizer Tool's right-click Move/Reshape menu. [Item #GM-7358]
- Added new option to allow snapping to Lidar point returns when digitizing. The option is under the right-click Options menu of the Digitizer Tool. [Item #GM-5859]
- Fixed the simplification of area features to remove the correct number of vertices. From v21.0 until v21.1.1, area simplification was often keeping many vertices that should have been removed. [Item #GM-10852]
- Fixed issues creating perpendicular lines when the selected line layer projection is different than the view projection. [Item #GM-10908]
- Fixed issue with ELEVATION attributes of point features changing when moving the features. [Item #GM-11231]
- Made 'Insert Vertices and Split at Intersections' keep per-vertex elevations and times. [Item #GM-11041]
- Add ELEVATION attribute to newly created point features created by snapping to 3D features (Lidar, terrain, 3D models, etc.) in the Digitizer Tool. [Item #GM-10992]
- Allow user to select "Above Sea Level" option when performing multiple volume calculations over a range of base heights. [Item #GM-10575]
- Fixed issue creating a buffer on one side of a line [Item #GM-10888]
- Updated Create Regular Grid operation to obey the Distance Calculation Type setting from the Configuration dialog. This means that if you are using Great Circle or Rhumb Line distance calculation, the grid cell edges will match the specified distance using the Measure Tool rather than being calculated in the current display projection. [Item #GM-5818]
Scripting Changes:
- Added ability to export TINs, Points, and Contours to Land/XML via a script. [Item #GM-7759]
- Added support for TAKE_OFF_ALT parameter for GENERATE_POINT_CLOUD script command. [Item #GM-11030]
- Added parameter to CALC_VOLUME script command to allow user to indicate whether the base height is at sea level or relative to the ground. [Item #GM-10913]
- Added built-in script variables for script file name with and without the extension [Item #GM-11106]
- Made VOID_ELEV parameter be obeyed for BIL elevation export using EXPORT_ELEVATION script command. [Item #GM-11133]
- Updated saved workspace files to remember a user-specified no-data value used when gridding text files on import. The new NO_DATA_VAL parameter for the IMPORT_ASCII command provides this support. [Item #GM-11139]
- Fixed bug causing the CALC_VOLUME_BETWEEN_SURFACES script command to require an AREA_FILENAME parameter to be provided rather than just calculating the volume inside the overlap of the surface layers. [Item #gm-11180]
Online Source Changes:
- Dramatically sped up the rendering of tiled online sources, especially in 3D. [Item #GM-10503]
- Added ability to add or replace layers in an existing MangoMap. [Item #GM-10933]
- Updated the Layer->Find Extrema (Min/Max) Elevation Points option to work with online terrain sources. There is also a new option to create point features at the located min/max points. [Item #GM-11056]
Projection/Datum Changes:
- Fixed issue with NTv2 datum transformations not being used immediately upon load. [Item #GM-10630]
- Added built-in IG05/12 and IG05/12 Intermediate datums and corrected the transform for the New Israeli Datum (NID). [Item #GM-10386]
- Added new Italian versions of ETRS89 and ETRF2000 datums that use NTv2 datum shift files. The base ETRS89 and ETRF2000 datums no longer use those NTv2 shift files as they only covered Italy and caused a slight discontinuity at the edge of the file. [Item #GM-10526]
- Added built-in PROJCS names for EPSG codes 2945-2951 (MTM Canada NAD83 CSRS zones). [Item #GM-10774]
- Improved the behavior of the GeoCalc mode projection selection dialog when loading layers so that transforms are automatically selected or prompted for when pressing OK rather than requiring the user to explicitly double-click on the transform list. [Item #GM-10808]
- When in geocalc mode and files are using a projection that isn't supported by geocalc a warning will appear and let you pick a new projection instead of hard crashing [Item #GM-10571]
- Updated MGI Austria datum shift with new file from Austrian government that fixes an issue in some locations. [Item #GM-6711]
- Fixed issues with display lat/lon grid lines for world-covering data cutting off around 67 degrees (N and S) for Mercator. [Item #GM-10801]
- Updated coordinate system definition files to include some missing EPSG codes. [Item #GM-11021]
- Fixed central meridian for Albers Conus EPSG codes (5069 and 5070) [Item #GM-11024]
Format Specific Changes:
- Added support for exporting terrain data to Land/XML as a TIN. [Item #GM-9472]
- Sped up tiled exports to ECW/JP2 files when multiple cores are available. [Item #GM-5063]
- Updated DXF and DWG exports to handle 3D models (meshes). Each triangle in the mesh is exported as a 3D area feature. [Item #GM-11345]
- Added the ability to customize the No Data value exported in Arc ASCII Grid files through the user interface. [Item #GM-10846]
- Updated projection information stored in GeoTIFF and LAS/LAZ files to include the detailed TOWGS84 datum transformation so that custom datums with unknown EPSG codes can be read back in correctly from exported files. [Item #GM-10849]
- Fixed issues in v21.1.0 rendering JPG-in-TIFF files. [Item #GM-10884]
- Fixed the methodology used to identify a SQLite/Spatialite database file. [Item #GM-7745]
- Updated exports to multi-band image formats (i.e. GeoTIFF, BIL, Erdas Imagine) to allow the inclusion of vector data and map layout items (i.e. scale bar). [Item #GM-8177]
- Fixed issue loading Japanese GML DEM files on systems where the locale was also set to Japanese. [Item #GM-9977]
- Ensure that exported KMZ files containing a 3D model can be read by Google Earth. [Item #GM-10926]
- Fixed slow load of vector files containing area features with large numbers of holes/islands in v21.1.0 release. [Item #GM-11131]
- Fixed issues loading ECW files with non-English characters in the filename or path. [Item #GM-11182]
- Added support for batch converting to the Garmin JNX format. [Item #GM-11334]
- Updated GeoTIFF 16-bit imagery exports to store signed 16-bit samples if any of the input layers have signed values. [Item #GM-10976]
- Added support for loading LandXML Parcels with 3D coordinate lists. Also added support for using Property values from LandXML as attribute values. [Item #GM-11054]
- Added option to use the Ordinance Survey Master Map (OSMM) styling when loading an OSMM file. [Item #GM-9055]
- Add an option to the KML/KMZ export to control the creation of folders for each geometry type. [Item #GM-10579]
- Significantly improved time needed to export data to CADRG format. [Item #GM-5415]
- Improved performance of exporting data to Digital Terrain Elevation Data (DTED) file format. [Item #GM-7830]
- S-52 zoom levels now are used when changing the detail slider on s-57 files. Features that disappear when zooming in will now more closely match the s-52 style [Item #GM-10788]
- Improved the loading of MSI-Planet files. The clutter files now load as a palette-based image layer if a 'menu' file is provided. A prompt to confirm the UTM zone hemisphere is also no longer required if the 'projection' file specifies enough information to determine the hemisphere automatically. [Item #GM-10822]
- Added support for MapInfo datum codes for GDA2020, S-JTSK, and other datums. [Item #GM-10973]
- Dramatically sped up the load of S-63 chart files initially encrypted for a different machine. [Item #GMSDK-240]
- Re-enabled support for loading NetCDF files larger than 2GB (broken since v20.0). [Item #GM-10803]
- Fixed problem with incorrect elevation units when importing Global Mapper workspace file containing TIF files. [Item #GM-10634]
- Fixed error loading some LAS files over 2GB in size. [Item #GM-11337]
- Fixed problems loading some JP2 terrain data, including crashes on load and missing data in parts of the display with elevations below -9999. [Item #GM-11157]
- Fixed problem exporting feature points to shape files when using the "Generate 3D Features Using Loaded Elevation Data" option and the points did not have an ELEVATION attribute. [Item #GM-10564]
- Improved exporting and importing 3D content (mesh data) to and from PDF files. [Item #GM-9727]
- Include color from GM point symbols when exporting to DWG and DXF.Read point color when importing DWG and DXF. [Item #GM-5606]
- Fixed issue where the wrong code page being written to an exported SOSI file. [Item #GM-11200]
- Fixed an issue where the projection was not being identified correctly in an exported SOSI file. [Item #GM-11201]
- Improved resolution when exporting large map layout from the Map Layout Editor to PDF [Item #GM-10629]
- Made ELEV_UNITS get passed down properly when adding terrain layers to map catalogs via script. Also ensure that loading map catalogs doesn't end up prompting for elevation units. [Item #GM-10792]
- Made export to CSV from Attribute Editor handle the case where the first column is empty or hidden. [Item #GM-10815]
- Include map layout elements when exporting to PDF from the main view.Make inclusion of layout elements optional. [Item #GM-10840]
- Fixed the inadvertent duplication of coordinate values when exporting a lat/lon dataset to CSV with the "Export Separate Lat/Lon Coordinates for Each Point" option selected. [Item #GM-10475]
- Removed extraneous vertices from FBX terrain export. [Item #GM-10903]
- Make sure REST and GeoJSON overlays have the codepage set to UTF-8. [Item #GM-10916]
- Remove invalid characters from DXF layer names during export. [Item #GM-10924]
- Automatically detect false easting/northing values specified in the wrong units for some MrSID files and load them with the correct interpretation. [Item #GM-6031]
- Improved display of filled areas in SOLID entities when loading DXF and DWG files. [Item #GM-5955]
- Fixed problem where linked image files were not being saved in an exported KMZ file. [Item #GM-11009]
- Move option indicating whether to load all PDF map frames to the PDF Import Options screen. [Item #GM-11017]
- Fixed DXF exporter so that it respects the label option when exporting point features. [Item #GM-10981]
- Resolved issue with missing attributes when importing OSM data. [Item #GM-11064]
- Fixed issues displaying some BMP files in v21.1. [Item #GM-11184]
- Rendering/Style Changes:
- Fixed issue with custom shape point symbols scaled to be less than 0.5 pixels in radius drawing as 2 pixels width. Also fixed the pixel location of vector data on display and export. It could be up to one pixel right and or down of where it should have been. [Item #GM-7490]
- Check online layers when rendering a texture map. [Item #GM-10860]
- Performance:
- Sped up tiled exports when cropping or tiling to selected area features. Now multiple cores will be used if available. [Item #GM-5063]
- Improved performance when specifying very small custom grid line spacing. [Item #GM-5788]
User Interface:
- Added a new top-level Digitizer menu providing access to all Digitizer functions. [Item #GM-11198]
- ASCII and Excel file import dialogs now have a preview for the top 10 lines [Item #GM-457]
- Added Apply button to the Layer Shift dialog when its opened from the Control Center [Item #GM-11126]
- Added preview of transparent colors in the Raster Options/Display dialog for all raster formats, not just palette based ones. [Item #GM-10675]
- Added new feature to keep Histogram Graph windows open after the metadata dialog has closed. [Item #GM-10883]
- Added options on metadata histogram tab to control display of histogram bin labels and the option to color the histogram bins based on the currently selected shader. [Item #GM-10878]
- Added option for more detailed batch/re-projection processing information during run. [Item #GM-10720]
- Added configuration option for setting water level increment in 2D view. [Item #GM-9475]
- Modified Layer Name input box to only outline the control with a red box if it is blank rather than a blinking color. [Item #GM-10895]
- Allow deleting single color from a list of a layer's transparent colors. [Item #GM-10891]
- Made the band selection dialog for multi-band exports resizable. [Item #GM-10731]
Misc. Changes:
- An update to the Raster Reclassify tool that allows it to with continuous data (terrain/slope, single bands of imagery).
- Enforce multi-part polygon grouping in Attribute Editor. [Item #GM-8068]
- Fixed issues in batch convert from v21.1.0 release, including cropping to selected areas and using other source files as filler. [Item #GM-11023]
- User settings import now will remember toolbar locations. They will be used when imported as long as the version and monitor resolution match. [Item #GM-10615]
- Fixed bug where vertical transformation box doesn't appear in geocalc mode [Item #GM-10560]
- Fixed bug where 3D settings didn't match expected values if there were no GM registry keys yet [Item #GM-10279]
- Global Mapper correctly reads the custom AoU file in geocalc mode [Item #GM-10127]
- Display attribute values in the appropriate code page on the Search Vector Data dialog. [Item #GM-10789]
更新時間：2020-09-17
更新細節：
更新時間：2020-09-17
更新細節：