Nubcake wrote:I just tested it with 21 new empty files it took 3 secs to close.
Usually I don't care, but I just checked now: 99 opened files here, all different sizes (real world source codes).
Starting the IDE requires 22 seconds here, 11 seconds for closing it.
I just mentioned it because it could be the problem GeBonet has. I press the close button of the window here
and nothing happens for 11 seconds. After 11 seconds the PB IDE window closes. Sometimes window title
changes to "(Not Responding)", so if I would press close again and again, it could trigger the task manager
for ending the process. I know it is slow, so I just press close one time here and everything ends correctly
after the 11 seconds.
For the user experience, it is unusual that I press the close button of an application and nothing happens
for 11 seconds. Other apps don't do that, they would close/hide the window instantly and save the
history database in the background.
Generally not a problem for me, all-thought I think some things could be improved:
The most funny thing is, the start-up splash screen is in the background, behind the main IDE window at start-up.
Makes the splash screen redundant, as I don't see it at the 22 seconds IDE start-up. Bringing it to foreground
does not work, because the IDE brings itself to foreground after loading of every file (99 times at start-up here).
Another thing is IDE start-up seems to use only one single thread. Could be made faster for an
Apple Mac Pro with 12 cores.
Looks like PB is parsing every loaded file at start-up and doing syntax highlighting. Does not make sense, because I see only
1 file after start-up has finished, so only this 1 file really requires instant syntax highlighting. Other files could be parsed later
(maybe in background or when switching to those sources), or at least the parsing could be done in threads, so it could be up to 12 times
faster on current machines, at least 64 times faster in the near future.
While we are at it, parsing in the IDE seems to be very slow generally. Working with a 9,000 lines file is not really fun, as
pressing <Return> takes 1 second for inserting every new line. Loading of the same file takes also 7 seconds (358kB, 8.718 lines to be exact).
I have the feeling this could have to do with extensive usage of Macro's.
I am used to it, so I don't want to complain. Just saying what my experience is. Maybe some things could get improved in the future,
after the chiefs heard about it.
It is such little things that make the difference between premium class cars and the cheapest cars.
