qt - C++ - Why do I create these widgets on the heap? -

-

when creating gui c++ , qt can create label example :

qlabel* label = new qlabel("hey you!", centralwidgetparent);

this creates object on heap , stay there until either delete manually or parent gets destroyed. question why need pointer that? why not create on stack?

//create member variable of class mainwindow qlabel label;  //set parent show , give text user can see     qwidget* centralwidget = new qwidget(this); //needed add widgets window     this->setcentralwidget( centralwidget );      label.setparent(centralwidget);     label.settext( "haha" );

this works fine, can see label , did not vanish.

we use pointers in c++ let live longer can use object in various scopes. when create member variable, won't stay until object gets destroyed?

edit: maybe didn't clarify enough. mainwindow class:

class mainwindow : public qmainwindow {     q_object     qlabel label; //first introduced here...  public:     mainwindow(qwidget *parent = 0);     ~mainwindow(); };  //constructor mainwindow::mainwindow(qwidget *parent)     : qmainwindow(parent) {     qwidget* centralwidget = new qwidget(this);     this->setcentralwidget( centralwidget );     label.setparent(centralwidget);     label.settext( "haha" ); }

if label gets out of scope, destructor (qlabel::~qlabel) called. docs:

destroys object, deleting child objects.

it not necessary create object on heap - put object on stack, need responsible lifetime of object (the 1 of problematic issues allocating data on heap question of "who , when should delete these objects?", , in qt handled hierarchy - whenever delete widget, child widgets deleted).

why program works - don't know - may not work (label destroyed @ end of scope). issue - how change text of label (from slot, example) if don't have reference it?

edit saw label member of mainwindow. fine have complete objects, , not pointer objects member of class, not destroyed before mainwindow is. please note if create instance of mainwindow this:

mainwindow *w = new mainwindow();

label created on heap.


Comments

Post a Comment

Popular posts from this blog

c# - How Configure Devart dotConnect for SQLite Code First? -

-
can configure following sample code ? when run following code, error : no entity framework provider found ado.net provider invariant name 'devart.data.sqlite' setting in machine.config <system.data> <dbproviderfactories> <add name="dotconnect sqlite" invariant="devart.data.sqlite" description="devart dotconnect sqlite" type="devart.data.sqlite.sqliteproviderfactory, devart.data.sqlite, version=4.6.287.0, culture=neutral, publickeytoken=09af7300eec23701" /> </dbproviderfactories> </system.data> after add below block code in app.config <?xml version="1.0"?> <configuration>   <configsections> <!-- more information on entity framework configuration, visit http://go.microsoft.com/fwlink/?linkid=237468 --> <section name="entityframework" type="system.data.entity.internal.configfile.entityframeworksection, entit...
Read more

erlang - Saving a digraph to mnesia is hindered because of its side-effects -

-
updated the digraph library in erlang implements data type side-effectful. each operation on data type saves new state in ets table -- instead of returning altered version of itself, more common in functional languages. the problem usage perspective, impedes effort store or pass around state in convenient way requiring me first "collect" state before can start juggle around. the closest solution have seen far serializer/deserializer , these have drawback tied current structure of digraphs instead of operating on abstract type -- prevents future proof solution. update pascal pointed out serializer utilizes interface of digraph, , hence eliminates drawback mentioned above. better, albeit still inconvenient, see no better alternative. what recommendation on how store digraphs? should go different data type altogether? thanks. i not sure understand concern. fact digraph stored in ets transparent in user interface, might want chnge either exchange digr...
Read more

java - Copying object fields -

-
what best way of copying classes when need have 2 independent variables? have simple class: public class myclass { boolean = false; string b= "not empty"; } do need make method : assign(myclass data ) { a= data.a; b= data.b; } is there automatic method copy (duplicate) objects in java? do need make method : pretty close. instead of making method, should make constructor. such constructors called copy constructor , , create them this: myclass(myclass data) { = data.a; b = data.b; } and create copy of instance, use constructor this: myclass obj1 = new myclass(); myclass obj2 = new myclass(obj1); copy constructor can tedious : using copy constructor create deep-copy can tedious, when class has mutable fields. in case, assignment create copy of reference, , not object itself. have create copy of fields (if want deep copy). can go recursive. a better way create deep copy serialize , deserialize object. why not use clone()? ...
Read more