Select Module function

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.
 

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.

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

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.  

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

Please do read the handbook. It may help you understand how this part of the forum works.

williamcopper
I have read it.  That doesn't mean I'll follow it.

That is OK. I just did not want you to be surprised when others do.

Inconsistency <> bug.
If valid this is an enhancement request.

Roll a dice then for outcome....At this stage the OP should be off to the problem reporter and pasting CWBRN here.

scook
Please do read the handbook. It may help you understand how this part of the forum works.

i did (surprise!) and (to me) it says troubleshoot here in this forum and then move to relevant forum if necessary, rather than troubleshoot elsewhere (sonar forum) then move here once verified/reported/numbered... just ambiguous guidelines i suppost but generally (and especially in technology) the author should aim to avoid being misunderstood (as apposed to being understood) unless ambiguity is a goal like in poetry etc

Still a problem in Cambridge.   Not that big a deal, but an annoying little thing.  I use the Selection Module constantly, as would anyone working from a music score with bar numbers and ranges outside the reasonable view of a screen.

The Select Module behavior reported by the OP has existed since Sonar X1 was released in 2010.  A likely reason for the behavior still existing is that most users probably do selections using the mouse and do not use the Select Module.  In other words either no one noticed the issue or no one was motivated enough to file a Problem Report.
 
Submitting a Problem Report is no guarantee that the problem will be fixed, but hoping that the problem will be "magically" fixed without submitting a Problem Report is a futile waste of time.
 
Workaround you may or may not know about: When the user sets the Now time to the start of the desired selection and clicks the From button in the Select Module, both the From and To fields are set to the same Now time value.  This will help prevent the undesired behavior from occurring.
 

If someone had a problem with you William but did not tell you how would you know.  It is only by telling you directly you would know.  
 
The Cakewalk problem reporting form is how cakewalk learn that there is a problem  If it is not used they will not necessarily know or do you believe them to be psychic.
 
All software creators have a method to report "problems" with their product, Cakewalk have a form here.
 
https://www.cakewalk.com/Support/Contact/Problem-Report
 
It is how us mere mortals make reports.
 

Very few Cakewalk employees spend time in these forums, they're too busy working on the products themselves. Mentioning an issue in the forums is great for getting confirmation from others if something is indeed a bug, or finding out it's pilot error or a computer issue or whatever. But if something is a bug or a feature request, it needs to be put in a format that someone at Cakewalk will see. Otherwise it's doubtful any action will occur.