Hello everybody,

 

I was wondering if there already is an user lib available to easily access the enhanced controls to the iFly 737 which are provided through their iflytofsuipc.exe

 

I started to copy the documented commands to a user lib but before doing all the effort, maybe someone already did it. I know that there is a module from Helge - but it only supports EFIS and MCP through macros. My goal is to write directly to the ifly fsuipc offsets.

 

Cheers,

Sebastian

I uploaded my lib-file. Just remove .txt-extension and copy it to your LINDA/linda/libs/-Folder. You can then access all key-functions provided by the iflytofsuipc.exe

 

Maybe it is of use for someone.

 

Cheers,

Sebastian

Thanks Sebastian,

 

but why haven't you written this into the IFly module (actions.lua) instead of making a LIB?

 

 

I do not have the IFly, but maybe there are some other LINDA IFly users out there who can rework the module...

Thanks Sebastian,

 

but why haven't you written this into the IFly module (actions.lua) instead of making a LIB?

 

Just because I am new to LINDA and don't understand the differences between module and lib. Where are the concepts explained? Also, I didn't want to alter Helge's module.

 

Just tell me how to do it better and I make any adaption. If I understand you correctly I just have to copy the contents from my file to the actions.lua provided by Helge's iFly module.

 

Cheers,

Sebastian

Just tell me how to do it better and I make any adaption. If I understand you correctly I just have to copy the contents from my file to the actions.lua provided by Helge's iFly module.

 

Yep, simply copy it into Helge's action.lua.

Would be nice if you contact him first and ask, just for the sake of politeness.

Otherwise I could also copy them together and make a separate module with credits to you and Helge. (or you could do this also, of course)

 

 

What you could please do is to sort the functions a bit with the separators: e.g.

 

-- ## Lights ###############

-- ## Engine ###############

-- ## Electric ###############

 

or whatever make sense to you ...

 

this makes it a lot easier for users to find and select a fucntion

 

 

Many, many thanks!

What you could please do is to sort the functions a bit with the separators: e.g.

 

-- ## Lights ###############

-- ## Engine ###############

-- ## Electric ###############

 

or whatever make sense to you ...

 

well actually there already is grouping in the file. It is based on the grouping provided by iFly documentation.

 

I imagine that we have to merge groups from Helge's macros and these actions which may be kind of work to do ;) There are also functions that are defined through macros with helges solution, too. How do we deal with these issues? This was another reason why I haven't merged the configs yet. Wouldn't it be easier to have two different configs? Another argument is, that there is an external dependency to the iflyftofsuipc.exe. Helge's module doesn't have it. Actually I am worried that people get confused when trying to assign actions that depend on the ifltofsuipc.exe and others do not.

 

What do you think?

 

Cheers,

Sebastian

Wouldn't it be easier to have two different configs?

 

ok, ok, I see, you really know what you are doing.

Thats opposit to me that I have no clue about the IFly stuff ...

 

If you think it is better to have two modules, that is no problem.

 

But a module would be better then a library or I'm false?

You should only explain to users what the difference is between th both modules when we upload them ...

But a module would be better then a library or I'm false?

 

If you can point me to a doc or provide me more information so that I am able to understand the intentions and differences between the concept of lib and module, of course I'll pick the most appropriate of both ;)

 

Cheers,

Sebastian

LIBs a mainly used to serve functions for all addons, like weather, or to manage external tools, like AivlaSoft EFB, IVAO etc...

 

A module is addon specific and would be selected automatically from LINDA.

If you add a libray function, this is valid for all addons, a module will be loaded only for the special addon (except FSX default planes...)

Ok... then it has to be a module ;) I'll fix this tonight.

 

Cheers,

Sebastian

I re-thought the thing.. I joined the functions into Helge's module and used a FSUIPC.prefix to clearly distinguish the functions.

 

Then I tried to detect whether the exe is running or not in the "InitVars" function. This works quite nice by applying a workaround where I write and read and offset to see if the offsets are available (and they only are if the .exe is running).

 

On the first time a user tries to execute an iflytoFSUIPC.exe-specific function without the .exe running, an error message will be shown.

 

I will get in contact with Helge to inform him about my update.

 

@Guenter: Please review my code to check if there is a better way to perform the detection and message display.

 

Cheers,

Sebastian

Feel free to update it :)

I only used macros because that was the only way to do it last year. It might be better to get rid of the macros alltogether if possible. I know from earlier ifly updates that they all have to be redone whenever a new version is released.

 

Helge

Ok, I will replace the macro calls with the adequate fsuipc function so it stays backward compatible and existing users won't have to change their configs. I also will remove the existing groups and put all legacy functions into one single folder/group named "DEPRECATED.". This won't affect the configs but will hopefully give a hint to new users, that they shouldn't use those. Another possibility would be to provide two different versions. One for new users without any legacy overhead and one backward compatible one. Actually I would prefer the last because I am a friend of clear and simple things that everybody can understand. Which one would you prefer?

 

I already created some additional groups in the new config to have less functions for each group. I will also remove the first part of the function call if there are no conflicts within the function names. This will make it easier to read when assigning functions.

 

Cheers,

Sebastian

Here's my current Version 1.0 1.1 of the updated module:

 

* support of iflytofsuipc.exe - no macros anymore, this approach is more update safe

* all 1247(!) documented key command offsets supported

* more groups than in iFly documentation for easier look up of actions

* backward compatibility to existing configs - but they only work with the iflytofsuipc.exe running

* basic detection whether iflytofsuipc.exe running or not

* user notification in FS if iflytofsuipc.exe not running

 

Tested only in FSX. Not all functions tested. I haven't tested backward compatibility (who can do that?)

So, means that should/could replace the current IFly module???

 

 

Many, many thanks for this great work!!!!!!