Change-Id: Icc9051bad16c0e66c9e9f631c487a2facde72e9f

Change-Id: I6e960db9659f5122a45c4cf173e680bb782acf76

Change-Id: I0c72231a932186130246bab343653ecb563a41f2

Change-Id: I7fb7cf919e3f46dd03a18b1cb95fa881915f9642

Change-Id: Ia126588580b76cc69944bb974d93cb51ee0356dd

Sometimes it matters; doing a disposeAndClear() instead can change
the order of destruction profoundly. Fix a number of issues from:
    "vclwidget: change all vcl::window fields to be wrapped in VclPtr"

Change-Id: I3127d3ed973458e8299156453258e167dbdb8ccf

Change-Id: I6d12eb32e9c8fcb403473c41b3a6eb2f29fe8639

Change-Id: Icc5b6e924dfeec7a7da4f654d79b17fe91ce1418

Now this is in dispose, not a destructor we can use RTTI nicely.

Change-Id: I6d92dce7a1c76a194a0f354a7a49a49a35c11794

Change-Id: Ic542fac901edb87418abc1d460ed4e7d9bad67c5

Also correct dispose ordering in dbaccess.

Change-Id: I31c9115662da2f81e1b22be91ee58e2862076b8e

Change-Id: I76489f833949a556b657010e5d5cba6f64c89ba7

Change-Id: Ie719ed153f2de462ced194fe67b6dd78933b354e

Change-Id: Icd2e193b66ace8212d1af086192abf0c43c5953f

Change-Id: I50490ad8957e8069e72e855f0f5a3b694218fd6b

Change-Id: I6846e56062fdde394e4039de7cde42b0560f34b3

Change-Id: I55e3153bf38af376fe367d575ceb19f5b4405e1c

Change-Id: I2015f517695682f17fe5c03a8df0171a427717bf

Change-Id: I3bfd7933d2cddf707662d10e9366e0c82f33d276

Change-Id: Ib47b2ec3cb54e374675981ad929856f43987418f

Also remove an over-optimistic assert & ref-holding in dispose piece.

Change-Id: I6ce6abb666c8143502fc450a26e1ba2aac787455

Also continue to move to extended toolkit/ API.

Change-Id: Ibd4337b014ee096c84d0ad4435e2c5de1b258afe

seems there was a lot of shared_ptr usage floating around...

Change-Id: Icd05243170eb8493709275fc36bf986fc194b781

Change-Id: I828f0e3841c396008cb5e51dec322d9d89f3a7c1

Change-Id: I1629cb6574361d6dd855140d61f38229ab593ed7

Change-Id: Ib243b14e3476d3a65ad1414e3843511420201c7c

Change-Id: I0393d906657b94cc547986a2165960a85d36cf48

Change-Id: I2aa5c818d4f2c07926bda539da30ada63620f69d

Toolkit has traditionally had a very odd lifecycle relationship
with VCL - start to fix that; first partial cut.

Change-Id: I77e5e62ebde101d32746d12d83dae92c49970001

Ultimately we will want to ref-count & VclPtr OutputDevice instances
separately from Window - but for now merge. This helps fix the amazing
lifecycle foo in toolkit/

Change-Id: If40ee9f645c87aff08815926205e908205bdd67a

Change-Id: I46f2bf5115f2b80990fdcac75bd31615c4221b9e

Change-Id: Ia8b6984a8a9bdf6f32cf5ebfc971a6921796eece

Change-Id: I533eede461d173bd270e5a309fa13aab37bc0a13

Change-Id: I7ce41ecff1eee4cb45f685a0f4dddb31225ac542

Change-Id: Idef33e0b8e6c986c8808c2b611c5f4b6632e7511

that need to be wrapped in VclPtr, and convert several sites

Change-Id: I1fb1ed164a99642a0c1ccbf433eb14df688fa476

Change-Id: Ia8c438984409a7b719f5756f9be30ba9e90c57dc

by using a new utility method in vcl::Window
This means that we don't have to make all our dispose
methods safe to call more than once.

Change-Id: I2110c7de4a86c70fdc97dd8fd318c86b56865374

Anything that used to be 'delete'd should be disposeAndCleared()
in the new world.