Its been a while.

The 2.0 feature I've been working on is one of the most interesting, but least likely to make it into Sesame. I am trying to write a small and relatively simple web server into Sesame. It allows you to contact the Sesame server, query records, and even post from your web browser.

Quote:


It doesn't really work that way. I never stop adding features. People other than me test and document while I work, usually a handful of features behind. When they decide that its ready to ship they grab that version.

Meanwhile the work I am doing goes into the next version.

If I had to stop working while there was release going on, things would get a lot less efficient. But then I would get some time off.

Also, I should point out - better and more web access is near the top of the wish lists coming in from customers.

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?

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.
-------------------------
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.
-------------------------------

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.

Thanks for listening Mark.

One of the advantages of forums and User Groups like SANE, and conference calling like Skype, is the opportunity to get input from others re what you are doing.  (Spencer, you need a name for the new Tampa users group).

After sending earlier message about need for @Delete, I talked myself into an easier and faster method. 

Not done yet, but will be tried soon:
When the DeleteRecord button is selected, I will just set a static variable.  When I close the Parent record I will check the status of the static variable and recals as needed if variable indicates a deletion.  And then will clear the static.  Just need to make sure I clear static variable if operator selects NO when prompted to really Delete?

This will eliminate the constant count of subrecords when opening and closing the Parent Form.  Only count will be needed at subrecord level after selecting the DeleteRecord button.

Thanks for listening, lots of good help here, great place for great ideas.

Mark -

Ray has been asking that we use the "support" link to submit suggestions:

Quote:


I thought, perhaps, that was so they could be tracked better or "whatever."

It's a lot easier to post suggestions here where the issues are being discussed.  Are you saying we can "forget about" using the support link to submit suggestions? Apparently that works for you; will it satisfy Ray also?

We do want to keep all of you happy when we can and want you to feel supported by us ... as much as we feel (and are, indeed) supported by you.  

Thanks

Mark -

So even though you say "suggestions are welcome here" it would probably behoove us (hope you're watching, Bob) to also "cut and paste" or whatever those that we care about, into the support request form using the support request link.

Is that a logical conclusion?

My nomination for Spencer's group:
F-ast                    A-sking            I-n
A-cting                 B-rainteasers    T-ampa
G-urus                  O-ver
H-oping            U-nproven
E-verything       D-esigns
D-evelops

Sorry, I couldn't help myself. All my programming went well today and I have a little extra time to ?

Hi Mark!

It is good to hear that a built in webserver is in the works. Can I ask why it is the least likely feature to make it into 2.0? Is this because of the amount of work or difficulty thereof ? Or is it a matter of priority?

Are you building the webserver from scratch or  trying to modify  something already out there to be apart of  Sesame?

Frederick