Use this Forum to post your “How to …” questions about your use of aXes. This is not a technical support forum. Both the aXes Support Team at LANSA and other aXes customers may answer your questions. LANSA cannot guarantee the accuracy of any information posted by customers.
Moderator: jeanmichel
-
Fairdinkum
- Posts: 119
- Joined: 24 Jul 2017, 17:02
Post
by Fairdinkum » 20 Dec 2023, 21:06
That's weird.
Can you check if the class "ax_customeautoguifkey" is there in a container DIV like shown below.
- Image 023.png (216.28 KiB) Viewed 16759 times
Note: if top and height are removed, it appears like above. The container DIV height is bit larger than the button.
If it exists there, the CSS selector "div.ax_customeautoguifkey button" should work.
- Image 024.png (181.86 KiB) Viewed 16759 times
Regards,
Hide
-
Fre_Vdh
- Posts: 30
- Joined: 20 Oct 2022, 17:49
Post
by Fre_Vdh » 20 Dec 2023, 21:11
No it's not... we are using Material Design, I don't know if it has to do something with that?
- properties.png (104.58 KiB) Viewed 16757 times
-
Fairdinkum
- Posts: 119
- Joined: 24 Jul 2017, 17:02
Post
by Fairdinkum » 20 Dec 2023, 21:21
Oh I see, you used the fKey panel extension. That's the difference between you and myself. I will try using the fKey panel as well tomorrow. Or it will work once the fKey panel is removed, I presume.
Regards,
Hide
-
Fairdinkum
- Posts: 119
- Joined: 24 Jul 2017, 17:02
Post
by Fairdinkum » 21 Dec 2023, 10:24
If it's "normal" autoGui button, it has a class linked to DSPATR. In case as shown below, "x29" represents COLOR(RED) DSPATR(RI).
- Image 025.png (140.76 KiB) Viewed 16752 times
COLOR(RED) + DSPATR(RI)
- Image 027.png (10.01 KiB) Viewed 16752 times
On the other hand, fKeys in fKey panel don't have the information about DSPATR...
- Image 026.png (146.92 KiB) Viewed 16752 times
So I think there are two options.
1. use "normal" autoGui fKey button.
2. ask Lansa to enhance this portion.
Regards,
Hide
-
Fre_Vdh
- Posts: 30
- Joined: 20 Oct 2022, 17:49
Post
by Fre_Vdh » 21 Dec 2023, 17:08
Hi,
Thanks for investigating this, but the result is as we thought.
It's impossible to start changing all the screens that have been made so far, so I guess we'll have to wait on Lansa to make this.
Unless it's possible to change the fKeyPanels to "normal" autoGui buttons in one action?
Kind regards,
Frederik
-
Fairdinkum
- Posts: 119
- Joined: 24 Jul 2017, 17:02
Post
by Fairdinkum » 21 Dec 2023, 17:50
Hi,
Try unchecking "Show function keys on Panel.
- Image 033.png (26.5 KiB) Viewed 16748 times
Regards,
Hide
-
Fre_Vdh
- Posts: 30
- Joined: 20 Oct 2022, 17:49
Post
by Fre_Vdh » 21 Dec 2023, 18:05
The screens that haven't been edited yet now show the function keys on the screen itself, and in a function key panel (that's automatically added apparently).
On the existing screens I only see the function key panel.
-
Fairdinkum
- Posts: 119
- Joined: 24 Jul 2017, 17:02
Post
by Fairdinkum » 21 Dec 2023, 18:46
Found a solution.
- Image 035.png (135.14 KiB) Viewed 16745 times
-
Fre_Vdh
- Posts: 30
- Joined: 20 Oct 2022, 17:49
Post
by Fre_Vdh » 21 Dec 2023, 19:02
I would have to do that on every screen then...
But I'm giving it a try for this screen to see what happens, maybe something can be found so that it can be a bit automised.
The div around the button ("supp") now gets the ax_customeautoguifkey class, but the style is not taken over. If you look at the right box, you see that the css is also shown. I tried changing the 'inherit' to #F12345 and then all the buttons got a color.
- button.png (99.2 KiB) Viewed 16744 times