I'm unable to find a way to reset Enterprise Architect (15.2) fully into its default settings. Is there one? I tried googling and exploring the menus without success.
No, the only way to reset to default settings is to uninstall, and reinstall EA. And even then you might need to do some cleaning in the appdata and the registry to be sure.
EA stores some of the settings in the registry, and some of the settings in the appdata folder in your profile.
The registry settings can be found here:
Computer\HKEY_CURRENT_USER\Software\Sparx Systems\EA400\EA
The appdata settings here:
%appdata%\Sparx Systems\EA
If you are trying to restore to original view, on Sparx 15.2, Choose Start/Workspace
Choose Start, Workspace and change or select appropriate workspace, including default. This will change your view and windows.
Related
The new version of VSCode 1.75 contains the new feature Profiles, which can be accessed via [Settings-Wheel]-[profiles].
One can now create profiles with different extensions and switch between them.
It would be great if a workspace would automatically use a specific profile.
Is there any way to bind the profiles to a workspace/working directory so that I can set up a workspace to automatically select a specific profile when I open that workspace?
So far I have not found a way to do this.
As it turns out, VSCode does this already. You just have to follow the correct order:
You select a specific workspace / folder and set your profile there the way you want it to be for that workspace - I take a workspace for C++ and uninstall everything I don't need for C++ development.
Now you can choose another workspace - for example one for Python. I create a new profile (I like to use one based on my base profile where I had everything installed so far) and remove everything from it that I don't need for Python development - for example the C/C++ development tools.
If I now switch back to my C++ workspace, I find all the settings there again as I left them.
The nice thing is that I don't just deactivate extensions as before - I actually uninstall them from the profile.
It makes the Extensions area much cleaner.
The situation is, I want to share my settings of vscode.dev to others. That could include
extensions installed
tabs opened (not files, but some extension related tabs such as panels or previews)
So the person who clicked on the shared link can go to vscode.dev, but with my configurations.
Try to use Settings Sync, its the easiest way: Settings Sync
You could try to create a settings.json too, and share that file with others.
I think the only solutions you have here is to use either GitHub Codespaces (Dev Containers) or store config in repository.
Basically you will not have a link for preconfigured vscode.dev. The idea is to have all required configuration in devcontainer.json file committed it to repository. So whenever the repository is opened VSCode uses the file to configure environment.
Also you can change you settings in Workspace and right click on extensions and click "add to workspace recommendations". That will create .vscode/extensions.json, .vscode/settings.json and commit .vscode folder into repository.
TLDR: commit VSCode configuration files into repository and open repository in vscode.dev
Look into Profiles, which can be enabled in your Settings (currently experimental but will be made generally available in vscode v1.75 due out very soon.
Current setting in Stable: Workbench > Experimental > Settings Profiles: Enabled
There is no setting for Profiles in the Insiders Build, it is just enabled by default. I assume when v1.75 Stable comes out that will also be the case.
See v1.75 Release Notes: Profiles:
We are happy to announce that the Profiles feature is now generally
available in VS Code. A Profile can include extensions, settings,
keyboard shortcuts, UI state, tasks, and user snippets. You can
customize VS Code for different development scenarios like data
science, documentation writing or for multiple programming languages
like Python or Java. If you have different VS Code setups based on
workflow like Work or Demo, you could also save those as different
profiles. You can open multiple workspaces (folders) with different
profiles applied simultaneously.
{image omitted]
You can also export and import profiles to share them with your
colleagues, friends or students to help them get started with VS Code.
The following video demonstrates how to export a profile using a
GitHub gist in order to share it with someone. Users that receive the
profile link can preview the shared profile in VS Code for the Web and
import it to their local VS Code instance.
There is a nice mp4 demonstration in the link, but it appears SO would take that format.
You can export a Profile to a Github Gist so that it can be imported by someone else or to a local file you can share (or yourself to a new maching, etc.) - my demo shows all the settings, UI State and extensions it can include.
More info on Profiles at v1.69 Release Notes: Settings Profiles
I'm building a VSCode appliance in docker with multiple pre-installed extensions.
By default the extensions get enabled when a session is created including a settings file in $HOME/.local/share/code-server/User/state/.json.
When I disable an extension in the UI the extension gets an entry in this config file meaning that it is disabled.
Is there a way to disable an extension before a session is created?
I was looking at the $HOME/.local/share/code-server/User/settings.json file but in the documentation I can't see an attribute for that.
thanks in advance
There was an option to turn off extension for the specific project.
Unfortunately, this option is not longer available:
Feature Link(used to work): Ability to enable extensions only on specific workspaces #15611
i know that the default profile name when i installed websphere was Appsrv01, I want to create my own AppSrv02 but the location of my IBM Websphere was in C: and i dont have any write permission, i dont have any admin rights also..
using COMMAND-LINE, I want to make my profile folder to be writable, so that my newly created AppSrv02 will be list down in the profile names in my RAD.
Please help me. Thanks
So that's your problem. In order to have a usable profile in WAS, your user must have write permissions. See this link from WAS ND infocenter, it applies to WAS standalone too.
http://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.installation.nd.doc/ae/tpro_manage_nonroot.html
If you cannot change the write permissions to this profile, you'll need to create your own. For this, you can either use WAS Profile Management Tool, WAS CLI or you can create your profile using the Configure profiles... link in the WAS server creation wizard you posted. I'd use the RAD way because RAD validates, within the IDE, the proper permissions that you need to create and use the profile within RAD.
First check whether you have admin rights or not if your using User/Guest profile, by creating any new folder in C drive where IBM WAS is installed.
If you have Admin rights, than right click on RAD run as administrator. It should work fine.
If Profile doesnt show up in drop down, Configure new profile and try checking that way.
If you dont have Admin rights better install RAD in any local drive other than C
Running Eclipse with Admin rights and removing the read-only tick for the AppServXX folder/WAS folder couldn't help me... cause I copied the WAS server from another PC :). So for those of you who want to move / migrate your development environment:
I did a search inside the copied WAS, Eclipse and the project's workspace folder for their old paths (with Total Commander, feed the results into a list) and dragged all the files (except the log ones) into my editor (NotePad++) and did a replace in all open documents for the new paths. It's a bit lucrative, but it took only 10 minutes for me and afterwards the WAS server in Eclipse showed the correct profile and it also did start up well.
I want to move my menu settings of TGit from one PC to other, but cant find them on HDD. Is it in registry somewhere? I'm on Windows 7 if that is important.
The last comment of TortoiseGit Issue 1013 seems to show those entries are in:
HKCU/Software/TortoiseGit/
Marco Eckstein points out however in his article:
There are some values which should probably never be shared between different TortoiseGit installations, e.g. CurrentVersion.
There are some values which you may not want to share between installations, e.g. those beneath the subkey HKEY_CURRENT_USER\SOFTWARE\TortoiseGit\History if you have one installation at home and one at work.
Some values will only be created when you change the configuration to be different then the default.
E.g., a new installation will not have any values for context menu configuration. If you would use a .reg file on another new installation, that would not be a problem. But if the other installation would already have values for non-default configuration, you would not overwrite the non-default configuration with the default configuration by importing a .reg file.
His script Set-TortoiseGitSettings.ps1 will help set the right configuration across workstation.