ProEject

SYSTEM · **Posted:** Sat Sep 17, 2011 6:50 am

spicydog wrote:

SYSTEM wrote:

Was the bug specific to Finnish?

I guess that what Guinness is saying here is that you were the first one who found out that these strings where missing in the .lng (master) file and translated them into Finnish :mrgreen:

No, these strings were present in the .lng file when I found the bug. Looking at the language files, they were also translated in every single file.

spicydog wrote:

Now that these strings have been translated in all languages and all ProEject's dialogs are multilingual I wonder why in the downloaded "Language" folder I see:

Dutch.lng
English.lng
German.lng
Italian.lng
Romanian.lng
Spanish.lng

but no Finnish? :shock:

The Finnish translation is in the file "suomi.lng".

spicydog wrote:

I take this opportunity to thank once more Guinness for his spectacular achievement and for his outstanding dedication.

+1

spicydog · **Joined:** Mon Mar 16, 2009 11:56 am **Posts:** 250

SYSTEM wrote:

The Finnish translation is in the file "suomi.lng".

Yes, but where is the "suomi.lng" file?

As I said the downloaded "Language" folder contains only:

Dutch.lng
English.lng
German.lng
Italian.lng
Romanian.lng
Spanish.lng

SYSTEM · **Posted:** Sat Sep 17, 2011 9:10 am

spicydog wrote:

SYSTEM wrote:

The Finnish translation is in the file "suomi.lng".

Yes, but where is the "suomi.lng" file?

As I said the downloaded "Language" folder contains only:

Dutch.lng
English.lng
German.lng
Italian.lng
Romanian.lng
Spanish.lng

OK, I have investigated.

First, I got the filename from my local copy. IIRC, the file was still called "suomi.lng" when guinness released ProEject 1.0.0.0.

I see you've got the list from the beta version. Indeed only the major languages are available in that version. (I'm going to update the Finnish translation soon, after which it'll hopefully be included as well.)

In version 1.0.0.0, all languages are present, and the file in question is called "Finnish.lng".

Finally, when I reported the issue, I used ProEject 1.0.0.0. The beta hadn't even been released at that time.

spicydog · **Joined:** Mon Mar 16, 2009 11:56 am **Posts:** 250

SYSTEM wrote:

I've got the TIP_EJECT_1 and TIP_EJECT_2 messages in English even though I use the Finnish language.

As I said in my previous message "these strings *were* missing in the .lng (master) file" and that's why they were showing in English despite you set ProEject in Finnish... Got it now?

*were* as in "at the time you posted the phrase quoted above"

SYSTEM · **Posted:** Sat Sep 17, 2011 1:06 pm

spicydog wrote:

SYSTEM wrote:

I've got the TIP_EJECT_1 and TIP_EJECT_2 messages in English even though I use the Finnish language.

As I said in my previous message "these strings *were* missing in the .lng (master) file" and that's why they were showing in English despite you set ProEject in Finnish... Got it now?

*were* as in "at the time you posted the phrase quoted above"

I had got it already.

SYSTEM wrote:

No, these strings weren't missing in the .lng file. Looking at the language files, they are also translated in every single file.

I used the word "were" in the same way. I haven't updated my local copy after noticing the bug.

Let me rephrase: at the time I found the bug, these strings were available in the master language file and translated to all languages.

I'll edit my previous post to make it clearer.

spicydog · **Joined:** Mon Mar 16, 2009 11:56 am **Posts:** 250

What was missing was the link to these strings... In other words the dialogs corresponding to these 2 strings (when you were running ProEject in Finnish) were not reading the .lng file but rather the hardcoded (English) strings in the executable.

I would say that matter should be clarified now :mrgreen:

SYSTEM · **Posted:** Sat Sep 17, 2011 10:00 pm

spicydog wrote:

What was missing was the link to these strings... In other words the dialogs corresponding to these 2 strings (when you were running ProEject in Finnish) were not reading the .lng file but rather the hardcoded (English) strings in the executable.

I would say that matter should be clarified now :mrgreen:

OK, got it.

So, likely the answer to my original question is "no", and the bug affected all non-English languages.

Guinness's post could have been clearer...

SYSTEM · **Posted:** Sun Sep 18, 2011 2:06 am

A glitch occurs if "Minimise ProEject on startup" is enabled and "Minimise to the system tray" is disabled.

SYSTEM · **Posted:** Sun Sep 18, 2011 4:15 am

SYSTEM wrote:

I'm going to update the Finnish translation soon

