Jump to content

Recommended Posts

Posted

Would it be possible to setup an internal template for DOF?

 

I am specifically thinking of many of the Config entries which actually to the same thing:

Fire Button		W16 Blink fu500 fd650
Fire Button RGB		W16 Blink fu500 fd650 Cyan
Fire MX			W16 Blink fu500 fd650 Cyan AT0 AL0 AW100 AH100

and

RGB Flippers		ON Blue
Flipper Button MX	ON Blue AT0 AL0 AW100 AH100

To me it should  possible to  at least go from RGB to MX semi automatically, normally going from RGB to MX means adding "AT0 AL0 AW100 AH100" to the RGB value. I was thinking of adding a templating system to the config tool?

 

Fire Button		W16 Blink fu500 fd650
Fire Button RGB		W16 Blink fu500 fd650 Cyan
Fire MX			{Fire Button RGB} AT0 AL0 AW100 AH100

This means when adding new config entries "Fire MX" would be automatically filled from the "Fire Button RGB", the "Magnasave Left MX" from "RGB Left Magnasave" and so on.

Reason for doing this? Well, looking at the config's you will see a lot of MX entries are missing and manually going through them in the WEB GUI you get sort of bored. Rather I would "fix" it in the backend...

 

Any comments?

 

/Jarr3

  • 2 years later...
Posted

An example is Fire Button compared to Fire MX.

 

Fire Button is defined for 100 tables, whereas Fire MX is only defined for 57 tables.

Would be good if * MX could be derived from the non MX version automatically.

Posted

Cool, will check it out! Though I beleive I got scared last time when I heard it used PHP...

 

I started this thread 2 years ago ;)

 

But since I have seen rumours that someone is rewriting the online DOF config tool and also @Dazz is asking for support: (from the config tool page)

 

Quote

Help Wanted!

The DOF Config tool has been prooving its necessity for the past 13 years. It is really showing its age... This tool is a very important tool for the digital pinball community and is at the heart of almost everyones build. We are in dire need of a developer to help bring this tool up to todays standards.

We are looking for a trust worthy compitent developer that would be willing to help bring this tool up to todays standards. Currently the tool uses PHP and SQL, but if you think we could take advantage of newer tech/code I am open for suggestions.

If you enjoy this tool, and think that you have the skills to help the community out please send a private message to Dazz via VPUniverse.com or via Discord at its.me.dazz.

 

I thought to reactivate this thread to not forget about it.

  • 2 months later...
Posted

@jarr3,

 

Yes, this is definitley something which can be added easily. - I was thinking of adding it to the "Save and Add Matrix Functionality" Action.

See if there is an entry for Firebutton RGB and if so create the Firebutton MX accorging to your recipe. - Same with Flipper RGB

 

Sounds good?

 

Michael

Posted
4 hours ago, mberneis said:

@jarr3,

 

Yes, this is definitley something which can be added easily. - I was thinking of adding it to the "Save and Add Matrix Functionality" Action.

See if there is an entry for Firebutton RGB and if so create the Firebutton MX accorging to your recipe. - Same with Flipper RGB

 

Sounds good?

 

Michael

Yes, would be amazing to have these "macros" activated by default, and if no one overwrite them with something specific, they just "flow" with the other non MX versions. Same color but additional functionality.

Are you one of the devs of the new DOF tools?

Posted
8 hours ago, mberneis said:

Yes, I am (the only)  dev on this new version. - Your enhancement request is now active in the latest version (0.5.5) 

Check it out and see if it works as you imagined. - Pls give me feedback through the feedback form at https://beta.configtool.vpuniverse.com/app/feedback

I can't keep up with so many threads going on at different platforms (vpuniverse, facebook, discord etc.)

 

Michael

 

Thanks @mberneis, it works but it does it only once, when I press save it already translates from "{Fire Button RGB} AT0 AL0 AW100 AH100" into "W16 Blink fu500 fd650 Cyan AT0 AL0 AW100 AH100".

We need to have it save with the template {Fire Button RGB}, so that each time someone changes Fire Button RGB, Fire Button MX will follow...

  • second request, it should be possible to save these template configurations to become static for all tables unless someone overwrite them completely. That is, that all new tables will have these static settings set, but they only generate when the main line is filled.
  • third request, if the configuration which the template point to does not exist, it should skip generating the config at all for that line.
    e.g. you have Fire Button MX defined as "{Fire Button RGB} AT0 AL0 AW100 AH100", there is no Fire Button RGB defined, therefore, the Fire Button MX should not be generated either. (edited)
  • 1 month later...
Posted
On 11/11/2024 at 11:04 PM, mberneis said:

Yes, I am (the only)  dev on this new version. - Your enhancement request is now active in the latest version (0.5.5) 

Check it out and see if it works as you imagined. - Pls give me feedback through the feedback form at https://beta.configtool.vpuniverse.com/app/feedback

I can't keep up with so many threads going on at different platforms (vpuniverse, facebook, discord etc.)

 

Michael

 

Hi Michael,

 

did you get any further on this? Is there something I can test?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
  • Create New...