Official 5.5 Beta Release Thread

[Dean Roddey]

5.4.913

• The list browser widget will cause an index error if it has less than a page full (and hence free space at the bottom) and you click past the last one when there is a defined click action.
  
• The Radio RA2 driver is sending out motion events but not storing the motion state to the field.
  
• The Radio RA2 driver complains if the low set point is >= to the high. Let them be equal at least, though that may cause some confusing in user logic if the difference is zero.
  
• Now that we are no longer downloading C++ drivers (client or server) we don't get the info about whether they have associated loadable resource files. Since they are local now, just look for the files before we load and set the flags that way.
  
• When importing quite small images into CQC you can get an error because the small size caused an inversion of initial and max sizes of a memory buffer used in the process.
  
• Interface containers (overlays in this case) are supposed to inform all their children when they are hidden or shown, to allow them to react if needed. Mostly they don't, but web brower and web cam widgets are special cases because they are separate windows that need to be hidden/shown.
  
• Add what I think is correct support to the Radio RA2 driver for the contact inputs. We'll see if it works. We assume if it as a component id of 32 or 33 then it's an input, else an output.
  
• Correct something in the RA2 driver now before it's too late. Contact closures are semantically read only. The read/write contacts on the Visor should be marked as relays, since those are semantically read/write. So the field names will change for the previously added r/w contact closures.