# The form data below was edited by norman_morse # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # Status: Job status; [open/closed/suspended]. Required # Project: The project this job is for. Required. # Severity: [A/B/C] (A is highest) Required. # ReportedBy The user who created the job. Can be changed. # ReportedDate: The date the job was created. Automatic. # ModifiedBy: The user who last modified this job. Automatic. # ModifiedDate: The date this job was last modified. Automatic. # OwnedBy: The owner, responsible for doing the job. Optional. # Description: Description of the job. Required. # DevNotes: Developer's comments. Optional. # Type: Type of job; [Bug/Feature]. Required. Job: job000181 Status: closed Project: perforce-software-p4connect Severity: C ReportedBy: StuartHarrisonSumo ReportedDate: 2015/03/25 05:43:44 ModifiedBy: norman_morse ModifiedDate: 2015/04/06 14:23:41 OwnedBy: StuartHarrisonSumo Description: The "Enable Perforce Integration" setting is not saved/restored from the Registry. A quick scan through the code suggests that in Config.cs, PerforceEnabledPrefName is unused. This appears to be related to the inability for you to disable Perforce Integration using the Perforce Settings > Enable Perforce Integration checkbox. Perforce server version "p4 -Ztag info" : ... serverVersion P4D/NTX64/2014.2/978861 (2014/12/19) P4Connect release (look at the bottom right corner of the Perforce Configuration window) : P4Connect 2.7 betaR.12101 Unity3d Version : Unity 5.0.0b22 (32 bit) Operating system version, 32bit or 64bit : Windows 7, SP1, 64 bit. DevNotes: The "Enable Perforce Integration" now is saved in the configuration in Beta2 Perforce starts up with this default as "off". Type: Bug