pctoledo wrote:
In my initial code SEARCH_OPEN, was using Form_1.StatusBar.Item (1) to get the current open folder, but your suggestion included the name of the selected file, then the only way out was to use Form_1.Tree_1.Cargo (Form_1.Tree_1.Value)).
"Cargo" is undocumented property and not a obligation using it here. Getting path info from a full file specification isn't difficult nor unknown method.
The HMG Easy Build can be used to compile the demos of the SAMPLES folder, but can also build any other project HMG in other folders. So I thought it best to limit SEARCH_OPEN only when the SAMPLES folder is selected. So the search will be based on the selected folder, searching forum function / events / controls related to the current folder.
IMO unnecessary limitations are not good programming practice; instead programmer should open easy and free ways to user as soon as possible. For example if I have a project named "browse" out of <hmg>\SAMPLE folder, what problem may arise when I want search "browse" on forum ?
When any folder is selected, different SAMPLES, the button HMG Forum will open hmgforum
Again, IMO this is a wrong behavior.
Sorry, everything in this subject are different personal points of view and discussing is meaningless. Lets author of program will select his best way.