Mouse Macro PIC 737

[martinair]

Pete,

I am using your great tool (in registered way) - thanks a lot for that. I a musing FSUIPC 3.9

My favorite Add on plane is the PIC 733.

I bulid a Mous Macro for a toggle "PIC733 Engine start levers1" as there was no way of finding the wilco Keyassignments for that.

It works on the 737-300

I did the same (a new Mouse macro) for the 737-400 and this is not working.

In my FSUIPC INI file I have Button programmed for each of the planes ( "feelthere 737-300" and "Feelthere 737-400").

Each of the planes have its own panel and in the macro file you can see the difference.

Do you have any idea, what I need to do to make the PIC 734 macro work?

If you need a copy of my FSUIPC.ini or the macros, I will send it to you.

Thanks a lot in advance and best regards from Germany

Martin

[Pete Dowson]

I did the same (a new Mouse macro) for the 737-400 and this is not working.

Did it work when you tested (via TAB) before naming it? If not, then the aircraft gauge concerned is probably simply not amenable to the way FSUIPC intercepts and handles the calls.

Do you have any idea, what I need to do to make the PIC 734 macro work?

No, sorry. I don't have all of the add-on planes one can get and I cannot undertake to test them all. The mouse macro facility is provided for you to try. If it works, great, if it doesn't it is unfortunate, but there's nothing really I can then do. It is quite easy for Gauge programmers to write gauges in a way which prevents the macros from working -- this is why you must always run the TEST as instructed.

Note that almost all of the default (Microsoft-written) gauges are not amenable to mouse macros either -- Microsoft did not follow their own rules in writing those gauges!

The only way might be to use something like Luciano Napolitano's "key2mouse" program to convert keypresses to mouse actions, and then program the buttons to send the keypresses.

Regards

Pete

[martinair]

Pete,

thanks a lot for your reply. I hope you had a great vacation time.

Regarding your answers: Yes I did test the macro with the TAB key and it worked. After that I did reopen the FSUIPC, I did end the macro making and after that I did add the function to the button (from the FS list, where the macro was now added). I did it the same way as I did it on the 737-300 where this function is working.

Best regards

Martin

[Pete Dowson]

... I did test the macro with the TAB key and it worked. After that I did reopen the FSUIPC, I did end the macro making and after that I did add the function to the button (from the FS list, where the macro was now added).

Well, if it worked with TAB, it should work okay normally, because the way it operates on "TAB" is the same as when it operates after you assign it and use it.

So, something else may be wrong. You could try enabling the Button and Key logging facilitiy (FSUIPC logging options) and see what that reports when you atrtempt to use the button you programmed. After that, perhaps you need to show me the relevant [buttons ...] sections of your INI file, and the [MacroFiles] section, and the Macro file you refer to as well. I will also need to know the version number of FSUIPC.

Regards

Pete

[martinair]

Pete,

I guess I found my mistake. It is working now. What I have done:

I copied the mous macro of the working one for the 737-300 to the new one called 737-400. In the fsuipc.ini file it was the last one in the [macro] part. I checked it with the TAB key and it worked. But it did not work with the button. As it was the last one in was not in the alphanumerical order and it seems to me that that was my fault. After deleting all macros in the ini file of the FSUIPC I restarted the FS 9 and redirected all buttons to existing macros. That did make the change in the FSUIPC.ini, where now the macros apear in alphanumerical order.

The best thing is, that it workes.

Thanks a lot for your supply. I really love your tool. From my point of view it is the best addon to the flight simulator and you do offer the best support I have seen on all the addons I own.

Best regards

Martin

p.s. sorry for my not very professional English

[Pete Dowson]

I copied the mous macro of the working one for the 737-300 to the new one called 737-400. In the fsuipc.ini file it was the last one in the [macro] part.

You can't really do that, unless they use the same Gauge (.GAU) or DLL (.DLL) module, because they are linked to it by a reference parameter. Additionally the macro entry numbers (line numbers) must be contiguous and correct, of course.

I checked it with the TAB key and it worked.

The TAB key only checks the macro details you set BEFORE they are written to the file. The assignment of buttons or keys is completely dependent on macro filename and macro name, which are encoded numerically according to the file number in [MacroFiles] and the line number in the referenced .MCRO file.

As it was the last one in was not in the alphanumerical order and it seems to me that that was my fault.

Well, not so much alphanumeric order -- the macro numbers need to be contiguous, but it is more the cross-referencing between macro file, macro number and GAU or DLL module which needs to be correct. All of that is encoded into the Button Assignment in one 32-bit number.

Anyway, glad you got it working. I'm afraid there are no easy short cuts from making each macro for each panel.

Regards

Pete