Hi Felix,
Zhang Xiaofei wrote:
Hi Mikhail,
Thanks to Frank's fix, I can dump the two dialogs in the specification
with the tool, please find the sample doc and the generated files in the
attachment.
And I need your advice on the following issues:
- Currently the layout is adjusted according to the en-US strings, I
fear that a localized string with larger length ( e.g. de ) will be
trimmed, maybe we should leave more spaces in the label field or is
there a more flexible solution?
Please take a look in svx/source/dialogs/webconninfo.cxx. There is a
constructor of WebConnectionInfoDialog class that does something similar
( using GetCtrlTextWidth() ). It calculates the required size of the
buttons and resizes them if necessary.
In case of labels that stay before the textentries if an additional
place is needed the dialog should become wider and the text fields
should be moved.
It is a little bit different in case of big label with the comment. It
is multiline, so the new height should be calculated ( get the text
size, divide it to the current label width and multiply to the current
text height, retrieved using GetTextHeight() method ).
- I attempted to modify the strings for de in the .src file, in VS2003,
when I was to save the changes, the IDE reminded me to save with
encoding, I'm a little confused about the many choices in the comboboxes
of "Encoding" and "Line endings". Would "Unicode - Codepage 1200" and
"Unix(LF)" be OK?
The encoding should be "UTF8".
The "Line endings" can be set according to the used system I assume (
Windows in your case ).
By the way, only en-US entries should be introduced by a new
implementation. But you want probably to test the long text handling.
Hope that helps.
Mikhail.
I'm looking forward to your guidance.
Thanks and Best Regards,
Felix.
P.S.: I find some small problems in the basic dialog editor,:
- Open a sample doc with dialogs, then open the Basic Macro Organizer,
the dialogs under the doc cannot be displayed in the tree view, I have
to open a dialog from "My Dialogs" or "OpenOffice.org Dialogs" to open
the dialog editor, then access the dialogs in docs from the "Current
Library" combobox. After the dialogs be opened, the corresponding items
in tree view become properly displayed, too.
- When the "With Title Bar" property of a dialog is set to "Yes",
adjusting the "Height" or "Width" properties will result in unwanted
values. For example, in the sample file every time when the value in
"Height" field is changed, the value of "Width" field automatically
jumps up by 3, changing "Width" causes similar problem.
I wonder if those issues are still unfiled.
Mikhail Voitenko
Hi Felix,
The author of the dialogdump tool will investigate the problem when he
has time, but currently he is very busy so we should proceed further.
First of all please change the basic dialog so that the help, cancel
and ok buttons do not have any text ( Label property in the dialog
editor ). Instead of that they should have the related type ( Button
type in the dialog editor ).
After that please let the dialogdump generate the output without using
the file ( as you did already ). The output contains contents of the
.hrc and .src files. Additionally it contains the beginning of the
.hxx file ( the exception will have to be filtered out :) ). Having
this files you can try to create the implementation of the dialog.
A number of examples of such implementation can be found in uui
project ( they are represented by four files ".hrc, .src, .hxx, .cxx"
with the same prefix.
I do not know any documentation regarding the creation of such
dialogs, so please ask questions based on the examples.
Best Regards,
Mikhail.
Zhang Xiaofei wrote:
[...]
Mikhail Voitenko
[...]
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
