Hi Chip: To get around these issues I am thinking of setting up a more standard Find box. Perhaps something like hitting ctrl-f3 to open it and then entering a string to search for, selecting the scope of the search, a particular language in the document or the entire document and then a search button or other options. That way you could enter a string for whatever element you wanted to find, enter <string and then find all the string elements in a language or in the entire document. Enter <menu or <dialog etc... and find those elements. Also that would allow for finding particular elementlelements by their id value search string of id="mythingy" and find that particular element in one or all languages as described above. In fact it would allow for searching the element values although those might be problematic since they will be in diferent languages. That said there might be a good reason to search for a foreign language word or phrase if known so this new search would allow that. Anyway, so far this seems the most flexible method and resembles the current Microsoft Find controls in functionallity somewhat. Rick USA ----- Original Message ----- From: Chip Orange To: gw-scripting@gwmicro.com Sent: Thursday, June 23, 2011 9:54 PM Subject: RE: WETranslator Proposed Feature Comments Wanted
Rick, treeviews and listviews are sub-elements of dialogs, so why would you include them on your secondary list? also, you really do need to include menu on your secondary list, since a menu can exist outside of a dialog (the one for the app menu), and so there would be no way to get to it. finally, I'd include group at least, to allow some finer positioning within a dialog. you know, you could avoid the speed problem, and so not limit the user, by having them click on a command button to "show xml" if they wanted to see it, and it would sync up and show the xml only then. hth, Chip ------------------------------------------------------------------------------ From: RicksPlace [mailto:ofbgm...@mi.rr.com] Sent: Thursday, June 23, 2011 12:01 PM To: gw-scripting@gwmicro.com Subject: WETranslator Proposed Feature Comments Wanted Hi Guys: My ReadOnly TextBox for displaying the contents of a xml file as you modify it was slow just cursoring up and down all elements in all languages. To speed it up i am going to add a find command of sorts to jump around to major elements in the scripts and then we can cursor within those elements which will be light years faster. A normal find will not work because of having multiple cultures represented within segments of the xml file. Here is my basic idea for moving around a xml script's major elements using a Find Dialog of sorts: Display A ListBox of Language Elements in the script with their ID values: Have a secondary list of: <language Element <strings Element Next <dialog Element Next <treeview Element Nextt <listview Element A user will cursor up and down the Language List and the selected language will be set for each index changed operation. when user clicks on one of the choices in the secondary list: The cursor will be set to that position and the xml document will scroll that tag into view. From then out it is just a matter of cursoring through the selected element to find whatever is being looked for. Can you think of any other major xml elements to include in the secondary list? I want to keep it simple but effective so I did not put in sub elements like menus menuitems, buttons and all that jazz. Let me know if you have any ideas before I start coding this puppy up. Rick USA
