Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MT12 Companion Simulator #5898

Open
1 task done
chofchop opened this issue Feb 12, 2025 · 6 comments
Open
1 task done

MT12 Companion Simulator #5898

chofchop opened this issue Feb 12, 2025 · 6 comments
Labels
enhancement ✨ New feature or request simulator

Comments

@chofchop
Copy link

chofchop commented Feb 12, 2025

Is there an existing issue for this feature request?

  • I have searched the existing issues

Is your feature request related to a problem?

The long-awaited companion for MT12 has finally been released. This is very gratifying.
Without further ado, I would like to point out a few points that caught my attention.

  1. When Axis X and Axis Y are specified for Pots, they are not reflected in the simulator.
  2. The simulator's button layout and the actual machine's switch panel are slightly different.
  3. Unable to input "enter" key using mouse wheel button.

Describe the solution you'd like

  1. Axis X and Axis Y inputs can be operated on the simulator.
  2. Make the button layout of the simulator the same as the switch panel of the actual machine.
  3. Since the rotary encoder is operated with the mouse wheel, the enter key should be a mouse wheel button.

Describe alternatives you've considered

Regarding 3. above, the same applies not only to MT12 but also to all models equipped with a rotary encoder.

Additional context

It would be even more convenient if "PAGE>" and "PAGE<" could be operated using the tilt button of the mouse wheel (horizontal scroll).

@chofchop chofchop added the enhancement ✨ New feature or request label Feb 12, 2025
@pfeerick
Copy link
Member

pfeerick commented Feb 12, 2025

  1. Axis X and Axis Y inputs can be operated on the simulator.

By this, are you referring to the flexible inputs, i.e. the swappable pot/switch/gyro module? As that may be a seperate issue, related to Companion support for simulating the flexible inputs and unique hardware like gyro X/Y inputs.

  1. Make the button layout of the simulator the same as the switch panel of the actual machine.

I do not believe this will be happening. We have moved to a generic model for all radios, so none of them perfectly match the layout of the real-life handset. The focus is on the availability of the input controls, not realism.

  1. Since the rotary encoder is operated with the mouse wheel, the return key should be a mouse button.

Interesting idea, it would be nice if it is possible. At the present time you would press the Enter/return key or click the enter button (which isn't so bad since you can have the mouse hovering over the Enter button while scrolling the mouse wheel).

It would be even more convenient if "PAGE>" and "PAGE<" could be operated using the tilt button of the mouse wheel (horizontal scroll).

And/or the back/previous buttons, as not all mice have horizontal scroll functionality, but some also have dedicated back/previous buttons.

@pfeerick pfeerick changed the title MT12 Companion MT12 Companion Simulator Feb 12, 2025
@chofchop
Copy link
Author

By this, are you referring to the flexible inputs, i.e. the swappable pot/switch/gyro module? As that may be a seperate issue, related to Companion support for simulating the flexible inputs and unique hardware like gyro X/Y inputs.

This is not limited to flexible inputs. Even if Axis X or Axis Y is assigned to S1 or S2, it will not be reflected in the simulator.
Assigning pots and sliders will be reflected in the simulator. I pointed this out five months ago.

I do not believe this will be happening. We have moved to a generic model for all radios, so none of them perfectly match the layout of the real-life handset. The focus is on the availability of the input controls, not realism.

I'm not looking for reality, but it's much easier to operate if the layout is the same as the actual machine.
Is it really that difficult to move the button a little as shown in the image?
Image

Interesting idea, it would be nice if it is possible. At the present time you would press the Enter/return key or click the enter button (which isn't so bad since you can have the mouse hovering over the Enter button while scrolling the mouse wheel).

It would be even more convenient if "PAGE>" and "PAGE<" could be operated using the tilt button of the mouse wheel (horizontal scroll).

And/or the back/previous buttons, as not all mice have horizontal scroll functionality, but some also have dedicated back/previous buttons.

Although adding these shortcut keys may be useful, I don't think there are any disadvantages. Registering multiple shortcut keys is not a difficult task, right? It would be best if the user could customize the shortcut keys.

@chofchop
Copy link
Author

In the first post, I confused the "enter" and "return" keys. It has now been fixed.

@pfeerick
Copy link
Member

pfeerick commented Feb 12, 2025

Even if Axis X or Axis Y is assigned to S1 or S2,

Ok, so this is related to the gyro/IMU simulation (or lack there of) then... meaning this is not MT12 specific. Probably should be a seperate issue.

Is it really that difficult to move the button a little as shown in the image?

Probably not (difficult). Just need to bear in mind the shown layout only applies when you have "all" simulators (not just the MT12 one) configured to show the buttons on the right side, rather than the Default setting of buttons on both sides of the display.

Registering multiple shortcut keys is not a difficult task, right?

Nope, this is why multiple shortcut keys already exist for some controls. The main question will be if QT5 allows for that event to be captured in the first place.

It would be best if the user could customize the shortcut keys.

This has been discussed already as something we already want, and are simply just not there yet. Also well beyond this scope of this issue ;)

@chofchop
Copy link
Author

Thank you for your detailed explanation.

@elecpower
Copy link
Collaborator

The 1st iteration has tried to balance 3 OSes and multiple keyboard sizes/layouts.
Once this iteration has stabilised then customisation is an area for attention subject to priorities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement ✨ New feature or request simulator
Projects
None yet
Development

No branches or pull requests

3 participants