Skip to main content

"field gets focus" and mouse click

  • January 21, 2019
  • 5 replies
  • 1 view

Branislav Barnak
Forum|alt.badge.img

FGF is NOT fired when user mouse-clicks to unifield.

Is it just an asn/ini settings problem or Uniface bug ?


note: FGF works fine when user cycles the form fields using keyboard.


5 replies

  • Rocketeer
  • January 22, 2019

FGF is NOT fired when user mouse-clicks to unifield.

Is it just an asn/ini settings problem or Uniface bug ?


note: FGF works fine when user cycles the form fields using keyboard.


What exact Unfiace version and patch level are you using?

There was a problem in Uniface 9.6 that started with the version 9.6.05 patch X503 and was fixed with the version 9.6.06 patch X604:

Issue 30842 - X503 and up: Mouse click not responding after clicking on unifield

Hope this helps.

Kind regards,

Daniel Iseli
Uniface Support


Branislav Barnak
Forum|alt.badge.img
  • Author
  • Participating Frequently
  • January 24, 2019

FGF is NOT fired when user mouse-clicks to unifield.

Is it just an asn/ini settings problem or Uniface bug ?


note: FGF works fine when user cycles the form fields using keyboard.


Hi Daniel


We use Uniface 9.7.04 G420, but it was not working even with the previous Uniface version 9.6.07 x704.

App is running via Citrix on Windows server 2016, build 1607.

Any ideas what else could be wrong ?


Thank you

Branislav




  • January 25, 2019

Hi Daniel


We use Uniface 9.7.04 G420, but it was not working even with the previous Uniface version 9.6.07 x704.

App is running via Citrix on Windows server 2016, build 1607.

Any ideas what else could be wrong ?


Thank you

Branislav



I did a quick test here with 9.7.04 + G420 on one of our Windows Server 2016 and (so far) I could not see a problem. The FGF is correctly fired in the described scenario (as far as I can see). And in general, we are not aware of any issues that are currently open in this area.

Have you already tested on the native console of the machine (i.e. without Citrix)? And there might be some additional factors that come into play here. Either try to strip down (one of) the form(s) where you can replicate the issue. Or start building a test form from scratch and add things until the problem starts to happen.

Daniel


Branislav Barnak
Forum|alt.badge.img
  • Author
  • Participating Frequently
  • January 28, 2019

Hi Daniel


We use Uniface 9.7.04 G420, but it was not working even with the previous Uniface version 9.6.07 x704.

App is running via Citrix on Windows server 2016, build 1607.

Any ideas what else could be wrong ?


Thank you

Branislav



I did the test on my local windows 10 machine and I have to say I was partially wrong.

The FGF is fired when the cursor is placed to unifield using left mouse click, but there is another issue:

There is a single message statement in FGF which should display message in the message line at the bottom of the startup shell, and when I click to unifield, FGF is fired but the message is not visible in message line. If I click to message line, then I can see the message at the end of message line.

It seems that the message line is just not refreshed properly, and it shows the "2018 Uniface B.V...." copyright statement always on mouse click.


Bellow you can find simple demo form.

https://1drv.ms/u/s!Alao0Q9lZujfiP81F51MRV6bBn0vyw


Best regards

Branislav




  • Rocketeer
  • February 6, 2019

Hi Daniel


We use Uniface 9.7.04 G420, but it was not working even with the previous Uniface version 9.6.07 x704.

App is running via Citrix on Windows server 2016, build 1607.

Any ideas what else could be wrong ?


Thank you

Branislav



Thanks for the info.

I had a quick look and I can see the described behavior here as well. It seems that this is actually a side-effect of the bug fix I've mentioned (Issue 30842), meaning I can see the problem starting with the patch X604.

I can force the message to appear in the message line when I use postmessage (to send a message to the current instance) in the FGF of the unifield and then execute the message statement in the Asynchronous Interrupt trigger of the component. It's not really ideal (to say the least) and it seems that the message line is now updated twice: first it'll show the copyright message and then the message from the Asynch.

Could you please log a new support call for this, in case you need a fix for this? That way it'll easier to trace the issue.

Thanks,

Daniel