Is there a way in MKS Integrity to clean up the member view? We have files that when you open the Member History view just look like massive spider webs. It would be nice if we could click a revision, hit a magic button, and only see the revisions directly tied to that revision (i.e., one level out from it). Does anything like that exist in MKS? (obvious: I'm new to MKS)
From the Member History window, go to menu -> View -> Change Filter to bring up the Filter Revisions dialog.
Modify the Filter Revisions based on whatever criteria you care about--in this case, probably based On Branch.
Click OK.
The member history should now display a filtered member history.
Unfortunately, there is no functionality for a "single button filter by current branch". If your organization has a current maintenance contract with PTC, you could have an appropriate contact log a feature request for this functionality on usability grounds.
Disclaimer: I work in PTC Technical Support.
As far as I know all my colleagues have the same problem. I can only give you the hint that when you have the Member History window you can set a filter in the menu [View].
Better would be to have some right-click menu for that - but this might be something related to an external script?
If you are using dynamic Member History views you might also consider having always 2 dynamic Member History views open.
One as list that shows all.
One graphical with a filter enabled with View -> Change Filter
If you never close that graphical history view the filter will remain active
even if you restart the Integrity client.
Related
Can anyone help me create a User Story for the dragging and dropping feature, where I can drag and drop projects from "New Project" to "In progress" etc Column
User-stories describes a feature from the user's point of view, making clear what the user wants to achieve. We cannot invent stories for your users: normally, you should discuss this with your users. But if you're learning and it could help, here an hypothetical example:
As a project manager I can drag a project icon in the "new project" column across my kanban board and drop it on the "in progress" column, so that I can easily and intuitively communicate that a project was started and is still going on.
Be aware that referring explicitly to a drag and drop seems very detailed and might not leave much room to propose better solutions. In this regard, you need to keep in mind that a story is not a detailed specification. It's just a placeholder for a conversation. Personally, I'd rather go for something simpler like:
As a project manager I can easily chose a project to launch and show that it is currently in-progress, so that the other users know on which project they may work.
I would then discuss with the user about the details of the story. Maybe drag and drop is the way to go. Maybe keyboard control (tab to select, space to chose target) is needed for accessibility reasons. But perhaps I'll discover that some users prefer to update the status in the project card if it's on the screen.
Anyhow, during this conversation you'd write down all the expectations, positive and negative, for the acceptance criteria. For example:
Dragging from "new" and dropping on "new" cancels the drag&drop operation
When dragging from "new" a visual feedback should be given to show the project moving
During the dragging, the use of the escape button may cancel the operation.
When the project is dropped by accident, the user may undo the operation.
When the project is successfully dropped on the "in progress" column, any open view of the project card should be immediately opened to show the new status of the project.
Attempting to drag a project, of which the user is not responsible, should lead to an error message about missing authorisations, etc.. .
The method list dropdown, as well as the project and class view drop down boxes are no longer working within the editor window with VS2013 update 2.
I suspect that this issue began after the update, but I cannot be certain ( I didn't pay much attention to it until this morning, although I performed the update when it was released)
For example, I expect VS to look like like
(from the screenshot posted in the accepted answer here however it looks like:
I've tried the following:
Run as administrator and regular user
Remove and readd the toolbar via Option -> Text Editor -> C# -> Navigation Bar
I've also noted that
issue occurs across all files
it affects all parts of the navigation bar
The dropdown's do update to reflect the current position of the editor
Any ideas on how I can resolve this?
So, I'm kinda new to SQL Developer, but I always heard a lot about it and how it was good. The thing is, my SQL Developer never showed my tables, nor had a "Tables" tab. Sorry if this is a dumb question, but, I've searched everywhere and, wherever I search they simply show that SQL Developer automatically generate the "Tables" tab when you connect. This never happened to me.
One more question, all of a sudden, my SQL Developer toolbars changed and the old ones simply vanished. And, when I say "all of a sudden" I mean it. I closed it and, when I opened, it changed. Also, the buttons doesn't work, none of them.
Your screenshot shows that you have the Data Modeler extension active. All those toolbar buttons are for creating logical data models and ERDs.
It's a little weird as you have a worksheet active, so the worksheet/SQLDev toolbar should be active.
Glad a restart helped.
If this happens again, try Window > Reset Windows to Factory Settings
You're looking at the DBA view. You probably want to be looking at the Connections view. Go to View and choose "Connections". That will bring up the window that contains the tree view that lets you navigate to different object types (like tables) rather than the tree view that lets you navigate to different DBA tasks.
If you are on Windows, try this
View(from the top menu bar) --> Connection(click it)
Clicking on Connection will open the Connection view with all the tables.
Is it possible to view a "timeline" (history) for a selected file for like 50 commits? I mean changes made to this particular file and and view commits when they were made and users who changed them? I know Xcode got some powerful version control features, I just can not find this one.
What it sounds like you want is the "Blame View", if we were on the terminal you could write git blame <file-name> to see the commit/time/and user for every single line of a particular file. In Xcode you can accomplish the same thing by activating the blame view. I've posted a picture to show you where the Blame View button resides. From there you should be all set.
For xcode 11.0, If you select a file, changes for that file is available on right panel.
The commit history is in the Version Editor.
Select the file for which you want to see the commit history. Then go to View > Version Editor > Show Version Editor (or just select the Comparison view from the top-right toolbar icon - same place as the Blame view).
Clicking on the commit label below the editor will reveal the history including dates.
Yes. Xcode's Comparison view is exactly for that. When you select a source file, and choose comparison view, you have a time-machine like user-interface that besides letting you compare any two versions of the file, will also present (when you hover) all the commits of the file with their descriptions. This UI opens when you click the clock button in the bottom between the two versions of the .
Pay attention, that Xcode will list all the commits, but will fail to show the content of versions of the file if the file-name or path changed. I think Xcode makers thought that because sources are considered "different" if they are named differently or located differently, there's no point in showing them. It may be, though that they just overlooked the --follow parameter to git.
Xcode 13
Enable Code Review (default: cmd+shift+opt+Enter to toggle)
On the right of the bottom bar (or if you have the debug area opened: the bar that sits on top of it) there are a couple of buttons used for comparing commits: clicking them allows you to pick which commits to use for the comparison on the current file.
Enable Code Review button
Comparison buttons on Debug Area
I'd like to know if it ever makes sense to provide some functionality in a piece of software that is only available to the user through a context (right click) menu. It seems that in most software I've worked with the right click menu is always used as a quick way to get to features that are otherwise available from other buttons or menus.
Below is a screen shot of the UI I'm developing. The tree view on the right shows the user's library of catalogs. Users can create new catalogs, or add and remove existing catalogs to and from their library. Catalogs in their library can then be opened or closed, or set to read-only.
The screen shot shows the context menu I've created for the browser. Some commands can be executed independently from any specific catalog (New, Add). Yet the other commands must be applied to a specifically selected catalog (Close, Open, Remove, ReadOnly, Refresh, Clean UP, Rename).
Currently the "Catalog" menu at the top of the window looks identical to this context menu. Yet I think this may be confusing to the users as the tree view which shows the currently selected catalog may not always be visible. The user may have switched to the Search or Filters tab, or the left pane may be hidden entirely.
However, I'm hesitant to change the UI so that the commands that depends on a specifically selected catalog are only available through the context menu.
The Windows User Experience Interaction Guidelines for Windows 7 and Windows Vista states (pg233):
“Don’t make commands only available through context menus. Like shortcut keys, context menus are alternative means of performing commands and choosing options.”
The Apple Human Interface Guidelines states (pg189):
“Always ensure that contextual menu items are also available as [pulldown] menu commands. A contextual menu is hidden by default and a user might not know it exists, so it should never be the only way to access a command.”
In your case, opening and closing the catalogue appears already available through the +/- buttons in the tree itself, so you’re already consistent with the Windows guidelines, if not the Apple guidelines. IMO, the only reason to put them on the context menu at all is if they're the default (double-click) action (which they're not right now). Rename may also already be available by directly selecting the name of a selected catalog, but you may want a pulldown menu item for that any way since that may be no more discoverable than the context menu. The rest of the commands probably belong on a pulldown menu in addition to the context menu.
As far as the Catalog pulldown menu being redundant with the Catalog context menu, you may want to consider organizing your pulldown menus by type of action, rather than class of object, in order to provide an alternative organization. As you’ve realized, context menus already organize commands by class of object. In addition to providing an alternative organization that some of you users may find more intuitive, this may simplify your menubar. For example, rather than a Catalog and Family menus, you can have a single Edit menu with Add, Delete, Rename, Copy, etc. where these commands apply to whatever is selected, whether it be a catalog, folder, or family. If they don't apply to the current selection, they're disabled, but if it makes any sense in your app, make them apply.
BTW, what’s the difference between Add Catalog and New Catalog?
In general, it's a bad idea to have menu items accessible only through a contextual menu. Many users may not think to right click on an item to find out what actions can be performed on an item.
From your description, it sounds like it would make sense to have a 'Catalog' menu that disables menu options that are not currently relevant. For example, if no catalog is open, the 'Close' menu item would be greyed out. Similarly, the 'Open', 'Remove', 'Refresh', etc. items would be greyed out if no catalog is selected.
I suppose this depends on your user base, and who you're targetting your software at. Personally I wouldn't expect the user to be able to deduce what functionality is available when it is essentially "hidden" until they right-click on the correct item.
If it were me, I'd have a toolbar shown with the functionality exposed on there. By default the buttons would be disabled, and clicking on a node would enable the appropriate buttons based on the context. You could have this in addition to your current right-click options.
As a rule, I've always treated right-click menus as a redundant (i.e not necessary for operation of the software) shortcut to functionality for "power users".
I would leave the menu item out because the user doesn't have a way to see what catalog they are modifying if the treeview is hidden which can create problems if they think a different one is being shown.
Though, the accessible solution would be to trigger it with the keyboard also.
Yes. One key feature of UI is "discoverability": can the user find the function?
If you think that having a top-level menu doesn't make sense, based on the context, then you could have a menu button (scroll down) labelled (e.g.) "Actions" at the top of the pane.