lmi
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] wxHTML table header alignment


From: Greg Chicares
Subject: Re: [lmi] wxHTML table header alignment
Date: Wed, 11 Mar 2009 10:04:29 +0000
User-agent: Thunderbird 2.0.0.19 (Windows/20081209)

On 2009-03-09 16:56Z, Vadim Zeitlin wrote:
> On Mon, 09 Mar 2009 16:50:38 +0000 Greg Chicares <address@hidden> wrote:
[...]
> But, just in case, maybe you should have a look at docs/changes.txt
> as this is just one of many things mentioned there. I don't know of
> anything else that might affect LMI but maybe something else there rings
> some bells for you.

I've read it, and I don't see any problems; but it does suggest
some ideas, none of which is urgent.

| - Added {wxTextCtrl,wxComboBox}::AutoComplete() and AutoCompleteFileNames().

AutoComplete() might be useful for lmi. In some "input sequence"
fields, we permit both numbers and certain "keywords"; I'm thinking
of a completion feature for the keywords. I looked at
  http://docs.wxwidgets.org/trunk/classwx_text_ctrl.html
but didn't see this function documented there; should it be?

| - Added support for drop down toolbar buttons (Tim Kosse).

Like ms excel's font, font size, and font color toolbar dropdowns?
Sounds interesting. Maybe someday we could consider merging some of
lmi's toolbar buttons: e.g., "{Varying, Fixed} column width" could
be one button with a drop-down choice. It might be nice to replace
the wxHtmlHelp "Options" button with font-controlling dropdowns.
Such font controls might also be good to use in lmi for controlling
wxHtmlWindow fonts (if wxHtmlWindow supports that).

| - Optimize wxGenericTreeCtrl::Collapse/ExpandAllChildren()

Does that suggest that the following idea would now be easier to
consider?

On 2008-02-23 03:33Z, Greg Chicares wrote:
!
! * For msw, I thought the numpad '*' and '/' keys normally worked
! like '+' and '-', but for all tree-control branches at once: i.e.,
! "expand all" and "collapse all", somewhat as described here:
!
! http://88.191.26.34/XYwiki/index.php/Tree
!
! But when I tried that with a treeview control in ms "control spy",
! only '*' had the effect I expected, and only when the root node
! was selected, so I guess wx is just doing whatever msw normally
! does. Nevertheless, if you think this would be a good enhancement,
! then please feel free to add it.

(A clarification for anyone who's testing this: in lmi's '.db4' editor,
numpad '*' seems equivalent to numpad '+' (it expands only one branch),
but that's consistent with the above-quoted description because we do
not display the root node).

| - Show busy cursor in wxLaunchDefaultBrowser and add wxBROWSER_NOBUSYCURSOR.

A stray thought: maybe we should use wxLaunchDefaultBrowser instead
of wxHtmlHelp. Our user manual is already more like a normal webpage
than a tightly-integrated help system anyway. (BTW, that's a conscious
design choice. We can have one or the other, but don't have time to
do both well.)

| - Added "enabled" and "hidden" attributes to radio box items in XRC.

Another half-baked thought: we might use that to hide certain
radiobuttons that would always be grayed on certain skins due to
problem-domain esoterica. What happens, though, if for even more
esoteric reasons such a radiobutton becomes selected (by the
program, not the user)? Would it then automatically become
unhidden?

| - Documentation for wxWidgets has been converted from LaTex to C++ headers
|  with Doxygen comments and significantly improved in the process

I've written lots of "///" doxygen comments in lmi, and I've been
meaning to ask whether you knew of any new tool that might have
displaced it. Now I don't need to ask. It's not that I dislike
doxygen; it's just that I don't read slashdot or freshmeat or
whatever, so I don't know when I've fallen behind the times.
If you want to comment more on this, please start a fresh doxygen
thread here, or wait for me to do so--I'd like to ask about your
experiences with doxygen because you may already have solved some
problems I'll be facing, and it may be a long, separate discussion.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]