I tried adding names to names resoures dll
-
Ah no! I had no idea the link was so old!
OK, I got the 1.1b, many thanks.
Maybe I can start regrowing my hair now.
It would be a good idea to hunt down those old links & update them - here’s the one I used this morning:
URL http://freelancercommunity.net/download.php?id=39Thanks pal.
-
Ya, I kinda knew I’d end up having problems by letting other sites hosting the files. I told Dwn to keep it updated, but he must’ve skipped the release…
-
Deleted the download and added a link to the forge … no more missed updates ;D
-
Hi FF…
2 more problems to report…
1. Got 1.1, unzipped it. Ran FLDev after uninstalling the previous version. It takes 6-7 minutes to load the .dll files. CPU usage goes to 100% and it’s impossible to use the PC until the dlls are loaded. Then it works normally until I save changes, when it does the same again but for about 2 minutes.
2. When it saves changes it does it as Language 1033. Some dlls use Language 0 and so those nodes are not replaced, instead two language nodes exist and the updated 1033 node is not displayed by FL.
Sending screenshots by email.
Thanks.
-
The node problem would be hell to correct; I don’t know when I’ll be able to do it.
The performance issue I can’t do much about; I’ve optimised the program as much as possible, including multithreading. I don’t see what else could be done. What are your system specs?
-
Well I’d expect multithreading to be just “normal” on single-core CPUs; it shouldn’t be slower because of it…
-
It’s a single-core 3.6GHz with 1GB Ram.
This is a new problem with version 1.1b, the previous versions were loading all the dlls within 5-10 secs.
-
Gonna have to check, but as I’ve said I have other priorities right now (just look at the letter thread). Unfortunately that means it will not be very usable for single-core CPUs for a while.
-
Oh dear.
Do you think it was the multi-thread change then?
-
I don’t see what else could make such a strong correlation while also being relatively logical. The multithreading was the largest change by far, and if the .NET threading implementation wasn’t built with lots of threads on a single core in mind, it might clog up the processor…