i have seen, this is already realized in iRIdium Studio, but only for Feedback channels.

Please complete the next (latest) step, and make an auto-create also for Commands.

Thanks

Theo

ok!

Hi Jackie,

The only thing i can say: we discovered these problems also, when preparing the ISE2015. In that time the software was re-installed on the EVIKA (=Embedded Systems) server.

But now, we have the same problems with the OnBox we have already 7 months in our office: startup is very slow...

Theo

ok thanks for the feedback!

And what was the reason of the problem? License or OpenGL ???
Because we have same problems....

Dear Oksana,

What is the value of a Public Beta test, if YOU have to improve and testing SIP again???

We are thinking the SIP-driver IS already improved and tested by you, and is available for US to test now...

But this is not right, looking to your words? So, we have to wait again for a 'new and improved and tested' SIP-driver???

Thanks

Theo

Is it working now, Margolin Oleg?

For me:
Take the idea from Ivan, and make an option to disable Shift-Click.

Better is to make Shift-Click for multie-selection, like all other windows-based programs...

Thanks

Theo

Hi,

i know scripting is a very, very powerfull tool in iRidium and/or other systems.

But a 'normal' installer don't know anything about scripting; it's only 'to do' by programmers or IT-guys that are 'thinking in functions'. That are capable to create functions, modules, etc.

We need entry-level (low-level) functions for every low-level installer, without programming every 'simple' function (like a timer, schedules timer, logical expression, etc) in Javascript....

But: thanks for the uRL to your script; we will try/use it ;-) But i don't understand why it is not mentioned in this topic; that could save us time (and money)...

Thanks!

Theo

Hi,

This topic is 8 months 'under review'. And there are many, many topics 'under review', many of them > 4 months.

And many of these topics are voted with > 10 votes (for example, this topic).

I think it's a good idea to say: yes it's possible, and give a timeframe when it can be implemented. Or "Yes, we can do it, but not now".

Thanks

Theo