Quote: "Quote: "You can't open a .DBA file; period. It will crash immediately with the following:"
fixed in v1.4.0 b8. However individual .dba files don't receive the same parsing and highlighting as those contained in a project."
That's understandable.
Quote: "
Quote: "Observation of performance"
I am seeing different results than you. I do see spikes up to 52% when changing to tabs with large source files, or opening all includes. These are spikes of a second or less not constant."
I have set up a new PC; so far I am experience the opposite. Now the Beta 7 version works without any performance hits; Indigo 'correctly' uses zero CPU when not focused, instead of 70-80; then when running a load project it takes about 50%. The new PC isn't a top of the range hardware unit.
It might be the extra CPU core that makes the difference. I am sure the problem that occurred was to do with the components and the CPU architecture. Taking 100% of one core is 50% cpu usage. Taking 100% of a single core system is using up all the systems resources. I am noticing an improvement with compile speeds too.
Quote: "Quote: "Auto-complete bug"
I'm not able to duplicate. Can you provide a better list of steps?"
Neither can I on Windows 7. On XP when I set beuitification to title case; and type in something in lowercase, pressing CTRL enter to finish the autocompletion appends the command after what you type in, in stead of replacing it. For example; here all lowercase characters where typed and the title case letters were auto completed: posit
Position Camera.
But this does not happen on Windows 7 here.
One thing I left out in the request list is the ability to convert absolute paths to relative .DBA project paths, instead of only files in the same folder or absolute paths (eg:sub-folder\file.dba instead of c:\project\sub-folder\file.dba)
Will try out the latest version;
but the site shows Beta 7.
Edit
OK with beta 7, on this PC, the status bar flickering seems to occur with large projects. Also the CPU usage when Indigo is not focused does go up to about 40-60 %.
Quote: "Something that does contribute to the CPU hit is the Line Overview. Hiding it does improve performance."
On here, the line overview works smoothly in Indigo 1.33. This version does not slow down for about 1 hour of usage in a 40k line project. In 1.4, the slow down occurs immediately after compilation of large projects.