Hi, Heidi,

 

My employer has gratiously given his OK for sharing this snippet, which enables turning on and off a keyboard message filter that replaces keyboard ENTER by TAB. It is best to add this code to a program containing an inputparameter ‘PI_ACTIVE’ (logical), and to call the invoked .Net code using a function name ‘SetEnterTabActive’ (instead of the generic ‘func’), and to pass along the inputparameter ‘PI_ACTIVE’ as the DotNet argument ‘active’. When called with a true value, a keyboard message filter is applied to the whole Magic Runtime. When called with a false value, the keyboard message filter is removed again. However you have used it in runtime, I recommend you still disable the message filter in development when returning from runtime: i.e. you’d best call the code with a false value from the Task Suffix of the Main Program; if for any reason the filter is not deactivated when returning from runtime to development, it is possible that a subsequent run of the same project will still have the message filter active, without any way of disabling it during runtime.

 

using System;

using F = System.Windows.Forms;

 

public static class Snippet

{

      public static void SetEnterTabActive(System.Boolean active)

      {

            F.Application.RemoveMessageFilter(ETMF);

            if (active) {

                  F.Application.AddMessageFilter(ETMF);

            }

      }

      static EnterTabMessageFilter ETMF = new EnterTabMessageFilter();

      public class EnterTabMessageFilter : F.IMessageFilter {

            public bool PreFilterMessage(ref F.Message m) {

                  if (m.Msg == 0x0100) {

                        /* KEY DOWN */

                        if ((m.LParam.ToInt32() & 0x01000000) != 0) {

                             /* NUMERIC KEY PAD */

                             if (m.WParam.ToInt32() == (int)F.Keys.Enter) {

                                   /* ENTER KEY */

                                   F.SendKeys.Send("{TAB}");

                                   return true;

                             }

                        }            

                  }

                  return false;

            }

    }

}

 

This code does not come with a warranty. I do recommend testing the code for your use cases, and if necessary, change it to suit your needs. The code I supplied has not really been vetted by anyone else but me. But I do hope it works for you.

 

Bye,

 

Frederik Soete

 

 

Op 17 jun. 2017 20:08 schreef "Heidi Schuppenhauer" <heidis13@...>:

Thanks Frederik.

My research said about the same: it CAN be done in .Net but it's in fact rather hairy! And given that I couldn't even figure out the task bar I have a ways to go with .Net! If you do get permission to publish it, it will help a lot of people!

I'm kind of wondering though if it should be handled at the Magic level. There is already a keyboard translation table. The only issue with it is that it does not differentiate between the normal Enter key and the numeric Enter key. But they likely have two different codes when they are accepted by Magic?

Heidi.Schuppenhauer

xpathinktank.blogspot.com

 

On Sat, Jun 17, 2017 at 7:20 AM, Frederik Soete <frederik.soete@...> wrote:

Hi, Heidi,

In the place I am employed, we are currently looking into transferring from eDeveloper v.9 to XPA, and I have researched some alternatives to get.dll functionality. Some things, like colour buttons have a straightforward XPA translation: XPA supports colour buttons in itself, so it is a no-brainer. But this one function, changing the ENTER key to TAB, is possible, I have found, but only with some very *hairy* Dot Net code, which I cannot access at the present, for I am on holiday for a week. I would still have to ask my employer for permission to share the intricate snippet. I may perhaps deliver the code, but I am sorry I cannot make any promises. I can still refer my employer to the fact we frequently used get.dll which was also "donated to the Magic community". For now I can only state it definitely IS possible.

Now for the method I followed, and the few details I remember without access to the code and the correct terminology. As I recall, it is possible to intercept some keypresses via Dot Net and substitute another keycode for these. At the time of coding I found different sites via google, which when creatively combined led to the complete solution. The solution needed an on/off switch, to be toggled whenever during runtime, and to be turned off at logging off (needed for the development environment). The on/off switch was implemented as a 'static' variable. The 'keypress code' added some event listener (only on first execution) which intercepted the ENTER key, and turned ENTER into TAB but only when the switch was activated. The only drawback is in development you have to remember to switch it off in Main Program Task suffix so as not to let it interfere with the next execution of the runtime, when a new event listener is registered. (I did not figure out how to unregister such an event listener, so the on/off switch is a good substitute.)

Bye.

Frederik Soete

What are you trying to achieve? You can also use Outer Join instead of Inner Join.

 

Van: main@magicu-l.groups.io [mailto:main@....io] Namens Lado Wali
Verzonden: woensdag 21 juni 2017 22:56
Aan: main@magicu-l.groups.io
Onderwerp: [magicu-l] SQL Range with Inner Join - uniPaaS 1.9

 

Hi Group,

 

I want to do sql range on one of my online program with the help of Link Inner Join but with condition. Is there any way I can use Link Inner Join with condition?

 

Thanks

Lado

 

Met vriendelijke groet - With kind regards, Florian Groothuis Analist/programmeur +31 (0)6 21927914

meilink.eu Meilink Beheer Borculo B.V. • Kamerlingh Onnesstraat 1 7271 AZ  Borculo • Nederland • +31 (0)545 253525 KvK 08009803 • Our general terms and conditions apply • Disclaimer