Access Violation with latest Virtual TreeView
UML modeling tool derived from StarUML compatible with Windows 7-10
Status: Abandoned
Brought to you by:
janszpilewski
Menu
▾
▴
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hello,
I am using the last release of Virtual TreeView on GitHub but every time I put something on a diagram I get an access violation and I cannot open the treeview that contains that node.. I am doing something wrong?
thanks
It is a well known problem. As mentioned in README.txt the last compatible version of Virtual TreeView is 5.1.3. Maybe one day someone familiar with Virtual TreeView will be able to take a look at that.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
thanks Janusz... I may have found a solution...
but honestly, I understand your frustration in managing this big project alone. May I suggest you move the project on GitHub... I think the community over there could be interested and you would get for sure much more contribution and visibility. Sourceforge is practically dead in the development community.
Sourceforge indeed seems to be losing its focus on the source code and is becoming yet another freeware site just happy to show some advertisements when files are downloaded. Some projects come even with no source code at all. Moving to Github would be more practical with updating first to a Git friendly Delphi release as the currently used XE5 is SVN only. But it is an idea worth considering.
Have you found any clues about problems with VirtualTree View?
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi Janusz,
sorry for the dealy but I have been travelling before Christmas. From my analysis it was the automatic ordering that was giving the isse. I just inactivated that option from the standard ones and I got rid of the error. Not sure it is the best way to solve it but it does the trick
I looked at it too and it looks that indeed auto sorting was added in the more recent versions. However as nodes are built in several stages sorting them as soon as they are created lead to problems. So I disabled auto-sort too and the release 6.7.1 is built with VTV 6.2.1. Hopefully it will stay stable for a while now.