Hi,
I would prefer if the com browser ordered the components by description and not by filename as default.
Also if you position to a file then resort the list by description your selection remains on the lists index and does not follow the item you had selected. Meaning, if you select component TEST which is number 10 then you reorder so that TEST becomes 5 then the new item 10 is selected instead of number 5.
Also it would be nice to see methods and properties in the browser like the PB Com browser or JaCom.
Regards,
Gian
I second the default sorting to be in description.
In the far future, maybe..
• The ProgID (or ID's - I think I read somewhere it could be multiple) should be automatically presented to the user so it's not so much of a hide and seek game finding it within the "wast" output. If there is just one, maybe just grab it and put in the property field, closing the browser.
• Uninstalled OCX's could be referred to by a "browse for file" function/dialog, and then loaded/handled as needed?
• It will possible to chose the different file/COM types to show in the browser. I.e. DLL/OCX/TLB and so on... Cause the list gets fairly long when showing them all (625 items in my case). Maybe a search feature on description would be a killer way of dealing..
If Paul tells me to change the initial ordering by description I will do ASAP. This is a very easy change, but I must say that this, as most things in life, are a matter of taste. Being a low level COM programmer I prefer ordering by filename because the documentation always refers to the name of the file not the description, but I can live having to click in the filename header. The problem is when you have not choice to reorder it, like with the PB COM browser.
Haakon -
The ProgIDs not only can be multiple, but there are always at least two, one for the version and other for independent version. So you have to choose one according your preferences. It is usually best to choose the version independent ProgID, unless you want that your program will only run if a specific version of the OCX is intalled.
The browser is designed to choose an OCX and, optionally, generate the events code. At a minimum, it requires to retrieve the license key (for licensed controls), if any, and the ProgIDs. If Paul tells me to change it to only show the license key and the ProgIDs I wil do it ASAP. Of course this class with the petition of Gian of show the methods and properties. As you can see, some people ask for less information and others for more. This a non win situation.
Uninstalled OCXs can't be initialized, so it will be of no use to load them using browse for folder. Of course it will be possible to check if it is registered or not, ask if you want to install it, register it, reread the register, etc., but there is a simpler way: use regsvr32 and the name of the file. Start -> Execute -> regsvr32 <filename>.
Gian -
I will change the program to get the selected item and reselect it after reordering.
Showing the methods and properties is of no use for the purpose of this browser and will take more time. The purpose of the PB COM browser is to generate the code for interfacing with COMponents and the purpose of the JACOM browser if to generate wrapper functions, whereas the purpose of this browser is to add OCX support for FireFly. If you want to see all the information available in the typelibs, download my full TypeLib COM Browser. It is free.