This trend of fancy schmancy mouse clicks for switches, dials, views, etc etc etc.

Right click to rotate right.

Left click to rotate left.

Right click to open fully.

Left click to open partially.

Right click to open cap, Left click to close (Why???!!!!)

Right click Left click Right Lfet Rtdg cRlik..............

 

Problem 1 .... developers all do it differently.

Problem 1.5 ... it's often not even consistant on the same aircraft, let alone trying to keep up with the inventive clickies of each addon I fly.

Problem 2 ... right clicking also opens the window dialog box, so every time you Right click where there happens to be no Right click option that damned window pops up ........ again ......... asking me what I want to do with window options. The answer each time is of course "nothing. go. away."

 

It's madness. And it is actually far, far more irritating than I find myself able to articulate or detail here. There was once, not so long ago, a perfectly fine, universal system of Left clicking and mouse wheeling up/down.

 

Click left side - thingy moves left

Click right side - thingy moves right

Click one side of cap - cap opens

Click other side - cap closes

Click outer area - big numbers change

Click inner area - small numbers change

 

I LOVE that ^^^

 

Simple. Logical.

 

Click areas are many times less frustrating than the guesswork involved with the inconsistancies of clickology, clickomatics, clickapalooza, and the irritating little surprises when guessing wrong.

Life can be tough sometimes.

You can always build yourself a real cockpit then and get rid of the mouse - squeak squeak

I fully understand! The NGX has about the best system I've used.

What ever you do, never ever try X-Plane, you will be gutted when you try operating their controls! ;-)

I don't know about you, but I don't find it so bad. Not bad at all, actually.

I think that each developer should do it how they best see fit to their product.

 

It's almost like you would require that each car has the same controls, placed at the same spot and handles the same. How boring would that be?

This trend of fancy schmancy mouse clicks for switches, dials, views, etc etc etc.

Right click to rotate right.

Left click to rotate left.

Right click to open fully.

Left click to open partially.

Right click to open cap, Left click to close (Why???!!!!)

Right click Left click Right Lfet Rtdg cRlik..............

 

Problem 1 .... developers all do it differently.

Problem 1.5 ... it's often not even consistant on the same aircraft, let alone trying to keep up with the inventive clickies of each addon I fly.

Problem 2 ... right clicking also opens the window dialog box, so every time you Right click where there happens to be no Right click option that damned window pops up ........ again ......... asking me what I want to do with window options. The answer each time is of course "nothing. go. away."

 

It's madness. And it is actually far, far more irritating than I find myself able to articulate or detail here. There was once, not so long ago, a perfectly fine, universal system of Left clicking and mouse wheeling up/down.

 

Click left side - thingy moves left

Click right side - thingy moves right

Click one side of cap - cap opens

Click other side - cap closes

Click outer area - big numbers change

Click inner area - small numbers change

 

I LOVE that ^^^

 

Simple. Logical.

 

Click areas are many times less frustrating than the guesswork involved with the inconsistancies of clickology, clickomatics, clickapalooza, and the irritating little surprises when guessing wrong.

 

Then build your own gauges!! What the left/right click does on particular gauge is no different to learning a specific cockpit procedure for a specific a/c type. Not all a/c are the same / nor is the gauge layout the same / nor are the switches and buttons the same.

So put your money (Bear in mind that most stuff is freeware!!) where your mouth is, and design cockpits for different a/c with different gauges, switches and functions and I think you will be eating your words somewhat!!

vololiberista

vololiberista, though I do share your opinion, please choose your words more carefully. Your post is coming over very rude.

i think to get rid of this problem, you need to invest in MCP and EFIS, i do not use keyboard anymore use an EFIS and MCP if you are flying like a 737 or 747.

 

For me it's checkride material. After not flying a particular AC for a few months you can forget how what works.

The most intuitive approach to me is using the middle wheel. Point the mouse anywhere on the knob and rotate the wheel. Maybe the SDK does not allow that, but some smart developer I am sure could introduce it. Standardization is a wonderful thing.

 

Bob

vololiberista, though I do share your opinion, please choose your words more carefully. Your post is coming over very rude.

 

I don't intend to be "rude"! And I'm sure some developers like to "show off" a bit. However the button clicks are there mostly out of necessity.

I can quote 2 examples:-

1. The Nav_Info icon has a left and or right click function left for the airport db and right for the map thus avoiding two icons on the panel.

2. CIVA INS. in real life some of the numeric keys have to be pressed simultaneously to activate certain functions like "updating"

This can't be done either on a keyboard or by a mouse so the option to right click on individual no.s is provided.

 

The most intuitive approach to me is using the middle wheel. Point the mouse anywhere on the knob and rotate the wheel. Maybe the SDK does not allow that, but some smart developer I am sure could introduce it. Standardization is a wonderful thing.

 

Bob

 

There are plenty of gauges that do that already. Altitude gauges quite often have that feature.

 

The poster is unfortunately going to have to learn to live with gauges that work differently in different a/c. (After all that is as "real as it gets!")

vololiberista

I think one would be surprised how much influence the community can have on the developers. I have no idea how much work is involved when you compare one method of turning a knob to another method. I think it just requires a plea to developers to give this a thought. I remember when the huge argument over pure FSX models was going on. Developers not divulging whether or not their product was a pure fsx model. I think because of the community and the awareness of this, developers were obigated moving forward to provide that information. I turn most of my knobs from external hardware, so I personally am not that concerned, but I will join the fight :aggressive:

The most intuitive approach to me is using the middle wheel. Point the mouse anywhere on the knob and rotate the wheel. Maybe the SDK does not allow that, but some smart developer I am sure could introduce it. Standardization is a wonderful thing.

 

Bob

 

I use the wheel all the time except for the Wilco AC which a right click will let you jump by 10 instead of one.

I helped solve that issue buy purchasing some hardware and re-assigning knobs and such via FSUIPC. Now, mostly, all adjustments are using the same button, knob, or switch no matter which aircraft I fly. I couldn't stand to use the mouse in VC.

I don't mind the operation, what I mind is tiny clickspots. And clickspots partially hidden behind other knobs. I've got TrackIR and I still find the partially hidden ones to be a PITA.

 

Sometimes, (and I can't believe I'm writing this) 2D panels are better especially when its bumpy and I'm doing many other things single pilot IMC argh....