# The form data below was edited by pmclary # 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: job000152 Status: open Project: perforce-software-p4connect Severity: A ReportedBy: p4pzp ReportedDate: 2015/02/23 12:06:44 ModifiedBy: pmclary ModifiedDate: 2015/12/08 15:14:08 OwnedBy: p4pzp Description: UI extremely laggy and unresponsive when significant changes are made. Unity Asset Store user Troy says: "When significant changes are made (say removing a large asset with many scripts), the UI for perforce in Unity becomes extremely laggy and unresponsive when changes need to be submitted. In my case, I needed to remove the uScript framework for an update requiring a change to over 1000 files. Perforce came to a crawl, so perhaps there are some issues with how it is handling its' changelist within the editor as after the submit is completed and the list is cleared.. performance returned to normal." DevNotes: 2015/12/08: Perforce Dev increasing severity to A This could probably be improved by some kind of Progress bar or feedack to user. The performance issues need to be addressed as much as possible. Priority: Medium Type: Bug