Welcome!On this forum you can discuss iRidium with other users. iRidium consist of 2 main components - i3 pro app and iRidium Server. Please post here your questions, ideas or errors you find.
Please send your questions to support team as a private messages.
It would be great to have a similar property to Wrap Text in a Button item called Scroll Text. When this is enabled and the length of the text exceeds the size of the button then the text becomes scrollable.
It has been implemented from iRidium Studio 220.127.116.1111 (beta)
I think it's a good idea to have the function to rotate items in the editor.
Another idea is that you can draw circles without using the circle borders because the borders have a limitation in size.
I think this will give the editor users more possibilities to draw unique interfaces.
It would be nice if he had on option to print all the Command and Feedback variables including their Properties.
This way when you created hundreds of Variables you print them on paper or print them to a "file format" to be able to check if all your varibales are correct.
Because they would be all underneath each other it would be easy to find "typos" or other mistakes.
Now it is quite difficult to click trough every variable and check every value.
Some thing like this:
Light_DimValue_B1 / REAL / R / 500
Light_A1 / Bool / R / 100.0
Light_A2 / Bool / R / 100.1
Light_A3 / Bool / R / 100.2
Light_DimValue_B1 / REAL / R / 600
Return_Status_Light_A1 / Bool / R / 200.0
Return_Status_Light_A2 / Bool / R / 200.1
When installer scan the Domintell-bus, the description from the Domintell-commands and feedbacks are NOT imported in the GUI Editor.
The installer has to manually edit all descriptions of commands and feedbacks, and this take lot of time.
Please improve the scanning of Domintell-bus, so the names of the commands and feedbacks are displayed correct in the Project Device Tree.
In Domintell, now the installer has to go to the project to scan the Domintell-bus (connect the laptop to the installation and scan with the GUI Editor). This is not convinient.
Please add an option to import the DAP-files from Domintell directly in the GUI-editor, so the installer don't have to drive to the house of the end-user to scan the Domintell-bus.
Please vote to use Timelimit in all clients instead of Trials!
As I see about half of newcomers (optimistic) give up on iRidium after first try. Too complex. Same goes to beta test - I've spent whole morning today, trying to get HWIDs, licenses etc. for new devices.
Trial is used to develop and test. It is better to set Timelimit instead of Trials.
I think that all Client apps and Emulator should work for, let's say 20 minutes after run, than need to close/open or press a "continue" button.
This will make it a lot easier to start using iRidium for newcomers.
It has been implemented from i3 pro 18.104.22.16803 (beta). Test Mode (20 minutes) is supported for integrators with "Full Registration".
In a client project, iRidiium server combines all commands and feedbacks into one big driver.
In my current project with 6x Global Caches, 2 x Integras, Full Lighting, alarm system and MRA, this makes up to 1000 commands all in one long list.
To top it off, the commands/feedback are ordered by the order they were synched, so the commands/feedback may not be anywhere near the rest of the commands/feedback for that driver.
This makes it very slow going and frustrating to find what I want
The search at the top does not make it any faster.
Please Please Please
1. enable separate server drivers in the client, connecting to iRidium server on different ports (the way iRidium Gate works)
2. Add folders to iRidium Server in the client, matching the name of the drivers. Making it much easier and faster to find commands
It is required to limit the volume of the Backup folder or the time for storing backup copies. I found a folder with backup files for 18GB. And I checked only one project.
Customer support service by UserEcho