Re: [poedit-users] unable to update a particular .o file from template

Vaclav Slavik <[email protected]>
Newsgroups gmane.editors.poedit.user
Message-ID <[email protected]>
Hi,

Cristian Secară wrote:
> > Please always try the latest version before reporting bugs -- at
> > this time, it's 1.3.7_pre2 -- can you still see it in there?
>
> The latest _stable_ version (according to www.poedit.net) is 1.3.6,
> so my report was based on that. 

I know, that's why I asked you to test against the latest available 
version. You see, that's where the changes since the last version 
went and by first verifying that the bug wasn't fixed already, you're 
saving both your and our time.

> But if youl like, ok, version 1.3.7_pre2 does the same, no
> difference here regarding this problem.

OK, I can reproduce it. What you're seeing is actually something 
completely different: there's a bug that doesn't disable poedit's UI 
when an external program is launched. In this case, the program is 
msgmerge and it takes a *long* time to run on a catalog as huge as 
yours (*). So just give it some time.

Regards,
Vaclav

(*) This will get better on multi-core CPUs when GCC 4.2 for MinGW is 
released.

-- 
PGP key: 0x465264C9, available from http://pgp.mit.edu/

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

_______________________________________________
Poedit-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/poedit-users
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (GNU/Linux)

iD8DBQBGhVhAxDYa/UZSZMkRAjyWAJ9bjYdPL19NCFTjzsStbIjiKhg3xACgpSFG
YJmxXQzrNABI0ZmD+EFwQK4=
=E8RU
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.