Wish I would like config path to be an optional switch when launching B4A (and B4i, B4J)

[Sandman]

The B4X suite supports b4xV5.ini in two locations:

1. In the AppData\Roaming\Anywhere Software\B4[AiJ] directory
2. In the actual directory if the B4[AiJ] binary

If there's an .ini in the actual application directory it overrides the .ini in the Roaming directory path.

I would like to have a switch for the B4[AiJ].exe binary that lets the developer specify a path to an .ini that will override the two locations above. For instance -config=<path>

This feature would enable developers to easier have per-project settings.

 

[JordiCP]

Agree. A step in that direction would certainly ease usability, specially if one works with multiple customers/projects and repos.

 

[Sandman]

This was an unexpected, and very nice, surprise:

I understand completely why you don't want to talk about upcoming features, or if/when they will show up.

But as I suspect that this feature probably wouldn't be overly difficult to implement, can you at least give some indication on whether you think it will happen? And if it will, perhaps whether it will happen within 6 months..?

Yes, I thirst for information because this feature would be a big deal for me.

 

[Erel]

I hope to add it the next version of B4A (or any other IDE). It will happen in less than 6 months.

Sometimes when you start implementing a feature you realize that it is more complicated or problematic than you first expected, so there is always place for some doubts...