Re: [Boa Constr] ZOA.zexp can't be imported?

[Hans-Peter J. <hp...@ur...>]

On Friday, 8. March 2002 05:05, Riaan Booysen wrote:
> Hello Hans-Peter,
>
> Currently you can move around a group of selected objects in 1 pixel
> increments by holding down control and using the cursor keys.
> There is a bug with wxAcceleratorTables on wxGTK which breaks this
> for you, but it works on Windows.

I've added a bug report on this one this week. 

> Try rebinding the keys under Preferences-Key bindings-Designer-Move*

Haven't found this in the menus, only KeyDefsDlg.py in source.

> You may also set the Designer grid to a lower granularity for
> moving multiple selected objects with higher precision.
> See Preferences-General-Designer-dsGridSize.

Done that before :) 
dsGridSize = 2

> > BTW: Right now, after selecting multiple objects and deselecting them
> > in a designer session, the handles of single selected objects are drawn
> > in background color thereafter. See attached screen shot. The first
> > control is selected. Disturbing...
>
> This is probably a repaint problem. Try to determine if the tags
> are actually the wrong colour or if they are just not updated properly.

I bet, it isn't.

After selecting one item, it's selection tags are drawn opaque black.
After adding a second selection, it's tags are drawn in background color
with a black edge. Thereafter, a _single_ selection is drawn with background
colored tags. Multiple selections are drawn as expected. I bet, the color of 
the multi selection tag leaks into the single selection color, which would 
explain the findings.

Would you like to give me a source code pointer into this?

> > Source formatting: Breaking long lines into a more editor friendly
> > format (say 100 columns).
>
> It's on the todo (properly handling multiple lines)
> For me the priority is not that high as I see the generated code almost
> as a resource, something you *usually* don't maintain manually.

We're all aesthetic fanatics, don't we? 

> > I18n: the possibility to wrap all strings in i18n().
>
> Maybe support for the gettext.py convention of using _(string)
> would be simplest (I think this has been suggested before)

Grmf. I really ment _()

> However there is a more general issue involved; Giving property editors
> more state, and how to manage it through the Inspector.
> Already property editors support the additional state of being linked
> to special frame attributes.
>
> A more specific solution would be to add a new specialised property
> editor dialog for strings with a checkbox for when the string should
> be _(gettext) wrapped. It could even possibly add the gettext import
> statement and _ binding when it's checked.

This is what I'm dreaming about ;) 

The question is: How can I help you on this?

> Riaan.

Cheers,
  Hans-Peter