Rewrite the installation script.
Make it universal for installing any package.
Merge-request: IJ-MR-149762
Merged-by: Egor Eliseev <Egor.Eliseev@jetbrains.com>
(cherry picked from commit 268ba9164f9e02fbef1520144486902077ad9e8a)
GitOrigin-RevId: 29eea5c5884a4c5afed6f3736691644171ea7f82
This is a bit complicated and confusing.
We have a flag to fit the popup into the screen.
However, the existing code ignored that flag and fit it anyway,
but only if the popup is too large. If it's small enough, then it was
left alone regardless of whether it's actually located fully within
the screen.
The previous fix ignored that flag as well, but fit the popup
into the screen in all cases. Which meant the flag was now useless.
So to keep it working for both cases, let's actually check that flag here.
If it's set, then use the new logic: fit into the screen no matter what.
Otherwise, only fit it into the screen if it's too large, keeping the old
logic there.
That logic was introduced for Search Everywhere to begin with,
and it has the flag set to false. So we're not changing anything there.
And at the same time it'll fix issues with popups such as
the Commit Options.
(cherry picked from commit 92d1f0be81d4860901414d3266ec4de3af2fc952)
IJ-CR-149457
GitOrigin-RevId: 4539693a61b8b7b8920795868e0146f53ffdd0ec
When the popup is finally shown, the log message
contains the coordinates of the popup and the ID
of the target screen. Add the bounds of the target
screen as well. They may or may not appear in earlier
messages, but it's very useful to have the end result
in one place (for example, to reason about why
it was / wasn't necessary to change the popup
bounds to fit it into the screen).
(cherry picked from commit d1f4fea44c4749589fccbb914afcc450d48df511)
IJ-CR-149457
GitOrigin-RevId: 820ba1ff87ab632dd2e206eac1751683dc25c622
The existing logic didn't take coordinates into account.
A popup may be smaller than the screen, but shifted so
that it doesn't fit anyway.
(cherry picked from commit 945d7a60730508eb3d68f257c95d3833d68846d1)
IJ-CR-149457
GitOrigin-RevId: c2874c7d61f524c183d8f1451408d64e0d8db356
Update test data.
1. Unresolved imports are not removed with optimize imports
2. Unresolved imports are not marked as unused
(cherry picked from commit 2c32c368ae0907fb75ea76fc9749e903c160667c)
IJ-CR-153189
GitOrigin-RevId: 153d42e7f61f8357eeb74f022e31bbe406e83c02
The logic for disabling the unused warning on unresolved imports was dependent on the visit order. Moving sustracting unresolved imports to the end of computation fixes the problem.
(cherry picked from commit adeb85e59c17261a5bf9f64dfb4a7836a2403f43)
IJ-CR-153189
GitOrigin-RevId: fac4173a0fac5b29be9301f9d5f04fed08cceff1
Turns out that Unconfined dispatcher still installs an event loop, which was the main reason of avoiding `runBlocking`
(cherry picked from commit 6c47ede47e1e0377504052a39bbceba3d2046c4e)
GitOrigin-RevId: af77b1b6ba4c640ac2253b51603332392389a3ad
Bundle.getMessage calls moved from constructors to the getDescription method in some *Macro classes to use it lazy and avoid issues with cyclic dependencies when getting the locale.
(cherry picked from commit 7741209200df121e4e7785ee58fd48c329a18077)
IJ-CR-149835
GitOrigin-RevId: a213423284890ad9f7b01e53da0c7129f430b4cf
Add a processing function for new breakpoints.
Merge-request: IJ-MR-152628
Merged-by: Egor Eliseev <Egor.Eliseev@jetbrains.com>
(cherry picked from commit 63ebb4c7c620cf7cc3f56924619fc5adc09e25dd)
IJ-MR-152628
GitOrigin-RevId: 1f26240498360aff61ff27878118b0eb841ec082
UsageState.restore also expands a tree node, and because it's called for every node, it shouldn't generate tree expanded events.
(cherry picked from commit 3c3d581e94bab9fe08ff655ac5c656aa21617a2e)
IJ-CR-151182
GitOrigin-RevId: cde9f512f810a3e4bb5a470bd7bef3b36540e686
This fixes a crash when opening the File Structure popup in very large files (JBR-7655)
(cherry picked from commit 9f497ecbf584fe8596630ab86245a0835a6eb3f4)
IJ-CR-151182
GitOrigin-RevId: 243ba2314b173347983aeea2299efdede60b2baa
This fixes a crash when clearing the search in the Keymap settings (IJPL-171132)
(cherry picked from commit f382cfcca06427f0069d4d1bcacd6862bf69d392)
IJ-CR-151182
GitOrigin-RevId: 4fec35a25dcf8ad45335f90c9a7328886c3d2106
This fixes a crash in Find Usages (IJPL-171433)
(cherry picked from commit 70eef793231c7819b88453eb55c05a63df9142d3)
IJ-CR-151182
GitOrigin-RevId: 3afbe9798ae200508739cc3e264af8fae187323f
This fixes the crash caused by too many tree expanded notifications when nodes get expanded by searching in the tree, for example, in database schema selection tree (IDEA-359880)
(cherry picked from commit bac09fd9d689118ef9efc87a1ac0cebb09164329)
IJ-CR-151182
GitOrigin-RevId: 418181a5a8631c8719beb799ba88003a0ad78dcd
This will prevent such contents from appearing automatically.
(cherry picked from commit dddec2df81308c53edd148148e8e04ae6fd6c3b2)
GitOrigin-RevId: 43481d6e805286044338fd681d0613254b84cf4d
The problem with using getActionOrStub as the action supplier
to get the custom icon is that if the action isn't loaded yet,
then its stub will have a null icon. Therefore, customization
doesn't work.
Performance considerations: it shouldn't cause any serious
performance issues unless there are very many icon customizations,
which is normally not the case.
(cherry picked from commit 4fa084bdcaebe8e06dc26f4004a6eeac33dd36a1)
IJ-CR-152585
GitOrigin-RevId: ea864f92b2f1b745e62cf8497ddf8c3af01cd467
Behavior changed unintentionally. Problem found during code review.
(cherry picked from commit 7424552ccbc568d2ddfb22570c2db479df624821)
IJ-CR-152316
GitOrigin-RevId: 4015ebbac27103eda06d8707882071a3394a37a5
Revert hiding public static field `INSTANCE` since a plugin uses it
(cherry picked from commit 44a0a3a066d923e0167489f443b511493a875daa)
IJ-CR-152896
GitOrigin-RevId: dea487b441d60680b93b246ee5ab1ab036e11d44
