Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration

FlexCoders mailing list
Hi FlexCoders,
Has any one done migration from Flex 3 to 4, If so could you please share your experience where as I need to know what things need to be taken care of during migration and where to start? 
Regards--Sachin 
 <a href="http://messenger.yahoo.com/edit/send/?.target=hey_sachin">
<img border="0" src="http://opi.yahoo.com/yahooonline/u=hey_sachin/m=g/t=9/l=us/opi.jpg">
</a>
Reply | Threaded
Open this post in threaded view
|

Re: Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration

FlexCoders mailing list
Hi Sachin,

Transition from 3.6 to 4.6  is not very complex nor its too easy what I mean to say is that there are somethings that you need to consider while you are moving to higher end versions of Flex SDK.

1. Flex 4 supports a spark skinning architecture which may sound complex for anyone new to it , if you are largely depending upon css based development/tweaking of your custom or native flex components then you it may not help you alot though you can use css also but there are some components in flex where css rules may not apply like Group/VGroup/HGroup as in skinning where you have the full liberty to change the full UI of the built-in components under Adobe's terms and conditions at the same time you may find it quite complex in maintaining your skins if you have no prior knowledge of skinning so I should recommend you that you should get some knowledge on it first.

You might need to change or configure your themes accordingly like Halo , Spark etc etc.

2.Regarding your service layer things may remain the same as they are currently with your current SDK version you may have to change one or two things but nothing very much is required at this end.

3. Data model will also not get much effected in transition but you will need to be careful while using advance data components of Flex like Advanced Data Grid OLAP datagrid.

4. Good support with backward compatibility and earlier versions of flex. Flex 4 supports full backward compatibility of your components you may only need to change the Application tag of your project according new Flex 4 based and rest is good to go.

5. Localization- this would almost remain same no special things required.

Note: These were a few things that I considered or encountered in my experience while I was taking my product to higher level SDK in flex but these are not all the things you may need to do some more Google on it. As these are some things that are normally considered on first priority in transition phase but remember they are not the all.

You can further read these 2 very informative and good articles

http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html

http://www.adobe.com/devnet/flex/articles/migrating-flex-apps-part1.html

Regards.
--------------------------------------------
On Thu, 11/27/14, sachin sharma [hidden email] [flexcoders] <[hidden email]> wrote:

 Subject: [flexcoders] Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration
 To: "[hidden email]" <[hidden email]>
 Date: Thursday, November 27, 2014, 7:35 PM
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
 
 
 
   
 
 
     
       
       
       Hi
 FlexCoders,
 Has any
 one done migration from Flex 3 to 4, If so could you please
 share your experience where as I need to know what things
 need to be taken care of during migration and where to
 start? 
 Regards--Sachin 
  <a
 href="http://messenger.yahoo.com/edit/send/?.target=hey_sachin">
 <img border="0"
 src="http://opi.yahoo.com/yahooonline/u=hey_sachin/m=g/t=9/l=us/opi.jpg">
 </a>
 
     
     
 
     
     
 
 
 
 
 
 
   
 
 
 
 
 
 
 
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration

FlexCoders mailing list
Thanks anas naeem, It is really a very helpful information for me.
Regards--Sachin <a href="http://messenger.yahoo.com/edit/send/?.target=hey_sachin">
<img border="0" src="http://opi.yahoo.com/yahooonline/u=hey_sachin/m=g/t=9/l=us/opi.jpg">
</a>

     On Friday, 28 November 2014 7:16 AM, "anas naeem [hidden email] [flexcoders]" <[hidden email]> wrote:
   

     Hi Sachin,

Transition from 3.6 to 4.6 is not very complex nor its too easy what I mean to say is that there are somethings that you need to consider while you are moving to higher end versions of Flex SDK.

1. Flex 4 supports a spark skinning architecture which may sound complex for anyone new to it , if you are largely depending upon css based development/tweaking of your custom or native flex components then you it may not help you alot though you can use css also but there are some components in flex where css rules may not apply like Group/VGroup/HGroup as in skinning where you have the full liberty to change the full UI of the built-in components under Adobe's terms and conditions at the same time you may find it quite complex in maintaining your skins if you have no prior knowledge of skinning so I should recommend you that you should get some knowledge on it first.

You might need to change or configure your themes accordingly like Halo , Spark etc etc.

2.Regarding your service layer things may remain the same as they are currently with your current SDK version you may have to change one or two things but nothing very much is required at this end.

3. Data model will also not get much effected in transition but you will need to be careful while using advance data components of Flex like Advanced Data Grid OLAP datagrid.

