User interface looks tiny on high resolution screens

Symptom

When working with high resolution screens, the Designer's user interface looks tiny and/or incomplete.

Solution

• Change Windows' SideBySide behavior in the Registry:
  • Open regedit as an Administrator
  • Select the key: HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > SideBySide
  • Right click in the righ pane and choose NEW > DWORD (32 bit) Value
  • Give it the name "PreferExternalManifest"
  • Double click PreferExternalManifest and give it Value 1 as Decimal.
  • Close regedit
  • Now windows will detect specific "Manifest" files when launching programs
• Create a Manifest file for Stambia DI Designer
  • Create a Text file named "stambia.exe.manifest" in the Designer's directory
  • File content:

  <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
  <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
      <description>stambia</description>
      <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
          <security>
              <requestedPrivileges>
                  <requestedExecutionLevel xmlns:ms_asmv3="urn:schemas-microsoft-com:asm.v3"
                                 level="asInvoker"
                                 ms_asmv3:uiAccess="false">
                  </requestedExecutionLevel>
              </requestedPrivileges>
          </security>
      </trustInfo>
      <asmv3:application>
          <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
              <ms_windowsSettings:dpiAware xmlns:ms_windowsSettings="http://schemas.microsoft.com/SMI/2005/WindowsSettings">false</ms_windowsSettings:dpiAware>
          </asmv3:windowsSettings>
      </asmv3:application>
  </assembly>

• Restart the Designer

Making SVN Subclipse to ask again for credentials

Symptom

You installed the subclipse plugin in the Designer to manager your SVN repositories.

You added your repositories and checked the box to save the user / password when the credentials where asked.

So now you don't have to enter the logins again at each operation.

The problem is that now you want to change the credentials and do not find any menu or option to change it.

Solution

As explained in the sublipse documentation that you can find below, the solution is, if you are using the SVNKit client (default) to delete the following file:

<stambia_installation_dir>/configuration/org.eclipse.core.runtime/.keyring

The credentials of subclipse are stored in this file, so after deleting it and restarting the Designer, they will be asked again and a new file will be created.

Here is the link to the subclipse documentation:

http://subclipse.tigris.org/wiki/PluginFAQ#head-d507c29676491f4419997a76735feb6ef0aa8cf8

Deleting this file will remove also the passwords for any additional plugins that is using it to store credentials

Cannot open a workspace

Symptom

Upon opening a workspace, the loading screen hangs or disappears completely. Either way, the workspace cannot be opened.

Solution

This kind of error tends to happen when the designer is closed abruptly. To open a workspace that is affected by this behaviour you may need to delete the files cache.xml and workbench.xmi.

Below the paths to the files that need to be deleted:

your_workspace_dir\.metadata\.plugins\com.indy.emf.uri\cache.xml

your_workspace_dir\.metadata\.plugins\org.eclipse.e4.workbench\workbench.xmi (note: deleting this file will reset some Designer settings to defaults, such as the Perspectives and Views layouts).

If the above solution does not resolve your problem, do not hesitate to send your case to the Stambia support team, explaining what you have already tried and attaching the log file that you can find in: your_workspace_dir\.metadata\.log

Error "NO_TOKEN_AVAILABLE" when activating a license

Symptom

When trying to activate / apply the Stambia License in the Designer, the following error is thrown:

NO_TOKEN_AVAILABLE

Solution

This error might come from multiple causes:

1. All the licenses available for your company are already in use, so as indicated, no token is available at the moment.

-> The solution in this case is to wait for a license to be available or to check with people using it.

2. The machine where the Designer is started is not registered in the license server.

Depending on the license type used by your company, the license might be linked to the MAC address of the machine using the Designer.

-> The solution in this case is to check with the support, or with the administrator of your license server, if the MAC address of the machine is allowed.

3. You have multiple network cards in your machine, including for instance virtual cards, bluetooth cards, etc.

There is a known Java bug that appear in some Java versions that avoids us to retrieve the correct list of MAC Addresses of the machine.

Therefore, a wrong list is sent to the license server, that so doesn't recognize the machine as authorized.

Here is the Java bug:

http://bugs.java.com/view_bug.do?bug_id=8021372

The solution in this case is:

-> Upgrade Java to a version where this bug is fixed / not happening

-> Or de-activate all the other network cards to have only the one authorized by the license server. Then, restart the Designer, and apply the license.