Messages

Why don't we use the on-screen "Q" quick menu button to open ML since we have a button for that on the dial already?  It's a cleaner function behaviorally than the 2 finger tap, in my opinion.

Edit:  Alternatively, is it also possible to use the pinch-to-zoom function during live-view [not playback] and open ML very much in the same way you open an album on an iPad?  Expanding from a pinch function with a threshold for "snaping" open.  I think the Q button is still cleaner, but the pinch could be another method that is still fairly intuitive for opening

Great, I'll keep that all in mind.  I will most likely play it on the safe side, but who knows what my impulsive side will have me doing 


I'm not familiar with working with a hack, so I hope you guys don't mind a couple questions. And please excuse my programming ignorance.

- What limitations do we have with interacting with Canons UI
- What limitations do we have with altering Canons UI
- Can we place controls on the main UI that have ML functions
- Are touch controls for x,y coordinates looking likely, and are visual cues for those functions also likely
- Are layers possible for touch controls, and can layers be given priorities
- Is there a way to assign the ML menus a variable [for lack of better words] so that when the ML menu is opened, all the buttons and scroll wheels function within that same variable essentially creating and isolated system for button assignments?


Also, is the ML menu open to alterations?

Hey Coutts,

New here, but wanted to ask you how camera safe these alpha versions are?  I understand that the ML firmware itself is already developed, but when booted on new devices, what are the challenges you have been facing as far as stability?

Normally I'd wait because I am new to ML, but I am also an Industrial Design student and have a little experience with human factors on interface design and wanted to jump in and see if I couldn't join the "mind pool" and see if I could help with the progression of this product.

However, I can't help with writing firmware, so it would be incredibly naive of me to jump in during this stage to tackle something that is better off handled after stability has been reached.


Anyways, thanks for your hard work.  Looks like you've already taken on a skill-set that will land you a sweet little career after college.  Take care.


Michael