What to implement first? (Page 3 of 8)

What I mean is that for example, I am writing some script and want to insert a procedure just where I am but just double clicking in the object event, the procedure is inserted at the top of script whatever we do.

mathmathou
Thanks for the suggestions.

+1     Constraints are useful and can save a lot of coding/memory/time if used natively.

Please please please please Father Christmas..... I want a DOM HTML Parser.....

I had a chance to play around with My Visual DB. It is a great application especially for people like who are not programmers. Instead of adding further features to existing ones, adding some core components would be better approach as they are sourly missing. After core components completed enhancing existing features may be looked at.

Core components I like to see. In order of importance in my view:

1. Ability to add my own About window and application exe icon. (Perhaps these futures are already implemented. If so, please direct me to an info how I can do them as I couldn't find a way.)

2. Treeview. We can work around this by using tab pages at certain degree but not enough.

3. Menu.

4. Toolbar. (It's not as important as above ones)

5. Editable grid. (this can be added later on too)

Once again, thank you for your work to offer us such a great application.

is there any plan/schedule to implement at least item 1 and 2 on my previous post above?

Hello Dmitry/Father Christmas,

Like every end of year, here is my Christmas present wish list

• TimeOut control on HTTPGet/HTTPGetFile : as you added the possibility to handle exceptions (with the True option), can we have control on the timeout duration ?
  

• Threads : I can imagine that this hard to implement, but when downloading a file (or a even a page), sometimes the application freezes. This is because the main thread is waiting for the download to complete and Application.ProcessMessages is of no use in that case. But if you can not implement thread management, could you had the Work, WorkbBegin and WorkEnd Indy HTTP properties (you're using Indy right ?) ? This way we can use the Application.ProcessMessages and prevent the application from freezing.
  

• A text/XML/HTML parser : Pos is ok, PosEx is better, a real parser would be awesome !!
  

• Maybe TRegEx if I dare
  

Thank you father Christmas, I promise I've been a good boy

Cheers

Mathias

It's great news on-grid editing may be coming soon!!!

Treeview PLEASE............

I'm bit puzzled. Why there is no radio button component in MVD yet?

Some helpful tune ups would be handy:
1. On database tables tab, ability to move db table tGrids to arrange their order.
2. Multi select components settings where applicable. i.e.
http://prnt.sc/dac89d
btw, it seems anchoring missed on the above image window.

edit:
I forgot to mention having global user defaults settings in MVD.
For example, user may prefer to use certain type of (Properties) comboboxes, panels, tGrids and so on. If we have global components properties setting then we wouldn't have to set component properties again and again with each use, only when needed.

mathmathou
I think MVD needs plugin system.

Hello.

Sorry but I can't understand your question.
What exactly do you mean?

Do you need an example how to use it in the login project?

Hello Dmitry,

Sergen has found a clever workaround to my question about it, but I think à help system could be really valuable to MVD and to the application we develop.

Could you had a way to open contextual help file page based on the index or ID of the page in the .chm file ? Or the Shelexecute command ? But I really feel that the HelpContext and HelpIndex would be better.

Either way, I'm sure you'll your best.

Thank you and cheers

Mathias