Tab doesnt work in tuniFrame since update to 1.90.0.1531

[erich.wanker]

hi,

i updated to 1.90.0.1531.. now the "next field with tab key" is just working in my TuniForm ..  but doesnt work in my TuniFrame ..

it worked in the past .. i ordered all edit-cpmpunents with "TabOrder" value 

... the "special" thing is ... it works NOT if the uniframe has a runtime-created parent "unitabSheet"  -> a Sheet of designtime-created uniPageControl  (the same technoloy as used in the "onlen desktop demo" on http://www.unigui.com/ )

 

hope - someone has a idea what the reason could be

 

thanx

erich

[picyka]

I think that in uniframe it never worked, when it reaches the last field of the tab, it does not change to another tab, but to another field.

[Farshad Mohajeri]

48 minutes ago, erich.wanker said:

hi,

i updated to 1.90.0.1531.. now the "next field with tab key" is just working in my TuniForm ..  but doesnt work in my TuniFrame ..

it worked in the past .. i ordered all edit-cpmpunents with "TabOrder" value 

... the "special" thing is ... it works NOT if the uniframe has a runtime-created parent "unitabSheet"  -> a Sheet of designtime-created uniPageControl  (the same technoloy as used in the "onlen desktop demo" on http://www.unigui.com/ )

 

hope - someone has a idea what the reason could be

 

thanx

erich

Hi,

Are you sure it is related to 1531?

[Farshad Mohajeri]

Can you please send a test case?

[erich.wanker]

Hi Farshad

.. the same uniGui Application on a customer server - what is compiled with  uni-1.90.0.1523 and ext-6.7.0 is working fine

..since i updated my version to extjs 7 and uni-1.90.0.1531- the tabulator does not work anymore  ..

 

I tried to make a test-case BUT can not reproduce the issue ..??? i copyied the hole form in a new Unigui App - and the TAB is working  .. the only thing i didnt inklude in this test-case is the database function ... i will try to reproduce the issue ..  please give me more time for this ;-)

 

Nice greetings and stay healthy  

Erich

[erich.wanker]

ok .. i think i found a thing ... the only different between a working and a not working version is the id ... the rest of sourcecode in Chrome-Developer-View is completly the same 

 

 

[erich.wanker]

ok .. i think i found a thing ... the only different between a working and a not working version is the id ... the rest of sourcecode in Chrome-Developer-View is completly the same 

 

[Farshad Mohajeri]

In ServerModule

Options->soControlNameAsId

Is it True or False?

[erich.wanker]

Hi Farhad - it was "true"

.. i set it to false - compiled the project AND THE TAB IS WORKING :-)

Thank you very much !!!!!!!!!!!

 

ThanX ..

Erich