# 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: job000351 Status: closed Project: perforce-software-p4connect Severity: B ReportedBy: colinbday ReportedDate: 2015/09/23 12:30:28 ModifiedBy: norman_morse ModifiedDate: 2015/11/09 15:09:10 OwnedBy: colinbday Description: Configuration saving does not work properly on OS X. When set to use EditorPrefs, P4Connect simply just did not actually remember any settings after restarting Unity. Workaround was to change to use a config file (and annoying cause we have to constantly ignore this file in all our external p4 tools), now P4Connect remembers settings, however now the settings window still states it's using "EditorPrefs", touching it and saying to use editor prefs again breaks it all over again. DevNotes: Priority: High norman_morse After investigating this issue, I was initially able to reproduce it, but it went away after I erased all existing settings and then connected to the server, and then "save settings" again. I think Unity gets confused with old registry entries from version 4. Type: Bug