Re: connections with version 2.27
Posted: 24 Mar 2023, 10:41
Hello
Yes I tried but it does not work in JT_Message
In your case it's not the same it's GT which sends the frame to Log4OM me it's JTAlert ..
But I think I understand, I have to look a little more
In fact, in the JTDX Log window, we sometimes have the Gridlocator in 4 characters or in 6 characters, but if I look at the frame transmitted by JTAlert to Log4OM (because it is JTAlert that sends the frame to Log4OM) and of course it it is JTAlert which modifies the locator sent by JTDX by forcing it with 6 characters and therefore Log4OM only does well to copy what was sent to it
So the problem (for my case) is a JTAlert problem and not a Log4OM problem but I'm surprised no one else has seen this problem
So I'm going to look on the JTAlert side
THANKS
Yes I tried but it does not work in JT_Message
In your case it's not the same it's GT which sends the frame to Log4OM me it's JTAlert ..
But I think I understand, I have to look a little more
In fact, in the JTDX Log window, we sometimes have the Gridlocator in 4 characters or in 6 characters, but if I look at the frame transmitted by JTAlert to Log4OM (because it is JTAlert that sends the frame to Log4OM) and of course it it is JTAlert which modifies the locator sent by JTDX by forcing it with 6 characters and therefore Log4OM only does well to copy what was sent to it
So the problem (for my case) is a JTAlert problem and not a Log4OM problem but I'm surprised no one else has seen this problem
So I'm going to look on the JTAlert side
THANKS