4. Good support with backward compatibility and earlier versions of flex. Flex 4 supports full backward compatibility of your components you may only need to change the Application tag of your project according new Flex 4 based and rest is good to go.

5. Localization- this would almost remain same no special things required.

Note: These were a few things that I considered or encountered in my experience while I was taking my product to higher level SDK in flex but these are not all the things you may need to do some more Google on it. As these are some things that are normally considered on first priority in transition phase but remember they are not the all.

You can further read these 2 very informative and good articles

http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html

http://www.adobe.com/devnet/flex/articles/migrating-flex-apps-part1.html

Regards.
--------------------------------------------
On Thu, 11/27/14, sachin sharma [hidden email] [flexcoders] <[hidden email]> wrote:

Subject: [flexcoders] Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration
 To: "[hidden email]" <[hidden email]>
 Date: Thursday, November 27, 2014, 7:35 PM
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
 
 
 
 
 
 
 
 
 
 Hi
 FlexCoders,
 Has any
 one done migration from Flex 3 to 4, If so could you please
 share your experience where as I need to know what things
 need to be taken care of during migration and where to
 start? 
 Regards--Sachin 
  <a
 href="http://messenger.yahoo.com/edit/send/?.target=hey_sachin">
 <img border="0"
 src="http://opi.yahoo.com/yahooonline/u=hey_sachin/m=g/t=9/l=us/opi.jpg">
 </a>
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  #yiv2721068956 #yiv2721068956 -- #yiv2721068956ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv2721068956 #yiv2721068956ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv2721068956 #yiv2721068956ygrp-mkp #yiv2721068956hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv2721068956 #yiv2721068956ygrp-mkp #yiv2721068956ads {margin-bottom:10px;}#yiv2721068956 #yiv2721068956ygrp-mkp .yiv2721068956ad {padding:0 0;}#yiv2721068956 #yiv2721068956ygrp-mkp .yiv2721068956ad p {margin:0;}#yiv2721068956 #yiv2721068956ygrp-mkp .yiv2721068956ad a {color:#0000ff;text-decoration:none;}#yiv2721068956 #yiv2721068956ygrp-sponsor #yiv2721068956ygrp-lc {font-family:Arial;}#yiv2721068956 #yiv2721068956ygrp-sponsor #yiv2721068956ygrp-lc #yiv2721068956hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv2721068956 #yiv2721068956ygrp-sponsor #yiv2721068956ygrp-lc .yiv2721068956ad {margin-bottom:10px;padding:0 0;}#yiv2721068956 #yiv2721068956actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv2721068956 #yiv2721068956activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv2721068956 #yiv2721068956activity span {font-weight:700;}#yiv2721068956 #yiv2721068956activity span:first-child {text-transform:uppercase;}#yiv2721068956 #yiv2721068956activity span a {color:#5085b6;text-decoration:none;}#yiv2721068956 #yiv2721068956activity span span {color:#ff7900;}#yiv2721068956 #yiv2721068956activity span .yiv2721068956underline {text-decoration:underline;}#yiv2721068956 .yiv2721068956attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv2721068956 .yiv2721068956attach div a {text-decoration:none;}#yiv2721068956 .yiv2721068956attach img {border:none;padding-right:5px;}#yiv2721068956 .yiv2721068956attach label {display:block;margin-bottom:5px;}#yiv2721068956 .yiv2721068956attach label a {text-decoration:none;}#yiv2721068956 blockquote {margin:0 0 0 4px;}#yiv2721068956 .yiv2721068956bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv2721068956 .yiv2721068956bold a {text-decoration:none;}#yiv2721068956 dd.yiv2721068956last p a {font-family:Verdana;font-weight:700;}#yiv2721068956 dd.yiv2721068956last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv2721068956 dd.yiv2721068956last p span.yiv2721068956yshortcuts {margin-right:0;}#yiv2721068956 div.yiv2721068956attach-table div div a {text-decoration:none;}#yiv2721068956 div.yiv2721068956attach-table {width:400px;}#yiv2721068956 div.yiv2721068956file-title a, #yiv2721068956 div.yiv2721068956file-title a:active, #yiv2721068956 div.yiv2721068956file-title a:hover, #yiv2721068956 div.yiv2721068956file-title a:visited {text-decoration:none;}#yiv2721068956 div.yiv2721068956photo-title a, #yiv2721068956 div.yiv2721068956photo-title a:active, #yiv2721068956 div.yiv2721068956photo-title a:hover, #yiv2721068956 div.yiv2721068956photo-title a:visited {text-decoration:none;}#yiv2721068956 div#yiv2721068956ygrp-mlmsg #yiv2721068956ygrp-msg p a span.yiv2721068956yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv2721068956 .yiv2721068956green {color:#628c2a;}#yiv2721068956 .yiv2721068956MsoNormal {margin:0 0 0 0;}#yiv2721068956 o {font-size:0;}#yiv2721068956 #yiv2721068956photos div {float:left;width:72px;}#yiv2721068956 #yiv2721068956photos div div {border:1px solid #666666;height:62px;overflow:hidden;width:62px;}#yiv2721068956 #yiv2721068956photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv2721068956 #yiv2721068956reco-category {font-size:77%;}#yiv2721068956 #yiv2721068956reco-desc {font-size:77%;}#yiv2721068956 .yiv2721068956replbq {margin:4px;}#yiv2721068956 #yiv2721068956ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv2721068956 #yiv2721068956ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv2721068956 #yiv2721068956ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv2721068956 #yiv2721068956ygrp-mlmsg select, #yiv2721068956 input, #yiv2721068956 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv2721068956 #yiv2721068956ygrp-mlmsg pre, #yiv2721068956 code {font:115% monospace;}#yiv2721068956 #yiv2721068956ygrp-mlmsg * {line-height:1.22em;}#yiv2721068956 #yiv2721068956ygrp-mlmsg #yiv2721068956logo {padding-bottom:10px;}#yiv2721068956 #yiv2721068956ygrp-msg p a {font-family:Verdana;}#yiv2721068956 #yiv2721068956ygrp-msg p#yiv2721068956attach-count span {color:#1E66AE;font-weight:700;}#yiv2721068956 #yiv2721068956ygrp-reco #yiv2721068956reco-head {color:#ff7900;font-weight:700;}#yiv2721068956 #yiv2721068956ygrp-reco {margin-bottom:20px;padding:0px;}#yiv2721068956 #yiv2721068956ygrp-sponsor #yiv2721068956ov li a {font-size:130%;text-decoration:none;}#yiv2721068956 #yiv2721068956ygrp-sponsor #yiv2721068956ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv2721068956 #yiv2721068956ygrp-sponsor #yiv2721068956ov ul {margin:0;padding:0 0 0 8px;}#yiv2721068956 #yiv2721068956ygrp-text {font-family:Georgia;}#yiv2721068956 #yiv2721068956ygrp-text p {margin:0 0 1em 0;}#yiv2721068956 #yiv2721068956ygrp-text tt {font-size:120%;}#yiv2721068956 #yiv2721068956ygrp-vital ul li:last-child {border-right:none !important;}#yiv2721068956

   
Reply | Threaded
Open this post in threaded view
|

