Hi,

In dForm.addBizobj method, there is a call to setStatusText() method.

But status bar is placed unsightly in left center side of main window,

farther it disappears to quickly to read this information in normal

situation.

It happens on Windows platform. Some users may be upset of this.

Here is sample screen: http://img134.imageshack.us/i/clipboard011c.jpg/

I think that status bar right place is the bottom of window.

Did I'm wrong?

--

Regards

Jacek Ka³ucki

2009/7/9 Jacek Ka=B3ucki <laborm@rz.onet.pl>:

> Hi,

>

> In dForm.addBizobj method, there is a call to setStatusText() method.

> But status bar is placed unsightly in left center side of main window,

> farther it disappears to quickly to read this information in normal

> situation.

> It happens on Windows platform. Some users may be upset of this.

> Here is sample screen: http://img134.imageshack.us/i/clipboard011c.jpg/

> I think that status bar right place is the bottom of window.

> Did I'm wrong?

> --

> Regards

> Jacek Ka=B3ucki

>

Do you mess with the statusbar on the mainform. That is instantiate it some=

how?

In general I think that you should not manipulate the UI from the

bizobj - UI manipulation code should stick to the UI layer. Perhaps an

idea is to ask the bizobj, from the UI, for whatever you are asking,

and given the result issue the setStatusText() call.

Hope this helps,

Miguel

On Jul 9, 2009, at 3:16 PM, Jacek Ka=B3ucki wrote:

> In dForm.addBizobj method, there is a call to setStatusText() method.

> But status bar is placed unsightly in left center side of main window,

> farther it disappears to quickly to read this information in normal

> situation.

That's at the wxPython level; we don't do anything to position =

the =20

status bar.

If you resize the window, does that change the status bar =

location?

-- Ed Leafe

U¿ytkownik Ed Leafe napisa³:

>

> That's at the wxPython level; we don't do anything to position the

> status bar.

>

> If you resize the window, does that change the status bar location?

>

I found that this only happen if main form is maximized at startup.

In such situation only toolbar, menu and background of main form are

displayed correctly, status bar and even right scrollbar are displayed

garbaged.

And remains garbaged until uiApp.MainLoop(), then is redisplayed correctly.

--

Regards

Jacek Ka³ucki

On Jul 10, 2009, at 10:05 AM, Jacek Ka=B3ucki wrote:

> I found that this only happen if main form is maximized at startup.

> In such situation only toolbar, menu and background of main form are

> displayed correctly, status bar and even right scrollbar are displayed

> garbaged.

> And remains garbaged until uiApp.MainLoop(), then is redisplayed =20

> correctly.

Sounds like a wx issue - they are displaying and maximizing the =

frame =20

without resizing the internal elements and repainting during startup. =20=

It would make more sense for them to delay the display until after the =20=

event loop is entered.

-- Ed Leafe

U¿ytkownik Ed Leafe napisa³:

> Sounds like a wx issue - they are displaying and maximizing the frame

> without resizing the internal elements and repainting during startup.

> It would make more sense for them to delay the display until after the

> event loop is entered.

>

But login procedure takes place before event loop.

--

Regards

Jacek Ka³ucki

On Jul 10, 2009, at 10:22 AM, Jacek Ka=B3ucki wrote:

> But login procedure takes place before event loop.

Why is there a maximized login window?

-- Ed Leafe

U¿ytkownik Ed Leafe napisa³:

> On Jul 10, 2009, at 10:22 AM, Jacek Ka³ucki wrote:

>

>

>> But login procedure takes place before event loop.

>>

>

>

> Why is there a maximized login window?

>

Isn't. But status bar is created for main form which is maximized.

Never mind, it's not so big problem to bother you.

I will try to investigate it myself and will be in touch.

--

Regards

Jacek Ka³ucki

Jacek Ka³ucki wrote:

> U¿ytkownik Ed Leafe napisa³:

>> On Jul 10, 2009, at 10:22 AM, Jacek Ka³ucki wrote:

>>

>>

>>> But login procedure takes place before event loop.

>>>

>>

>> Why is there a maximized login window?

>>

>

> Isn't. But status bar is created for main form which is maximized.

> Never mind, it's not so big problem to bother you.

> I will try to investigate it myself and will be in touch.

I have this line in my main startup script (perhaps we should add this

to dabo):

> 154 if app.MainForm:

> 155 dabo.ui.callAfterInterval(250, app.MainForm.refresh) ## clears artifacts

Paul

U¿ytkownik Paul McNett napisa³:

> I have this line in my main startup script (perhaps we should add this

> to dabo):

>

>

>> 154 if app.MainForm:

>> 155 dabo.ui.callAfterInterval(250, app.MainForm.refresh) ## clears artifacts

>>

Problem is that existing refresh mechanism works correctly for sized

main form,

but fails for maximized :(

I tried to call app.MainForm.refresh(0) directly after main form Show()

but it won't help.

Seems like all form events were stopped till main loop begins.

--

Regards

Jacek Ka³ucki