Done!

SYSTEM · **Posted:** Thu Sep 22, 2011 9:12 am

My observations: the beta version of ProEject successfully closes all windows but terminates after that. It leaves windowless processes running and doesn't even try to eject the drive.

I have uploaded the complete log file here.

guinness · **Joined:** Mon Aug 27, 2007 2:00 am **Posts:** 3707

Sorry about not getting back sooner I've been a little busy outside of the world wide web, so I hopefully have answered the questions asked in the previous posts :mrgreen:

Quote:

Was the bug specific to Finnish?

No, it was present in all languages other than English of course. The problem was simple to fix but long and painful to find. Ejecting from the drive you're running ProEject from is not possible, I therefore have to move ProEject to the %TEMPDIR% and then eject the drive from the %TEMPDIR% (it also self deletes itself) what I was failing to do was copy the language file across too, hence why English was always being shown. This is not the case anymore and instead of copying the language file, I just grab the appropriate language strings.

My explanation was poor due to being posting when I was in a hurry.

Quote:

I guess that what Guinness is saying here is that you were the first one who found out that these strings were missing in the .lng (master) file and translated them into Finnish

Correct, I just pointed out that you can now use Finnish (suomi) and it will translate those strings, since SYSTEM/you was/were the first user to bring this to my attention.

Quote:

Now that these strings have been translated in all languages and all ProEject's dialogs are multilingual I wonder why in the downloaded "Language" folder I see:

I haven't included all the languages from V1.0.0.0 only those that have been fully translated for the latest beta. I have included a file with the new language strings though if you want to translate.

Quote:

I take this opportunity to thank once more Guinness for his spectacular achievement and for his outstanding dedication.

Right back at those who have helped me test this application or translated, your time is just as precious than mine.

Quote:

What was missing was the link to these strings... In other words the dialogs corresponding to these 2 strings (when you were running ProEject in Finnish) were not reading the .lng file but rather the hardcoded (English) strings in the executable.

Exactly!

Quote:

A glitch occurs if "Minimise ProEject on startup" is enabled and "Minimise to the system tray" is disabled.

FIXING...Now it's FIXED!

Thanks SYSTEM for the Finnish translation. I decided to use the English terms for languages e.g. Deutsch = German as this was down to the automatic detection of the users system language (I hope people don't mind or are offended by this.)

Quote:

My observations: the beta version of ProEject successfully closes all windows but terminates after that. It leaves windowless processes running and doesn't even try to eject the drive.

Weird, looking at the log file what happens if you turn off file flushing?

Thanks all.

guinness · **Joined:** Mon Aug 27, 2007 2:00 am **Posts:** 3707

ProEject V1.1.19.31 (Beta)
This Beta release includes a couple of bug fixes and source code changes, so if you know AutoIt or are interested in the code then please take a look. This release also includes ever language (even those which haven't been updated yet!) I've also included standalone versions of ProEject x32/x64 for those who wish to have more control* especially if you wish to monitor the return codes of ProEject. I would advise that if you have a x64 version of Windows and use x64 Portable applications to use the x64 version of ProEject, otherwise the x32 is just fine.

*For example if you were to use ProEject in a custom application and were monitoring when the PID had closed, then using the wrapper version would return as immediate since the PID would be for the wrapper not ProEject (Windows!) Therefore by using the specific architecture version of ProEject it's now possible to monitor when the PID of ProEject closes.

SYSTEM · **Posted:** Tue Oct 04, 2011 6:23 am

guinness wrote:

Sorry about not getting back sooner I've been a little busy outside of the world wide web

I was wondering why you were so inactive. Welcome back!

guinness wrote:

Quote:

My observations: the beta version of ProEject successfully closes all windows but terminates after that. It leaves windowless processes running and doesn't even try to eject the drive.

Weird, looking at the log file what happens if you turn off file flushing?

Thanks all.

Exactly the same result.

(new log file)

guinness · **Joined:** Mon Aug 27, 2007 2:00 am **Posts:** 3707

Weird, it looks as though it just stops! I have an idea of what it could be, perhaps the batch file I use to monitor when ProEject terminates is closing ProEject a little early as I have it set to wait 30 seconds and if nothing close ProEject, this is done in case ProEject was to hang. Would you mind if I were to PM you to find the problem?

SYSTEM · **Posted:** Tue Oct 04, 2011 8:37 am

guinness wrote:

Would you mind if I were to PM you to find the problem?

No problem.

ProEject

Who is online