Hello,
RTL issue in runtime.
PB 2019 Build 2170
Columns in DW that defined as RTL, in Runtime environment randomly works as defined.
Please Help
Regards,
Marina
Hello,
RTL issue in runtime.
PB 2019 Build 2170
Columns in DW that defined as RTL, in Runtime environment randomly works as defined.
Please Help
Regards,
Marina
Hi Marina.
Yes you have to deploy the pb.ini in the same folder where you executable is located.
This pb.ini needs to contain only those specific params that you exe needs to work as you want.
Andreas.
Should I deploy PB.ini?
If yes, what does this mean?
On my computer in Runtime environment - all the problematic columns that the users complain about, works fine...
I added to PB.ini
this option, that we had in previous PB12.5 version:
[Data Window]
useDefaultKeyboardLayout=yes
It solved the RTL issue in some DWs , but not in all.
The columns are columns from the select behind the DW. Text , Style - Edit, RTL columns.
In previous PB12.5 version Runtime it worked perfect.
Regards,
Marina
Hi Marina;
Do you mean Rich Text Edit style on a column ... RTE?
Regards ... Chris
Please open a support ticket and provide test case so Appeon engineers can reproduce your issue. Thanks.
Anyway, I believe that this is a point where documentation needs to be improved.
Last try..
Usually all the users have 2 language defined in each computer - English (default) and Hebrew
DefaultKeyboardLayout is English
In PB.ini I added:
[Data Window]
ForgetColumnKeyboardLayout=yes
useDefaultKeyboardLayout=yes
And it solved the problem but not in 100%
There are still a couple of users that face the same problem
What is missing?
The problem is :
When you open some window with dw (with select behind it), the focus goes to specific column for example WITHOUT Right-to-left defined - start to write in it - should write in English, press Tab or click with the mouse on another column WITH Right-to-left defined - start to write in it - should write in Hebrew and so on...
In PB12.5 it works fine.
Regards,
Marina
Sounds like opening a Support Ticket with a simple test case PB App for this issue might be the next step. I would suggest supplying the test case in PB 12.5 and then Appeon Support can migrate the code through 12.6, 2017Rx and then 2019Rx to see where it might be breaking.
Regards ... Chris