Hi,
Two questions please.
Question 1:
Is there a place to get a copy of the m_60 build, with the new icons,
available - all my usual hunting has turned up nada.
What I have at the moment is the binary based on the m_56 builds, pulled
from the qa-upload server. (installs as OO.o 3.2)
Also of course the DEVm_59 binary.
There are issues relating to Win 7 with the build supplying the new
icons, not present in the m_59 build.
More then one and different issues depending on whether MSO 2007 is also
installed or not - but maybe they are all rooted in a small block of code?
.doc files with OO.o set as default application display the ODF icon
[Actually all files set to use swriter instead of soffice will display
the ODF icon]
.doc file type is erroneously displayed, in all cases where the OS
displays it (fly overs, File Open dialogs, Windows Manager) if MSO 2007
is not also installed with OO.o
[This gets particularly annoying if in a library view one sees multiple
documents with the same name, but different file types and descriptors (
xxx.odt, xxx.doc ), the file descriptors are no longer displayed, but
the actual file type is. ]
.doc files if associated to OO.o AND MSO 2007 is not installed on the
system become lost within the LIBRARY VIEW functions of the windows manager
[This bug does not appear if MSO is also installed OR if neither MSO or
OO.o are installed, it acts as if the OS is expecting the assigned
application, OO.o here, to supply some information and it's not getting
it..just a guess really. The file is of course displayed if one browses
by physical directory rather then virtual library]
Question 2:
Should I open the issues based on what I am seeing with the m_56 based
build from qa-upload? -or- is there a newer build available (m_60
perhaps) where I can check now?
If there is going to be a push for these new icons in 3.2 and if 3.2 is
still targeted to 'officially' support Win 7 it needs some checking.
Anyway - I have pretty good step by step instructions and screen shots
of all this...but I'm hoping most of it is due to the earlier build
basis so don't want to muck up the issue tracker if they are not in the
current (in Hamburg) builds.
Thanks
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
