AutoHotkey Community

[sinkfaze]

Since the gears are already in place with iWeb_TableParse and iWeb_TableLength here's a conceptual framework to set in motion retrieving the table/row/cell reference for a text element:

[sinkfaze]

I did a slight re-write of jethrow's Learner build to mimick the old style for a proof of concept. I have re-added the old iWeb Function section of the script, but instead of a dynamic Edit box it's a static ListBox. When you press Ctrl+e while your mouse is over a page element, the recommended function calls are loaded to the ListBox. When you double click on one of the recommended calls, it is output to the code box in the writer.

I still lean towards an external script writer, but hopefully this will give a glimpse of how to output from the viewer to the writer.
_________________
Try Quick Search for Autohotkey or see the tutorial for newbies.

[tank]

I havent dived into your code yet
something should cause a selected example to copy to the clipboard i think double click ctrl + c i dunno what feels right but something


your choices for example seem intuitive
I definately think im going to keep that bit you did some cleanup on the gui this is good I am still confused why you both think frames needs a multiline. Since there seems to be a concensus on this tho i wont fight it
All informational sections i think should be grayed out (ReadOnly) i think it makes it clearer.
If jethrow voices no concerns on the new GUI layout i think ill change it as you presented it but set the other informational feilds to ReadOnly
_________________

We are troubled on every side‚ yet not distressed; we are perplexed‚
but not in despair; Persecuted‚ but not forsaken; cast down‚ but not destroyed;

[jethrow]

[tank]

[jethrow]

[sinkfaze]

I was annoyed with how I put together the last GUI so I re-wrote it so altering parts (if necessary) is much easier.

In accordance with jethrow's wishes, I also trimmed the width of the GUI and (in the interests of saving space) removed the width/height fields from the Viewer tab. I'm also testing a "rolled up" window feature I'd like you guys to check out. If you're on the Viewer tab, F1 will toggle the "rolled up" window state, but if you press Ctrl+e the window will automatically "roll down". The Script Writer and About tabs both default to the "rolled up" state. In addition, if you press Ctrl+e while the GUI is on any other tab, it should automatically activate and "roll down" the Viewer tab.

I've also modified how pause works in the GUI since there were previous instructions to pause the GUI before working in the Script Writer tab. The GUI should be toggled to paused automatically when in any tab other than the Viewer tab. I also created a subroutine that monitors the paused state when the Viewer tab is active, so if you navigate to another tab and go back to the Viewer tab, it should restore the Viewer tab's previous paused state.

Here's the link to check it out. Let me know what you think.

EDIT: I almost forgot, I also added additional identification techniques in the Ctrl+e hotkey to output sample code for iWeb_execScript() and iWeb_SelectOption() to the listbox where appropriate.
_________________
Try Quick Search for Autohotkey or see the tutorial for newbies.

[jethrow]

[sinkfaze]

[sinkfaze]

Just another thought tank, how come you haven't wrapped COM_Release(pwb) into an iWeb function? Just occurred to me that one little piece seems odd when writing code through the writer.
_________________
Try Quick Search for Autohotkey or see the tutorial for newbies.

[sinkfaze]

I have upgraded iWebBrowser2 Learner to build 2.3 for review. The major implementations in this release:

• "To Clipboard" checkboxes have been added to the viewer tab and the Script Writer tab. Checking the box on the Viewer tab will automatically save the selection from the ListBox to the Clipboard; checking the box on the Script Writer tab will automatically save the added selection from the dropdownlist to the Clipboard. Appending the selected item from either page to the bottom of the existing script is now the default.
  
• Double-clicking to select an item from the ListBox in the Viewer tab will automatically send you to the Script Writer tab.
  
• The script in the Script Writer must pass through five code filters before it can be executed:
  
  
  1. There must be an equal number of iWeb_Init() and iWeb_Term() statements,
     
  2. iWeb_Init() must come before iWeb_Term(),
     
  3. There must be an equal number of iWeb_getWin() and COM_Release() statements,
     
  4. Each iWeb_getWin() statement must be followed by a COM_Release() statement,
     
  5. All iWeb_getWin() and COM_Release() statements must be between an iWeb_Init() and an iWeb_Term() statement
     (only one iWeb_Init() and iWeb_Term() per script are currently supported).

• A beta version of individual form retrieval has been implemented for the Forms tab. When the 'Get Forms' button is pressed the source from the Source tab will be parsed, the name/id of each form will be sent to the dropdownlist and its corresponding form will appear in the Edit control when it is selected from the dropdown (the dropdownlist and the code box default to the first form).

_________________
Try Quick Search for Autohotkey or see the tutorial for newbies.

[tank]

I have uploaded the latest merges and have made some other minor changes as well
_________________

We are troubled on every side‚ yet not distressed; we are perplexed‚
but not in despair; Persecuted‚ but not forsaken; cast down‚ but not destroyed;

[jethrow]

[sinkfaze]

Is it possible 'Always on top' could be an optional mode?

And what is the bigger picture goal behind the message box that generates for each Form on the Forms tab? Is it just to show the "input" elements on the page? I just don't think an end user will be big on the persistence of those message boxes, particularly since the message boxes don't indicate what the significance of the contents are. Perhaps, as an alternative, we can trim down the size of the main Edit control for the code of each form and create another Edit control below it to output that data to?

I ultimately agree with making a lot of those fields read only but at the same time I wouldn't want to make the user feel like the information cannot (or should not) be copied. With that in mind, I added the "Left click/copy to Clipboard" functionality implmented by toralf in AHK Window Info 1.7 to my most current revision of the Learner for review. The same link I provided previously should work to download the revised version.
_________________
Try Quick Search for Autohotkey or see the tutorial for newbies.

[tank]