From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14971 invoked by alias); 30 Apr 2008 14:12:41 -0000 Received: (qmail 14960 invoked by uid 22791); 30 Apr 2008 14:12:40 -0000 X-Spam-Check-By: sourceware.org Received: from imr1.ericy.com (HELO imr1.ericy.com) (198.24.6.9) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 30 Apr 2008 14:12:19 +0000 Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id m3UECCwp019601; Wed, 30 Apr 2008 09:12:12 -0500 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 30 Apr 2008 09:12:12 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [PATCH:MI] Return a subset of a variable object's children Date: Wed, 30 Apr 2008 16:22:00 -0000 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA042910B6@ecamlmw720.eamcs.ericsson.se> In-Reply-To: <18456.6496.685993.987138@kahikatea.snap.net.nz> From: "Marc Khouzam" To: "Nick Roberts" , "Vladimir Prus" Cc: X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-04/txt/msg00702.txt.bz2 > > > I was thinking that only a small number of children would ever exist > > > simultaneously. Scrolling might make that a larger number but maybe > > > it could be arranged to delete children that go out of view. > >=20 > > I wonder if deleting children that are not visible is possible/desirabl= e. > > In Qt, item data is requested only when item is drawn. I think SWT's Tr= ee > > can be configured the same way. However, I don't think I saw any way, in > > either, to detect than an item is no longer visible. Marc, can you tell= if > > SWT allows that? >=20 > In Emacs I would just find the first and last line numbers and work out > which elements were displayed from that.=20=20 I'm not sure what SWT allows... In DSF-GDB, we have a LeastRecentlyUsed queue which allows us to know which varObj is the oldest (which implies it is not visible), and we can deleted once we have reached our limit of 1000 varObjs. I still think that GDB should avoid having the requirement of 'deleting old varObjs' toward the frontend. It would be nicer if GDB would keep its efficiency, not matter what the frontend did in this case.