7 replies to this topic

[freezy]

Hi!

 

Your project looks interesting, however before I put any time into it I wanted to know if you happen to have a public repo with the source code anywhere? I've searched a little but couldn't find anything and noone seems to have asked the question before.

 

Thanks in advance!

[TerryRed]

DDH69 (creator of DOFLinx) is on vacation for a week or two, but as far as "I" know, there isn't a public repo of any sort. (I could be wrong....)

 

Maybe send him a PM to ask him some more in depth "programmer to programmer" type stuff.   

 

dmdext rocks freezy.

[DDH69]

There is no source code provided. While I'm still actively developing and supporting I am unlikely to release it.


.... and yes, holidays at present. The weather in Bali is sssoooo much nicer than home!

[freezy]

Pity. In my experience open sourcing a side project brings far more advantages than drawbacks. You'll get free bugfixes, features and community love and yet it's still you navigating the boat.

[jarringmars]

I know this topic is pretty old but I was looking for the DOFLinx source code today and I see that it's still unavailable to the community.  It would be great to be able to share in this great project. 

[Urko]

There is no source code provided. While I'm still actively developing and supporting I am unlikely to release it.


.... and yes, holidays at present. The weather in Bali is sssoooo much nicer than home!

[fulg]

One more vote for releasing the source code, otherwise as a programmer my only option to fix or change things is to rewrite the whole thing. Since you are using GitHub as a distribution platform now it is kind of going against the spirit of the site, as the source is not available and nobody can fix bugs and/or add features.

 

In my case I wanted to look at the code to understand how the directoutput.dll is searched for (for some reason DOFLinx is using a hardcoded path C:\DirectOutput, why?) but I am sad that I cannot find out, I will have to keep guessing.

 

Similarly it is unclear how the whole x86/x64 thing is handled (my guess is "not at all", it is a complicated topic), again the code would answer this quite clearly but it remains a mystery.

 

Now don't get me wrong, I appreciate the work that you do for free and I am glad you keep releasing updates, but keeping things closed is no fun for everyone else.

[DDH69]

One more vote for releasing the source code, otherwise as a programmer my only option to fix or change things is to rewrite the whole thing. Since you are using GitHub as a distribution platform now it is kind of going against the spirit of the site, as the source is not available and nobody can fix bugs and/or add features.

 

In my case I wanted to look at the code to understand how the directoutput.dll is searched for (for some reason DOFLinx is using a hardcoded path C:\DirectOutput, why?) but I am sad that I cannot find out, I will have to keep guessing.

 

Similarly it is unclear how the whole x86/x64 thing is handled (my guess is "not at all", it is a complicated topic), again the code would answer this quite clearly but it remains a mystery.

 

Now don't get me wrong, I appreciate the work that you do for free and I am glad you keep releasing updates, but keeping things closed is no fun for everyone else.

 

Perhaps the release notes can assist you with the issue you have.  Here are a the relevant excerpts since the updated mjr version:

 

8.23 17/2/25

- Change the order or searching for a valid DirectOutput.dll so that the local folder is the last place looked.

  This forces the use of installed DOF versions first.

  Remember, you can force a path for which DirectOutput.dll to use by placing DOF_PATH=\Thelocation\ as a command line argument

 

8.13 11/10/24

- Fix, reintroduce the display of date / version information for DirectOutput.dll

 

8.12 3/10/24

- New allow loading of DirectOutput.dll from any location.  A valid DLL will be sought in order from 

    1. User set via DOF_PATH= on the command line at startup

    2. If a DLL is in the same startup folder as DOFLinx.EXE

    3. As defined by the DOF CLSID entry

    4. As defined by the registry entry for DOF

    5. by checking C: to F: drive in \DirectOutput, and the appropriate folder of \DirectOutput\x32 and \DirectOutput\x64

 

Let me know if you have any other questions.