Like could we move up and down triggers like we do with gauges. Asking for this request so I can organize triggers. Actions would be nice too.
Sometimes I make a trigger or action only to expand on it later and it gets disorganized.
Secondly any way to expire export triggers to an XML? That way if we want to code triggers in XML like we do for animation triggers it might be easier for some of us.
Also lastly can we have an option to move triggers between a dash and global triggers?
I assume an XML file import/export would gelp produce all of the above.
You position yourself as a developer who listens to the opinion of the community. So when will you be able to do the basic thing that will make life much easier for the skin-creator?
This devs honestly do a good job at keeping up. Yes, sometimes things get pushed back, but that happens to any projects. If you like me want something worked on sooner, either keep the post alive and as the dev said, ask nicely.
Btw @realdashdev I just came back from a hiatus away from the forum and definetly could use some help on a different issue.
Now that I’m back, I would like to get back to this. I’ve recently done a lot of javascprit lately and was wondering if you guys will ever push a way to code for triggers and actions a lot faster.
I know you guys use XML for animation triggers, but is there any chance of doing import/export of XML or other format for ALL triggers?
I would really like to code triggers and actions on my computer. Then from their upload them to my RealDash and test from there.
It’s just so problamatic sometimes to do so from within the app. Don’t get me wrong, the setup is nice for a few triggers here and there but I want to expand on my system and make it a lot more complex espeically with a lot more speak text. I want to make custom warnings for a lot of stuff and to edit it within the app sometimes is problamatic if I need to go back and fix something. For example, a typo in text there’s no way to replace just a single word. I’d have to delete the whole thing.
Another issue I’m starting to run into is that some of these triggers I now want on a global scale. That way they work for all my future dash designs, not just the one. So being able to import and export trigger and action files to both global and standard would be nice.
Could you guys push this up, please and thank you.
Also, I don’t know if this was checked but I mentioned it before, you guys stated triggers and actions won’t work if multiple names. But Ive had animations give multiple of the same name and they worked fine. I don’t believe this is intentional on your guys part, but obviously it contradicts what you’ve told me in the past. If you can look into that as well please.
Actions should have unique name. When trigger fires, it just looks for a first action with specified name. If you have multiple actions with same name, others will not be fired. Even if it seems to work, you should follow the rule of all actions having an unique name.
I would do an export/import for triggers and actions if it was an easy task. Currently triggers use a lot of internal id numbers that would be next to impossible to enter by hand on a text editor. Of course this could be changed, but to my honest opinion the entire trigger-action system would need to be rewritten as currently it allows too easy of misuse and confusion.
Let me remind you all that entire editing system on RealDash was not meant to be public at all. Its developed to be our internal quick-and-dirty editing tool, when oddities some some extra laboursome is not an issue. Actually I was pushed internally to release the editing for everyone, I never wanted to do that.
I think we can all agree now, that it was a good thing that I was pushed to publish the dashboard editing for everyone. Even knowing that it will cause frustrations/poor reviews from the users.
Alright, back to the issue. Currently Global Triggers and Actions can be exported/imported with vehicle settings in the Garage. If you make some global triggers and actions, go to the garage and export the settings, you can see that the format of triggers and actions in XML is not edit-friendly. I could relatively easily add an similar export/import XML for dash triggers and actions but I believe it really does not solve the actual issue, which is easy misuse and overcomplication that comes with triggers and actions.
At least that way I can transfer triggers and actions to the global side without full on manually recreating them. Then from there I can simply delete and save as necessary. @realdashdev please
I haven’t seen the format of global triggers but definitely would like to see how they look once exported.
So far animation triggers and actions weren’t too bad imo
Edit:
Also triggers use internal IDs, is there any way to use pointers to them? Like names to point to the internal IDs without disclosing exactly what the IDs are
Also I don’t believe the dashboard editing is an issue.
I say that is more user end. People want to edit but don’t realize you need some photoshop skills to do so. That, a bit of math for angles and finding out measurements per se to do a dash.
From there triggers and actions aren’t as bad either, just a pain when you want to create multiple.
And I guess the most headache would be the more advanced stuff like can bus decoding. But again, that’s not at fault of you guys, it’s a huge fault of how cars are developed and what data they want to show easily.
I would much rather discuss why someone may need ‘thousands’ of triggers for a dashboard. In our most complex premium dashboards trigger count is about 30-40, so this makes me feel that either trigger system is grossly misused, or there is some sort of a use-case that we do not fully understand and which forces to use multiple triggers to achieve one thing.
Yeah most I think are speak text actions based on triggers conditions.
below operating temperature
at or above operating temperature
temperature hitting hot
temperature critically hot
change in heading
time notification every 30 min
low gas
different warning message after x amount of low gas messages
eco mode
sports mode
obd2 disconnect while driving
obd2/start up
service reminder, different stages
brightness control based on time, this worked on my tablet not on my PI
Edit: there’s so many more I plan to add, and for the most part when they work they do. Memory wise I’ve never had issues on 4 gb.
Sone I used to have a few, ex would be speak time. But I’ve reduced reduced it down to 4.
I always do can I make it work, okay it’s working. How can I simplify this and clean it up.
Sometimes I go back and add something extra that’s part of a group of triggers. This one is a bit why I want to move triggers and actions around. As I don’t always remember the names and I know the trigger I’m looking for is around the rest.