How to generate track changes from files before and after changes are made? - ms-word

I have two versions of a word document as two different files.
How can I get a track changed version?
Is there a way to compare them and merge as track changed version of these two documents?
PS: MS Word's comparing tool seems a solution it doesn't work for me. I need its "track changes" version.

First, turn on Track Changing
On the Review tab, in the Tracking group, click the Track Changes image.
To add a track changes indicator to the status bar, right-click the status bar and click Track Changes. Click the Track Changes indicator on the status bar to turn Track Changes on or off.
NOTE If the Track Changes command is unavailable, you might have to turn off document protection. On the Review tab, in the Protect group, click Protect Document, and then click Stop Protection at the bottom of the Protect Document task pane. (You might need to know the document password.)
NOW,
On the Tools menu, click Track Changes.
When the Track Changes feature is enabled, TRK appears on the status bar at the bottom of your document. When you turn off change tracking, TRK is dimmed.
Make the changes you want by inserting, deleting, or moving text or graphics. You can also change formatting.
Track changes while you edit
You can easily make and view tracked changes and comments while you work in a document. By default, Microsoft Office Word 2007 uses balloons to display deletions, comments, formatting changes, and content that has moved. If you want to see all of your changes inline, you can change settings so that tracked changes and comments display the way you want.
Balloons show formatting changes, comments, and deletions.
NOTE To prevent you from inadvertently distributing documents that contain tracked changes and comments, Word displays tracked changes and comments by default. Final Showing Markup is the default option in the Display for Review box.
Track changes while you edit
Open the document that you want to revise.
On the Review tab, in the Tracking group, click the Track Changes image.
To add a track changes indicator to the status bar, right-click the status bar and click Track Changes. Click the Track Changes indicator on the status bar to turn track changes on or off.
Make the changes that you want by inserting, deleting, moving, or formatting text or graphics. You can also add comments.

Related

How do you hide the "updates available" badge for VSCode extensions?

VSCode has a blue badge on the Extensions tab showing how many extensions updates are available. This thing lights up a couple times per day and it's right beside the badge that tells me if I have uncommitted Git changes. This makes it super distracting because it's right beside a badge that really matters. I care about Git. I definitely do NOT care if every single extension is 100% up to date.
How do I permanently turn off the badges on the Extensions tab?
Edit: I'm aware that you can right-click and "Hide badge", but this only gets applied to one vscode window and the badges re-appear as soon as you restart that window.
A commit has just been added to vscode (closing the issue cited below) to enable the persistence of hiding those view badges, see Ensure badge state is persisted in activity bar cache. Shouldbe in the next Insiders Build and Stable v1.76 early March 2023.
As you noted in the comment, right-clicking and Hide Badge (see How to disable blue notification badges on VS Code?) is not remembered between reloads of vscode.
I don't think there is a way to do that currently, so upvote the github issue
Persist state of numbered-badges hiddenness

How to turn on/off the SOURCE CONTROL PROVIDERS view in vscode?

