summaryrefslogtreecommitdiffstats
path: root/media/tools/player_x11
diff options
context:
space:
mode:
authoroshima@chromium.org <oshima@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-06-02 19:57:25 +0000
committeroshima@chromium.org <oshima@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-06-02 19:57:25 +0000
commitd5e4a478d52c048f60b514cdffc64320ffa4cd1b (patch)
tree9af276b38456b8e77939fcb7b7cfc1e66a8a5db4 /media/tools/player_x11
parenta08df20f67c559c6594be07040a8d8eadce568dd (diff)
downloadchromium_src-d5e4a478d52c048f60b514cdffc64320ffa4cd1b.zip
chromium_src-d5e4a478d52c048f60b514cdffc64320ffa4cd1b.tar.gz
chromium_src-d5e4a478d52c048f60b514cdffc64320ffa4cd1b.tar.bz2
Create CompositePainter once for a widget instead of ref count.
There is a issue in adding new composited child after the ref count of painter became zero. RefCount::Release does not tell if it's been deleted so it can't remove the painter key from G_OBJECT(widget). I could have changed RefCounted::Release to return true, but I took this approach because new child will be added later in most use case (like info bubble), and it's more efficient to keep the painter rather than creating and deleting each time. BUG=none TEST=none Review URL: http://codereview.chromium.org/2449010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@48757 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'media/tools/player_x11')
0 files changed, 0 insertions, 0 deletions