Re: Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration

FlexCoders mailing list
In reply to this post by FlexCoders mailing list
Hi Guys,

After converting application to sdk 4.6 and compiled the flex application and got this errors, could u please provide solution for this. I searched on google but no luck. It would be great help if you can point me to right direction

VerifyError: Error #1014: Class IDeferredInstantiationUIComponent could not be found.

 

VerifyError: Error #1014: Class mx.flash::UIMovieClip could not be found.

Regards
Sachin

Sent from Yahoo Mail on Android

Reply | Threaded
Open this post in threaded view
|

Re: Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration

FlexCoders mailing list
In reply to this post by FlexCoders mailing list
 

Hi Sachin

What appears to be the sole cause of this error is your versions not matching up between your Flex/AIR SDK and the AIR application descriptor file. This can happen after you update/reinstall Flash Builder, or the SDK folder manually.

Just open your AIR descriptor file(generally the only XML file in the project src folder) and change the xmlns to the current version of the SDK you are using(1.5.3 => 2.0 for instance). 

and one more reason for this type of issue is that i guess some of your external dependencies like swc file are not matching with current flex sdk version

let me know if this works for you...

A

On Dec 5, 2014 6:40 AM, "sachin sharma [hidden email] [flexcoders]" <[hidden email]> wrote:
 

Hi Guys,

After converting application to sdk 4.6 and compiled the flex application and got this errors, could u please provide solution for this. I searched on google but no luck. It would be great help if you can point me to right direction

VerifyError: Error #1014: Class IDeferredInstantiationUIComponent could not be found.

 

VerifyError: Error #1014: Class mx.flash::UIMovieClip could not be found.

Regards
Sachin

Sent from Yahoo Mail on Android

