Skip to main content

Revise AcuToWeb execution on IOS to support W$MOUSE routines.   Associate finger taps to AcuCobol W$MOUSE coding.  Perhaps the following:

1-finger-tap held ==>   left-button-pushed

1-finger-quick-tap ==>   left-button-released

1-finger-2-quick-taps   ==>   left-button-double-clicked

1-finger-tap-held with 2nd-finger-double-tap ==>   right-button-double-clicked

and be able to determine the position with GET-MOUSE-STATUS (in pixels)

or another possibility using Push-Buttons to know what is being tapped is to have transparent Push-Buttons that don't actually display, (or that only show an outline with whatever image is behind it showing through). Then I could have a couple hundred of these push-buttons positioned where I might service the operator's tap to determined where they tapped.

I currently have a routine that displays a graphic, representing a layout of a marina, that the operator can double click to show the name of the boat & owner occupying the slip, the size of slip, and/or to assign the slip to a new boat.

Thanks

 

 

Revise AcuToWeb execution on IOS to support W$MOUSE routines.   Associate finger taps to AcuCobol W$MOUSE coding.  Perhaps the following:

1-finger-tap held ==>   left-button-pushed

1-finger-quick-tap ==>   left-button-released

1-finger-2-quick-taps   ==>   left-button-double-clicked

1-finger-tap-held with 2nd-finger-double-tap ==>   right-button-double-clicked

and be able to determine the position with GET-MOUSE-STATUS (in pixels)

or another possibility using Push-Buttons to know what is being tapped is to have transparent Push-Buttons that don't actually display, (or that only show an outline with whatever image is behind it showing through). Then I could have a couple hundred of these push-buttons positioned where I might service the operator's tap to determined where they tapped.

I currently have a routine that displays a graphic, representing a layout of a marina, that the operator can double click to show the name of the boat & owner occupying the slip, the size of slip, and/or to assign the slip to a new boat.

Thanks

 

 

Good morning,  

I am going to discuss your requests internally with our AcuToWeb Developers, and I'll let you know soon.

In the while, can you raise a Case on the Support Portal, so we can track your enhancement requests there?

Should you have troubles in logging.in, please follow this help.

Regards.

Revise AcuToWeb execution on IOS to support W$MOUSE routines.   Associate finger taps to AcuCobol W$MOUSE coding.  Perhaps the following:

1-finger-tap held ==>   left-button-pushed

1-finger-quick-tap ==>   left-button-released

1-finger-2-quick-taps   ==>   left-button-double-clicked

1-finger-tap-held with 2nd-finger-double-tap ==>   right-button-double-clicked

and be able to determine the position with GET-MOUSE-STATUS (in pixels)

or another possibility using Push-Buttons to know what is being tapped is to have transparent Push-Buttons that don't actually display, (or that only show an outline with whatever image is behind it showing through). Then I could have a couple hundred of these push-buttons positioned where I might service the operator's tap to determined where they tapped.

I currently have a routine that displays a graphic, representing a layout of a marina, that the operator can double click to show the name of the boat & owner occupying the slip, the size of slip, and/or to assign the slip to a new boat.

Thanks

 

 

 , what do you think of this: https://bit.ly/3svclhs

It works for me on Android, and it "almost" works on an IPad.
(it just needs a quick rectification of the position where the pop-up menu appears; something we can fix in a week)

How it works today: 
1-finger-quick-tap = left-button-pushed
1-finger-tap held = right-button-pushed = the popup menu is shown

This is a way to replicate the Push Buttons you'd like to have in your "marina" screen.
Unfortunately, a PB cannot be transparent, but you can apply a bitmap over it and simulate the graphic you'd like to have.

We are available for discussing this further.

Looking forward for your feedback.

Terms & ConditionsAccessibility statement