The new UI is only enabled by default on fresh installations (when no configs of previous versions are found on the machine). The old UI is still there if it works better. Another way to open the Content pane is to click on View > Tools > Content and that should open it up. > The advantages in being able to see everything in one tab and not having to hunt for the other set of information when you need it is too great To edit the text such as changing the font color, font size or the font itself, you want to highlight hte text you want to change, right click, select properties and the Touch Up panel will open to the Text Tab. allows seeing the log while preparing the commit. While this might be true, separating the views provides benefits e.g. > Separating the git functions into separate tool windows is counter-intuitive for all but the most basic git user. It opens in editor, and follow the selection afterward. That is what one needs to double-click or use Next changes shortcut (F7) to open the diff. Since Local changes can be used not only for commits, we decided that showing diff right away is too aggressive. > the local changes view does not show the diff for the file. In contrary to the commit dialog, which is modal, and blocks the app when it is shown. Non-modal means the NEW style, which is indeed non-modal - does not block the app when it is shown. "Modal" has a specific meaning for a software developer > I would never have guessed "non modal" meant the old style. We'll check if there are some bugs with settings migration in the described scenario, thanks for reporting.Īnd let me clarify some of the mentioned issues You will ruin one of the main things I really, really like about the JetBrains IDEs when it pertains to VC workflow. The advantages in being able to see everything in one tab and not having to hunt for the other set of information when you need it is too great.
0 Comments
Leave a Reply. |