From:"anas naeem maverick_0601@yahoo.com [flexcoders]" <flexcoders@yahoogroups.com>
Date:Fri, Nov 28, 2014 at 7:16 AM
Subject:Re: [flexcoders] Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration

 

Hi Sachin,

Transition from 3.6 to 4.6 is not very complex nor its too easy what I mean to say is that there are somethings that you need to consider while you are moving to higher end versions of Flex SDK.

1. Flex 4 supports a spark skinning architecture which may sound complex for anyone new to it , if you are largely depending upon css based development/tweaking of your custom or native flex components then you it may not help you alot though you can use css also but there are some components in flex where css rules may not apply like Group/VGroup/HGroup as in skinning where you have the full liberty to change the full UI of the built-in components under Adobe's terms and conditions at the same time you may find it quite complex in maintaining your skins if you have no prior knowledge of skinning so I should recommend you that you should get some knowledge on it first.

You might need to change or configure your themes accordingly like Halo , Spark etc etc.

2.Regarding your service layer things may remain the same as they are currently with your current SDK version you may have to change one or two things but nothing very much is required at this end.

3. Data model will also not get much effected in transition but you will need to be careful while using advance data components of Flex like Advanced Data Grid OLAP datagrid.

4. Good support with backward compatibility and earlier versions of flex. Flex 4 supports full backward compatibility of your components you may only need to change the Application tag of your project according new Flex 4 based and rest is good to go.

5. Localization- this would almost remain same no special things required.

Note: These were a few things that I considered or encountered in my experience while I was taking my product to higher level SDK in flex but these are not all the things you may need to do some more Google on it. As these are some things that are normally considered on first priority in transition phase but remember they are not the all.

You can further read these 2 very informative and good articles

http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html

http://www.adobe.com/devnet/flex/articles/migrating-flex-apps-part1.html

Regards.
--------------------------------------------
On Thu, 11/27/14, sachin sharma hey_sachin@yahoo.com [flexcoders] <flexcoders@yahoogroups.com> wrote:

Subject: [flexcoders] Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration
To: "flexcoders@yahoogroups.com" <flexcoders@yahoogroups.com>
Date: Thursday, November 27, 2014, 7:35 PM
















 









Hi
FlexCoders,
Has any
one done migration from Flex 3 to 4, If so could you please
share your experience where as I need to know what things
need to be taken care of during migration and where to
start? 
Regards--Sachin 
 <a
href="http://messenger.yahoo.com/edit/send/?.target=hey_sachin">
<img border="0"
src="http://opi.yahoo.com/yahooonline/u=hey_sachin/m=g/t=9/l=us/opi.jpg">
</a>






















__._,_.___

Posted by: Anas <[hidden email]>
Reply via web post [hidden email] [hidden email] Start a New Topic Messages in this topic (5)

.

__,_._,___
Reply | Threaded
Open this post in threaded view
|

Re: Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration

FlexCoders mailing list
Hi Anas,

Thanks for advise, I have migrated application successfully to 4.6, it is working fine now. Now looking at performance issues as it is not working fine in IE8.0, all other broswers are fine with this.

Regards
--sachin

Sent from Yahoo Mail on Android

Reply | Threaded
Open this post in threaded view
|

Re: Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration

FlexCoders mailing list
In reply to this post by FlexCoders mailing list
 

Sachin glad to hear that you have successfully migrated it now for the performance issues could you pls tell me that what type of performance issues you are encountering in IE i mean does the loading time is more as compared to other browsers or anything else?

-A

On Dec 14, 2014 8:15 AM, "sachin sharma [hidden email] [flexcoders]" <[hidden email]> wrote:
 

Hi Anas,

Thanks for advise, I have migrated application successfully to 4.6, it is working fine now. Now looking at performance issues as it is not working fine in IE8.0, all other broswers are fine with this.

Regards
--sachin

Sent from Yahoo Mail on Android

From:"Anas maverick_0601@yahoo.com [flexcoders]" <flexcoders@yahoogroups.com>
Date:Mon, Dec 8, 2014 at 8:54 PM
Subject:Re: [flexcoders] Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration

 

Hi Sachin

What appears to be the sole cause of this error is your versions not matching up between your Flex/AIR SDK and the AIR application descriptor file. This can happen after you update/reinstall Flash Builder, or the SDK folder manually.

Just open your AIR descriptor file(generally the only XML file in the project src folder) and change the xmlns to the current version of the SDK you are using(1.5.3 => 2.0 for instance). 

and one more reason for this type of issue is that i guess some of your external dependencies like swc file are not matching with current flex sdk version

