Hey folks,
After I (or others on my team) import a project, Flare is terribly slow to populate the folder within the Content Explorer.
For example, after import, when I spin open one of the folder displayed in the content folder, Flare makes room in the Content Explorer pane for the contents within the folder, but the files within the folder appear one at a time, each with a long delay.
When I spin open the Resources/Images folder, there are hundreds of files within and displaying all the files within can take a very long time, depending on how far down the list of files I have to work. In cases where multiple pages of files are contained, Flare does not allow any other activity to occur (e.g., working within the text of an open topic), and the pane must completely populate before Flare relinquishes control.
Furthermore, if we add a file to the project through the Windows file system, then Flare will hang in the same way when it encounters the new file.
In generally takes about one to two seconds per file. In cases where there are hundreds, you can see this taking quite a long time.
This is something that occurred in v9 and still occurs in v10. Has anyone experience this behavior?
After Importing Project, Flare Slow to Populate Folders
-
ToddPh
- Sr. Propeller Head
- Posts: 140
- Joined: Wed Jan 30, 2013 2:41 pm
- Location: Kirkland, Washington
Re: After Importing Project, Flare Slow to Populate Folders
Are you using network-based source control for your projects (I'm assuming the answer is yes)?
I've been seeing this behavior since upgrading to version 10, though I had it to a lesser extent in 9.x as well. Nita mentioned in another thread (http://forums.madcapsoftware.com/viewto ... 68&t=18549) that using HTTPS to access SVN seemed to make a difference for her. From what I've been reading, MadCap is aware of the issues related to source control performance and is working on a solution.
I've been seeing this behavior since upgrading to version 10, though I had it to a lesser extent in 9.x as well. Nita mentioned in another thread (http://forums.madcapsoftware.com/viewto ... 68&t=18549) that using HTTPS to access SVN seemed to make a difference for her. From what I've been reading, MadCap is aware of the issues related to source control performance and is working on a solution.
Todd

When puns are outlawed, only outlaws will have puns.

When puns are outlawed, only outlaws will have puns.
Re: After Importing Project, Flare Slow to Populate Folders
Thanks, Todd. That's a good suggestion--I'll give it a shot.
-
ToddPh
- Sr. Propeller Head
- Posts: 140
- Joined: Wed Jan 30, 2013 2:41 pm
- Location: Kirkland, Washington
Re: After Importing Project, Flare Slow to Populate Folders
On the other hand, I'm using HTTPS to access cloud-based SVN and am seeing slow performance no matter what I do.
I did experiment briefly with using Tortoise to control my check in/out from Explorer without binding the Flare project to SVN. THAT method works quite well, if you're up to it.
Hope this helps.
I did experiment briefly with using Tortoise to control my check in/out from Explorer without binding the Flare project to SVN. THAT method works quite well, if you're up to it.
Hope this helps.
Todd

When puns are outlawed, only outlaws will have puns.

When puns are outlawed, only outlaws will have puns.
-
ChoccieMuffin
- Senior Propellus Maximus
- Posts: 2650
- Joined: Wed Apr 14, 2010 8:01 am
- Location: Surrey, UK
Re: After Importing Project, Flare Slow to Populate Folders
Todd, that's exactly what we do here, and it works fine (as long as you remember to add any new topics or images you create).
Started as a newbie with Flare 6.1, now using Flare 2024r2.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Re: After Importing Project, Flare Slow to Populate Folders
Hey folks,
This really seems to be independent of source control. After Flare has received the project files from source control, they exist locally. When I open a folder in the Content Manager, the display populates using local information and not source control, but still the delay persists.
This really seems to be independent of source control. After Flare has received the project files from source control, they exist locally. When I open a folder in the Content Manager, the display populates using local information and not source control, but still the delay persists.