C++ Expert Needed for FileMaker Plug-In
Budget: $50 – $0 AUD
This is a call out to expert C++ programmers see who can assist in making a FileMaker plug-in display in FileMaker Pro with its functions visible in the Script environment.
OPTIONAL FOR EXTRA PAY
The plug-in does return results (or, more accurately, did work except I now have an issue with it, see below for more details), but has virtually no error reporting when something doesn't work, compared to say Terminal.app on macOS which does provide feedback. If this feedback can be returned by the plugin, that would be extremely helpful. Otherwise, when the plug-in does work, it works like a charm.
THE ISSUE
There is very little to do in this project as the plug-in code has already been re-organised, all errors fixed, and have even gone through all the deprecated warnings. I use the C++17 compiler, which returns a "Successful Build" every time. The problem is that even after comparing the code to other plug-ins that do show up in FileMaker Pro, it is not apparent what is stopping the plug-in from showing up in FileMaker Pro.
The successful freelancer for this project will not only identify the cause for this issue and fix it, but also return the code and highlight where the problem is, so I can test it at my end.
Key Responsibilities:
- Code testing and modifications as needed
- Only one bug fix (a rarity these days!). Just make the FileMaker plug-in show up in the FileMaker Pro app so I can see the available functions.
Ideal Skills:
- Extensive experience and proficiency with C++. No students learning on the job for this project. Only experts please.
- Familiarity with FileMaker Pro and its plug-in C++ codebase structure is desirable, but not essential.
- Strong problem-solving skills and attention to detail is a must.
Please note that the primary task will be debugging to find the culprit to the above mentioned issue, but I'm also open to suggestions for performance optimization and potential feature enhancements.
Happy bidding everyone!
OPTIONAL FOR EXTRA PAY
The plug-in does return results (or, more accurately, did work except I now have an issue with it, see below for more details), but has virtually no error reporting when something doesn't work, compared to say Terminal.app on macOS which does provide feedback. If this feedback can be returned by the plugin, that would be extremely helpful. Otherwise, when the plug-in does work, it works like a charm.
THE ISSUE
There is very little to do in this project as the plug-in code has already been re-organised, all errors fixed, and have even gone through all the deprecated warnings. I use the C++17 compiler, which returns a "Successful Build" every time. The problem is that even after comparing the code to other plug-ins that do show up in FileMaker Pro, it is not apparent what is stopping the plug-in from showing up in FileMaker Pro.
The successful freelancer for this project will not only identify the cause for this issue and fix it, but also return the code and highlight where the problem is, so I can test it at my end.
Key Responsibilities:
- Code testing and modifications as needed
- Only one bug fix (a rarity these days!). Just make the FileMaker plug-in show up in the FileMaker Pro app so I can see the available functions.
Ideal Skills:
- Extensive experience and proficiency with C++. No students learning on the job for this project. Only experts please.
- Familiarity with FileMaker Pro and its plug-in C++ codebase structure is desirable, but not essential.
- Strong problem-solving skills and attention to detail is a must.
Please note that the primary task will be debugging to find the culprit to the above mentioned issue, but I'm also open to suggestions for performance optimization and potential feature enhancements.
Happy bidding everyone!