Don't turn this thread into an annatar help thread He already has one!

Due to the holidays I have to delay the beta release to beta testers by a few days. This, of course, means that the final release is delayed as well. Sorry.

I may be late testing the beta, my internet isn't working, but it will get fixed soon.

(currently at teh library)

I'll send you my E-mail.

Well, I have run into a bit of an annoyance. This will probably push back the beta a day. Sucks.

Anyway,

For some reason, you cannot easily edit subitems in a listview. The only control powerful enough for proper editing of subitems with a treeview and listview combined is the FlexGrid by ComponentOne studios. This costs money to use. A few hundred dollars, iirc. Thus, I am not going to use it.

Designing my own component is possible, but it is something I do not want to do, nor is it practical from a time spent vs. reward point of view.

So, my question to you all is, is it alright for me to do the following:

When the user clicks on an item or subitem,  a dialog box will pop up allowing them to edit the item or subitem. The user can click OK to confirm the changes, or cancel to disregard them.

Sound OKAY?

I will post an example screenshot of what it will look like, shortly.

I am sorry this is taking longer than expected. I am very busy here in Japan, and when I am not, I like to rest or go out with friends . Not program, haha .

Here's the dialog: http://img181.imageshack.us/img181/9731/sinseditoreditdlgpo3.jpg

Cool. Well, Everything is finally done. I am smashing a few bugs, and then I'll email the beta to you and the rest of the testers.

Ill try to add a few more features to the release while fixing any issues with the beta.

-Ian

awsome

you said tomorrow on the 10th, where is it?

It will be released when I am not feeling like shit, so that I can get the redrawing of the tree to behave how I want it to. Since my whole system was based on an indexable collection of strings for the file data, and I have to replace that collection with an indexable collection of row states... it could take quite a while to accomplish that.

Sorry for the delay; however, it will be well worth the wait when it does come out (I am shooting for a weekend release as long as I feel well). 

And, when I get started on v1.1.0, where I won't have to deal with the basic parsing bugs and where I have my system set up andwith well defined behavior, I will be able to focus on adding features without worrying about breaking something.