Compare "Loop" module start and end entry fields with "Select" module start and end entry field.  
If not already set, use Bar:Beat entry format.
 
Set both modules to the same values, begin 5:00 and end 10:00.  
 
Now try to set a new Loop range of 15:00 to 20:00 by typing the Start bar first, then the End bar.  It works.
 
BUG:  now try to set a new Select range of 15:00 to 20 by typing the Start bar first, then the End bar.  It doesn't works.
 

I tried this in Platinum 21.01.00 Build 38 x64 and concur that the Loop and selection fields do not accept type entries correctly.  Can someone else please test this and confirm thank you.
 
Just for the record when testing please type your entries as requested by William because when trying the above the way I normally do selections, from the ruler with a point and drag, the figures placed in the Loop and Select boxes are updated correctly.

It will not allow one to move the start point past the end point. To move the start point past the end point, change the end point then the start point.

scook
It will not allow one to move the start point past the end point. To move the start point past the end point, change the end point then the start point.

If I understand what you are saying then to complete the changes indicated by William the correct method would need you to change the endpoint first then the start point?
 
Which I have tried and it works as expected.  Thanks for testing this Scook knew I was missing something as I never use the selection and loop boxes by manual entry, always point and drag in the time ruler, or lasso selection.

Yes, the entry fields will not allow a start value larger than the end value.

scook
Yes, the entry fields will not allow a start value larger than the end value.

That is logical thanks for your help here Scook

Come on guys.  "this is logical?"    Did I not illustrate the Loop module acting differently?  That one is "illogical" then?  This is a bug.
 
It is also new, bad, behaviour introduced with the x stuff.  

And btw, the human brain just doesn't work that way:   set end and then set start.    Just pass it on to the programmers, please, they have already made the loop module work correctly, this should be a very very very simple fix.

Please read the handbook http://forum.cakewalk.com/FindPost/3151738 there is no "pass it on to the programmers" option but you may fill out a formal report with the Problem Reporter

scook, just a bit of background: when I was younger, and probably nicer, I contributed a great deal to the improvement of sonar 3 to sonar 5.    I USE the software, heavily.    Don't discount, please, my experience because it doesn't match your experience.  (my username at that point was anonymous .. don't see the point in that anymore, since google knows all about me already)