FLEXnet Publisher identifies your machine using a combination of information about the hardware on this
machine. No personal data is used in creating this ID. Small changes to your machine, like switching dis-
play cards, upgrading memory, or changing hard drives can cause the license to become "damaged". A li-
cense can also be damaged by changing the system date by more than one day. When this happens you
will need to repair the license.
SlickEdit
®
Core automatically detects damaged licenses and launches the SlickEdit License Manager.
You will be prompted to enter your license key. The number of repairs is limited, but enough are available
to handle any reasonable hardware changes. If you run out of repairs, please contact Product Support.
If enough hardware is changed, then this will appear to be a different machine and you will have to activ-
ate the license as though this was the first time Eclipse with SlickEdit Core was run. In that case, you will
lose the activation you had previously. Therefore, we strongly recommend that you deactivate your li-
cense prior to making substantial changes to your computer's hardware.
Adjusting the System Date
Changing the system date on your computer could damage your license. The SlickEdit
®
License Manager
records the date each time the product is run. If you run Eclipse with SlickEdit Core with a system date
that is more than one day earlier than a previous run then your license will be damaged. This is part of the
tamper protection on time-limited licenses, like a trial license or the SlickEdit Core subscription.
Changing your system date is a normal part of testing time-based behavior in the software you are devel-
oping. For example, you may need to set your clock ahead to test alerts on a task management program.
As long as you don't run Eclipse with SlickEdit Core (or another FLEXnet Publisher licensed product)
while your clock is set ahead, you will not have any repair issues. If you do need to run SlickEdit Core,
your license will be damaged when you run again at the current date. When this occurs, you can repair
the license as described in
Repairing a License
. The number of repairs is limited, so you should be cau-
tious about running SlickEdit Core when your clock is set ahead. If you run out of repairs, please contact
Product Support.
Daylight savings time will not cause this to occur since it is only adjusting the date by one day. Only
changes larger than one day will trigger this.
Uninstalling SlickEdit
®
Core
To uninstall SlickEdit
®
Core:
1. In Eclipse, select
Help
→
Software Updates
→
Manage Configuration
.
2. Select
SlickEdit Core
from the list.
3. Right-click and select
Uninstall
.
Uninstalling SlickEdit
®
Core
13
Summary of Contents for Corev3.3 for Eclipse
Page 1: ...Think Slick Corev3 3 for Eclipse...
Page 2: ......
Page 3: ...SlickEdit Core v3 3 for Eclipse...
Page 5: ......
Page 6: ......
Page 14: ...xii...
Page 20: ...xviii...
Page 22: ...xx...
Page 23: ...Chapter 1 Introduction 1...
Page 41: ...Chapter 3 User Interface 19...
Page 61: ...Chapter 4 User Preferences 39...
Page 80: ...BODY BODY HTML HTMLEOF Restoring Settings on Startup 58...
Page 82: ...60...
Page 83: ...Chapter 5 Context Tagging 61...
Page 97: ...Chapter 6 Editing Features 75...
Page 124: ...Code Templates 102...
Page 238: ...Figure 6 49 Test Parsing Configuration Example 1 C Refactoring 216...
Page 241: ...Figure 6 51 Test Parsing Configuration Example 3 Reviewing Refactoring Changes 219...
Page 250: ...228...
Page 251: ...Chapter 7 Language Specific Editing 229...
Page 328: ...306...
Page 329: ...Chapter 8 Tools and Utilities 307...
Page 350: ...328...
Page 351: ...Chapter 9 Macros and Macro Programming 329...
Page 360: ...338...
Page 361: ...Chapter 10 SlickEdit Core Dialogs 339...
Page 375: ...Find and Replace View 353...
Page 491: ...Chapter 11 Appendix 469...
Page 567: ......
Page 568: ......