Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
New really cool tool
Message
From
09/02/2022 09:37:07
 
 
To
09/02/2022 07:02:02
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Miscellaneous
Thread ID:
01683500
Message ID:
01683504
Views:
85
Wow!!!!!!!

I could've added more exclamation points :-)

So nice. Thanks for mentioning this tool Tore.

>Hi everybody,
>
>not all of you use Thor, for whatever reason. And even fewer have joined Thor Discussion Group. This means that a lot of you haven't received the last emails from foxprothor@googlegroups.com.
>
>On Monday this week Jim Nelson, creator of Thor, shared a tool which he and the late Matt Slay has developed. A few minor bugs have been fixed, and it now seem to run perfectly. This is an edited version of Jim's emails:
>
>February 2, 2022:
>
>Hi everybody --
>
>In honor of my very good friend, the late Matt Slay, I want to share the last tool we collaborated on.
>
>The tool is not actually our concept at all, as it derives from two other tools that have been in the community for a long time (see the original message, below, that got us started.)
>
>
>All that we did was to customize an existing tool, add some features, eliminate some bugs and provide some customization. (Actually, not much to get excited about.)
>
>It's called rather simply: Do Form Explorer with (Object Reference)
>
>The trick to making this a really valuable tool was to find the following unexpected way to call it. We have added the following line of code into our production code and also for use in our IDE:
>On Key Label F9 Do Form Explorer with Sys(1270)
>You can invoke Explorer at any time by hovering over any object in any form and using the hot key, and Explorer will open for that object.
>
>We find that this is invaluable in Production; it also works in IDE the same way although we do not use it there as often.
>
>One last thing: a hidden UI feature is the ability to edit properties by double-clicking in the value column of the grid. You can also view and edit properties of arrays the same way.
>
>Peace

>
>February 7, 2022:
>
>Hey everybody --
>
>Attached is the source code for Explorer (hoping this will be work better than my last attempt). For each of the attached files, remove the TXT extension and you should end up with two SCXs and one VCX.
>
>You should be able to use this right out of the box. As noted in my previous message, I assign a hot key, whether in production, in development, or when writing code in IDE:
>On Key Label F9 Do Form Explorer_Modal with Sys(1270)
>You can invoke Explorer at any time by hovering over any object in any form and using the hot key, and Explorer will open for that object and the form it belongs to.
>
>We have found this to be an invaluable tool that lets you get inside forms while they are running in production.
>
>There are also some very pleasant unanticipated uses. Try any of these:
>• Do Form Explorer_Modal with _Screen
>• Using the hotkey over a form in the IDE, such as GoFish, PEMEditor, or Thor, will let you view their insides. Since Explorer is a form as well, you get use it to spy on itself.
>• Using the hotkey over a form or class you are editing in the IDE works like a reduced-function version of the Properties Window or PEMEditor. A curiosity, maybe, but navigation is easy and so is modifying properties.
>• Make the following little piece of code available in your app (for me, available from a context menu available only to Devs). It created a collection of ALL your open forms to browse.
>Local loForms As 'Collection'
>Local lnI
>loForms = Newobject('Collection')
>For lnI = 1 To _Screen.FormCount
> m.loForms.Add(_Screen.Forms[m.lni])
>Endfor
>Do Form Explorer_Modal With m.loForms, 'All Forms'
>
>A few technical notes:
>• This does not depend on Thor being installed (amazing, eh?)
>• The three files in this release are intended to be self-contained and have no external references.
>• The VCX is the base which Matt and I worked on and shared. (If anybody were to make changes to share with the group, they should be in the VCX)
>• The SCXs are our forms where we customized the base VCX as desired.
>• I always use the modal form in production. (Use the modeless form at your own risk.) You may well choose to change some of the native form settings as appropriate for your environment.
>• Nodes are added to the TreeView only when you expand a parent node.
>• The grid on the right is recreated each time you click a node.
>• The filter box finds all matches in either the property name or value.
>• There is a browse button at the bottom left, available if Explorer (known as Dora to her friends) can determine the cursor related to the current node (such as a grid or column in a grid)
>• There are a number of properties and methods, in both the form and its main object "TreeContainer", available for customization. These are easily accessed using PEMEditor, as they are are Local . There's a description field for each.
>
>It may seem odd that most of the customizable properties and methods are in the object TreeContainer, rather than in the form. This is by design; Matt's use of this was to embed the TreeContainer into his own form in his app, my use is to have a stand-alone form.
>
>P.S.: Offered as-is.
>
>Enjoy!

>
>You can download it here: https://www.vfphelp.com/download/explorer.zip
*******************************************************
Save a tree, eat a beaver.
Denis Chassé
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform