|
From: PGridDev <pgr...@ya...> - 2011-11-01 19:07:25
|
Thanks Asa
Re not using the control: I mean that I don't have much time for it lately... You already mentioned the wxWidgets 2.9 control which has the same name, so you know the alternative :-)
Duly noted for the memory leak, I will investigate, maybe this week-end.
About the scrolling, if I understood you correctly, you want a behavior similar to Windows explorer, where dragging an object abovethe top or under the bottom of the visible part of a tree will trigger scrolling as long as the cursor does not come back in the tree window.
If so it sounds like a good idea, but is going to be some work, so if you don't mind please enter the request in the Feature Tracker (helps me not forget and gives a chance to other users to add comments):
http://sourceforge.net/tracker/?atid=462819&group_id=51305&func=browse
Cheers
Ronan
On 31/10/2011 21:34, asadilan indrabudi wrote:
> Hi Ronan,
>
> I did not try it with the sample.
> I have an application that uses the tree ctrl, the earlier version.
> what it does is build trees, allow double clicking, drag and drop, automatic scroll (drag the item out of the window/ into the window, the tree automatically scroll)
> and attaches data to every item in the tree.
>
> What i did, i just replace the files( the source and the header ) and run my app like as usual and thats when i noticed the memory leak.
>
> the scrolling:
> lets say i have a small window and really a lot of tree item with child item and stuffs. i expanded the view (all tree item are expanded), what you will see is a a lot of tree items that wont fit into the window.when this happen, a scroll bar will appear.
> what i was going to do was when user drag an item up, to the item that can t be seen, i want the tree to scroll up so that the item above will be seen. same thing with going down.
> What i implemented now is by checking the tree size limit, it will determnine if the dragging should be up or down.
> Once its determined, i just do scrollto the next item.
> So far so good, the only flaw happen when user is trying to drag up and down up and down without releasing the mouse button.
> what i found is everytime the cursor enter the window, onbegindrag event will called.
>
> Please let me know if further information needs to be provided.
>
> If you are not using wxTreeListCtrl, is there an alternative that people use now or you just dont use it as much as u dont really need it?
>
>
> Thank you very much Ronan.
>
> Asa
>
> On Sat, Oct 29, 2011 at 1:24 AM, PGridDev <pgr...@ya... <mailto:pgr...@ya...>> wrote:
>
> Hi Asa
> I don't use the control much lately, but I am the maintainer...
>
> Can you be more specific about the memory leak? (does it happen with the provided sample? When doing something in particular ?)
>
> I do not understand the question about scrolling: the content part of the control is a scroll window, scroll bars appear as soon as the window is too small ?
>
> Regards
> Ronan
>
>
>
> On 27/10/2011 20:16, asadilan indrabudi wrote:
>> Hi guys,
>>
>> Any of you use this class?
>> i am experiencing a memory leak when using wxtreelistctrl 1104 and not with the earlier version, can anyone confirm?
>>
>> how do i scroll the window with wxtreelistctrl?
>> btw this is not the 2.9 wxtreelistctrl but wxtreelistctrl from wxCode.
>>
>> Thanx
>> Asa
>
|