Hi Frank

I found some time ( took a little longer than I thought to get back to
this ) to look again at the patch, the latest iteration is attached to
the iz issue, hopefully it addresses all of the issues :-)
On Mon, 2008-08-11 at 13:30 +0200, Frank Schönheit - Sun Microsystems
Germany wrote:
> Hi Noel,
> 
> >> since of course we want it to handle the placeholder text
> >> as one big chunk only (i.e. when the user starts to type, the place
> >> holder is completely removed). Not sure how difficult this would
> be.
> >
It seems to work (but.. /me is not very unfamiliar with gui things ) I
made it so the SvURLBox thingy now accepts an externally defined
placeholder ( I hope where I defined the resource for use with the
formcontrol browser is acceptable ), if the placeholder is displayed,
the first keypress results in the placeholder getting selected, this
should ensure it gets immediately replaced with what you type.
> >
> >> Care needs to be taken here: if the method "hasField()" returns
> true,
> >> then the control is bound to a database column, in which case the
> >> "Link" checkbox should be disabled. If it is "false", it should
> >>   be enabled (and checked by default?).
hasField is not accessible here ( it's in the model implementation ) but
what I did I should work. But... I couldn't test this, you see I am so
stupid I don't know anything about base and after fiddling for a while I
couldn't see immediately how to bind the imagecontrol to a dbcolumn. I
would be really grateful if you could test that bit for me :-)
> 
> >> - do you know "makeAny( <value > )"? Saves the
> >> Any aValue( <value > );
> >> useValue( aValue );
> >> construct you often use.
> > how can you say its a 'construct I ofter use'? afaiks I only did it
> > once!!! :-P
> 
> Ehm ... well ... you used it once in this patch, and once in the
> previous version, IIRC :)
haha, actually I used uno::makeAny in the first version of the patch,
the pattern above in the second and in the latest version I revert to
makeAny again ( I have no idea why I did it differently in version 2)

also, I did put in a potential #FIXME in the patch, I wasn't sure about
the implications of returning early ( you will easily see what I am
talking about in the patch, just look for '#FIXME?' ) so I took the
route of 'leave the orig code path alone as much as possible' maybe you
have some additional input/idea there.

additionally;
* as promised I added some idl doc for the [X]GraphicObject.idl
* I did do a WAE fixup ( but on Linux only ), you use windows right? if
you come across any windows ones then let me know

Thanks,
Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to