let me know if this works for you...

A

On Dec 5, 2014 6:40 AM, "sachin sharma hey_sachin@yahoo.com [flexcoders]" <flexcoders@yahoogroups.com> wrote:
 

Hi Guys,

After converting application to sdk 4.6 and compiled the flex application and got this errors, could u please provide solution for this. I searched on google but no luck. It would be great help if you can point me to right direction

VerifyError: Error #1014: Class IDeferredInstantiationUIComponent could not be found.

 

VerifyError: Error #1014: Class mx.flash::UIMovieClip could not be found.

Regards
Sachin

Sent from Yahoo Mail on Android

From:"anas naeem maverick_0601@yahoo.com [flexcoders]" <flexcoders@yahoogroups.com>
Date:Fri, Nov 28, 2014 at 7:16 AM
Subject:Re: [flexcoders] Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration

 

Hi Sachin,

Transition from 3.6 to 4.6 is not very complex nor its too easy what I mean to say is that there are somethings that you need to consider while you are moving to higher end versions of Flex SDK.

1. Flex 4 supports a spark skinning architecture which may sound complex for anyone new to it , if you are largely depending upon css based development/tweaking of your custom or native flex components then you it may not help you alot though you can use css also but there are some components in flex where css rules may not apply like Group/VGroup/HGroup as in skinning where you have the full liberty to change the full UI of the built-in components under Adobe's terms and conditions at the same time you may find it quite complex in maintaining your skins if you have no prior knowledge of skinning so I should recommend you that you should get some knowledge on it first.

You might need to change or configure your themes accordingly like Halo , Spark etc etc.

2.Regarding your service layer things may remain the same as they are currently with your current SDK version you may have to change one or two things but nothing very much is required at this end.

3. Data model will also not get much effected in transition but you will need to be careful while using advance data components of Flex like Advanced Data Grid OLAP datagrid.

4. Good support with backward compatibility and earlier versions of flex. Flex 4 supports full backward compatibility of your components you may only need to change the Application tag of your project according new Flex 4 based and rest is good to go.

5. Localization- this would almost remain same no special things required.

Note: These were a few things that I considered or encountered in my experience while I was taking my product to higher level SDK in flex but these are not all the things you may need to do some more Google on it. As these are some things that are normally considered on first priority in transition phase but remember they are not the all.

You can further read these 2 very informative and good articles

http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html

http://www.adobe.com/devnet/flex/articles/migrating-flex-apps-part1.html

Regards.
--------------------------------------------
On Thu, 11/27/14, sachin sharma hey_sachin@yahoo.com [flexcoders] <flexcoders@yahoogroups.com> wrote:

Subject: [flexcoders] Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration
To: "flexcoders@yahoogroups.com" <flexcoders@yahoogroups.com>
Date: Thursday, November 27, 2014, 7:35 PM
















 









Hi
FlexCoders,
Has any
one done migration from Flex 3 to 4, If so could you please
share your experience where as I need to know what things
need to be taken care of during migration and where to
start? 
Regards--Sachin 
 <a
href="http://messenger.yahoo.com/edit/send/?.target=hey_sachin">
<img border="0"
src="http://opi.yahoo.com/yahooonline/u=hey_sachin/m=g/t=9/l=us/opi.jpg">
</a>






















__._,_.___

Posted by: Anas <[hidden email]>
Reply via web post [hidden email] [hidden email] Start a New Topic Messages in this topic (7)

.

__,_._,___
Reply | Threaded
Open this post in threaded view
|

Re: Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration

FlexCoders mailing list
Hi Anas, Now in application autocomplete combo box displaying text from right to left, if I type some text to search like ABC it shows like CBA, As I changed setSelection to selectRange , and anchor position as per flex 4 upgrade. But auto complete combobox is not working properly, Please help if you have experienced the same.

-/Sachin

Sent from Yahoo Mail on Android

Reply | Threaded
Open this post in threaded view
|

Re: Flex 3 (SDK3.6) to Flex 4 (SDK 4.6) Migration

FlexCoders mailing list
Hi Guys,

 I am facing issue with auto complete feature where I have replaced  textInput.setSelection with textInput.selectRange and textInput.selectionBeginIndex with textInput.selectionAnchorPosition as per flex upgrade standard but it started strange behavior for combobox in application. At runtime when I type text leike "ABC" into combobox it always move cursor in the leftmost position and type in reverse order like "CBA".
 

 Please provide some help if anyone experienced with the same issue or point me any solution. It would be a great help.
 

 Regards
 --Sachin