I have one folder that contains multiple sub folders, and each of them is one git repository. Sometimes I can see this SOURCE CONTROL PROVIDERS view showing up and it's super helpful, but sometimes it doesn't show up. I would like to know if there is a switch on the vscode UI to turn on or off this view. (Maybe it's a plug in that I accidentally installed?)
Thank you!
Version 1.31.1 has a config parameter to always show the source control providers:
Type Ctrl+, to access settings
Search for SCM
Check the "Scm: Always Show Providers" option
You are using 1.17 released today (at least for me). For info about that panel see source control providers. I don't see a toggle for that panel - I assume you always get it if you have multiple SC Providers and open up the source control icon CTRL-Shift-G.
but sometimes it doesn't show up
Starting with 1.47 (June 2020), it does not show up at all, as it used to.
There is a new "single-unified view":
(the old view might come back in 1.49, Sept. 2020, see at the end)
The Source Control view has been consolidated into a single view:
All repositories are rendered in a single view, so you can get a better overview of the entire workspace status.
Additionally, the Source Control view can now be moved to the panel and other views can be moved to the Source Control view container
This... has not been appreciated. See issue 102118:
In the old system, if I had 4-5 repos showing, the one or two with active changes would show up clearly at the bottom.
Now it's very muddled, and sort by status simply puts the repos with changes at the top.
Here is the old view. List of changed files only show up when a repo is clicked. They are clear and distinct, separated from all the list of repos and everything else at the bottom.
The new single source view. One has to hunt for the changes amidst a list of other repos. It is cluttered, hard to parse, and requires hunting to find what you want. The old view was much easier to follow and use.
issue 104151 proposes to bring back the old view
Example:
The Source Control Repositories view is now back.
(It used to be called Source Control Providers).
It lets you control visibility of multiple repos in the Source Control view.
The setting scm.repositories.visible is now back
(It used to be called scm.providers.visible).
I've sprinkled visibility actions both in the context menu of the Source Control view as well as the ... menu, to make it easier to control the visibility without using the Source Control Repositories view.

StarTeam share change request across multiple branches or views

We currently have a simple Star Team setup with a couple of branches or views as they seem to be refered to in Star Team:
--Production
--Staging
--Development
--Trunk
We would like to "Share" or create a "Referenced View" of a Change Request (CR) that would be visbile on all of these views, but we would like it to be updated across all the branches when a change is made to it.
I have tried Ctrl + dragging and dropping the CR to the various views but they dont get updated when I make changes to it. Its as if they are being treated as individual copies of the CR. I also tried checking and unchecking the "Branch on Change" checkbox for the behavior of each of the items but that seems to have no effect either.
Have you tried the "Floating" Radio Button under "Advanced | Behavior" on the "Configuraion" Tab?
Georg

How to autofocus working copy in the dynamic history view in mks integrity?

At work I use MKS Integrity for version control (and PLM). I wonder whether there is a possibility to automatically focus something reasonable, like the working copy or the member revision, in the member / project history view (I have set it to 'dynamic'). At the moment it always opens up at some more or less random position when I select a new member. Then I have to scroll around to find my working copy - that's really annoying.
It is not possible to get MKS to open the graphical history view at a certain position. However, I just discovered that there is a list history view, which feels much more convenient to me. You can change the Intial View under File -> Edit Preferences -> Configuration Management -> Views -> Member History View (and ... Project History View respectively). In the list view, things are clearly sorted and one can find specific revisions (working/member revision are marked with symbols at the beginning of the line) a lot quicker.
NB: when changing the settings for the history views, all history views have to be closed, otherwise the changes are not applied

Eclipse IDE last edit location history - multiple steps back?

I'm now in a process of transition from Netbeans to Eclipse (Indigo).
Ctr+Q seems to have the same function - going back to the last edit location. But in Netbeans I was able to press Ctr+Q repeatedly and go further back without the need of altering the file content (undo and redo hack).
Is there such functionality in Eclipse?
Some info:
I'm using the JavaScript Development Toolkit, PDT, and YAML editor.
It seems that Back action (Alt+Left) is more or less the same. The difference is that it tracks any action, not only edits. Actions as "Go to declarations" are also included in the history of Alt+Left.
I think, in a way, it's more useful because I track back my real actions as in "real browsing" the code. Though I will switch the keyboard shortcuts for Last Edit and Previous Action so that I keep the Ctr+Q habit.
It is currently not possible in Eclipse. There is an old feature request for this functionality with Bugzilla id 72773 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=72773).
9 years later, check out Eclipse 4.17 (2020_09)
Multiple Last Edit Locations
Previous Edit Location navigation (formerly named Last Edit Location) is now expanded to remember multiple edit locations.
The last 15 edit locations are now remembered.
For convenience, similar edit locations in close proximity to each other are also merged so that each of the 15 remembered locations remains distinct.
How to use
Two new keyboard shortcuts are introduced:
Ctrl+Alt+LEFT_ARROW (or on Mac Ctrl+Opt+LEFT_ARROW) navigates to the most recent edit location, just as Ctrl+Q always has in prior releases.
However, now continuing to hold Ctrl+Alt and then pressing LEFT_ARROW again begins a traversal through the history of prior edit locations, with each additional press of LEFT_ARROW moving a step further back in history.
Once traversal stops, future Ctrl+Alt+LEFT_ARROW actions are now temporarily anchored to this older historical location for easy exploration of that code region.
The classic Ctrl+Q mapping has been likewise enhanced with this new functionality, so that Ctrl+Q and Ctrl+Alt+LEFT_ARROW are synonymous.
Ctrl+Alt+RIGHT_ARROW (or on Mac Ctrl+Opt+RIGHT_ARROW) conversely moves the anchor forward through edit history, so after traversing backward with Ctrl+Alt+LEFT_ARROW, you can go forward again by holding Ctrl+Alt and repeatedly pressing RIGHT_ARROW.
A new menu item has likewise been added for this forward navigation as well.
New edit locations are always inserted at the end, so original historical ordering is always maintained.
New edits also reset the last location "anchor" back to the most recent edit, so that pressing Ctrl+Alt+LEFT_ARROW once again brings you to the most recent edit rather than a historical one.
You can use the local history if you lost your undo redo functions.
to do that: 1/ right click anywhere on your code, 2/ Team, 3/ Show Local History, then choose the version you want according to edit time.