U++ framework: UppHub » TabBar. Uninitialized member

Home » Developing U++ » UppHub » TabBar. Uninitialized member

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Re: TabBar. Uninitialized member [message #20804 is a reply to message #19877]

Thu, 09 April 2009 01:41

Mindtraveller
Messages: 917
Registered: August 2007
Location: Russia, Moscow rgn.

Experienced Contributor

One more little bug. Happens when all the tabs are closed and after that parent window is being closed. Parent window invokes Accept() for all the children, and TabBar::GetData() is called. Due to one can`t set TabBar::SetCursor(-1) before all it`s tabs are closed, TabBar tries to Get(0) and fails with ASSERT.
There are many ways to correct this. The simplest one is checking if there are any tabs in TabBar before trying to Get anything:

TabBar.h, line 268:

	virtual Value GetData() const			{ return HasCursor() ? Get(active) : Value(); }

change with:

	virtual Value GetData() const			{ return (GetCount() && HasCursor()) ? Get(active) : Value(); }

Report message to a moderator

[Message index]

		TabBar. Uninitialized member By: Novo on Thu, 29 January 2009 05:39
		Re: TabBar. Uninitialized member By: Mindtraveller on Thu, 09 April 2009 01:41
		Re: TabBar. Uninitialized member By: Mindtraveller on Fri, 10 April 2009 18:19
		Re: TabBar. Uninitialized member By: koldo on Wed, 20 May 2009 15:26
		Re: TabBar. Uninitialized member By: mrjt on Wed, 20 May 2009 16:56
		Re: TabBar. Uninitialized member By: koldo on Wed, 20 May 2009 17:39
		Re: TabBar. Uninitialized member By: koldo on Wed, 20 May 2009 22:19

Previous Topic:	Cairo
Next Topic:	OfficeAutomation documented

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Sep 27 08:04:38 GMT+2 2026

Total time taken to generate the page: 0.00785 seconds