Quote:That sound like it will be quite useful Mark....thanks for looking out for us.
While you're at it, how about a MouseMove(x,y) and MouseMoveRelative(x,y) and a MouselClick(L/R/M) to allow moving mouse to screen position to click items that may not be available from the keyboard?
As far as I know, in runtime 1.1.3, the only elements not available from the keyboard is the window drag to resize, and main window max / min buttons. I suspect that these are actually available from the keyboard too (they are in Linux/X11), but I don't know the keystrokes to cause them. Commands to resize the main window (as per the buttons at the top right of the main window) have been implemented in 2.0. Also, macros can be used to click on any element in 1.1.3 and 2.0.
Quote:MouseMove(x,y) moves mouse to absoute pixel screen position
MouseMoveRelative(x,y) moves mouse to pixel position relative to Window top left corner to handle windows that are not at position 0,0.
MouseClick Left/Right/Middle button.
Could ask for more like MouseClick(Down/Up) to also allow for dragging, not to mention DoubleClick or MouseMove/Over but don't want to be too greedy right now.
Originally, before 1.0 - the macros used to play back showing mouse motion (actually pushed the mouse cursor around the screen). But it was decided that it was too slow and too obvious what the macro was doing. I'm not sure why people care if the end user knows what a macro is doing - but they did.
Can you be more specific as to what you are trying to do with this?
Quote:-------------------------
Also, a simple way for the Parent form to know that one or more child records have been deleted that might trigger the need for some recalculations. Right now I am adding code to count subrecords when parent form opens and again when closes, and compare for difference. But with many sub records, this becomes visible slow down. This could be some type of StatusFlag like @Add/@Modified .... @Deleted would be a new status flag.
-------------------------------
We've been looking into providing an "on delete" event to be added in like on form enter/exit.
Quote:I know, suggestions can be entered elsewhere, but since you are doing your own thing, I thought I would try to slip in a few idle thoughts. Things you could easily implement without major effort. It's always easy when someone else has to do it.
Suggestions are always welcome here. Both of the entries I made in this thread (the "simple web server" and the "parent form on change" features) are in reaction to forum/email posts. Sesame is definitely a collaborative effort (largely based on user suggestions) and no portion of it is me doing "my own thing".