Hi Vladimir

It seems to be something to do with the scripting perhaps corrupting or something

I have done more testing:

- reinstalled 1.0.7

- run an old project from backups (installed on a client site and working happily)

1. crashes in i3 32 bit

2. start i3 64 bit, no crashing

2. it uses a script to change popups. Put in a line of logging to see where it might be crashing, run iRidium 32bit, no crashing

see video here: https://www.dropbox.com/s/npvhz5bj3qce8ul/32%20bit%20crashing.wmv?dl=0

- new project,

- script to show page, based on same code as above, copied and pasted script, crashes without logging.

- change the script, remove lines or add lines, and crashing stops.

Sending both projects projects to support@iridium email

It seems to be older iridium version projects scripts crash and new projects, exactly the same, made in 1.0.7 do not. I have a project I have been working on, nothing changed, opened in 1.0.7 after installing 1.0.7 and now crashes in 32bit.

We have this issue in other projects upgraded to 1.0.7, completely different projects with different scripts.

In this example, the inclusion of the *.h & *.cpp file in this example is for Mac's, and the dll for Windows.

So yes, the resultant project would be platform specific.

There are other examples of platform specific features in iRidium, such as IR.Execute.

Interesting. I have not used VNC on iPads, just windows PC's. Which VNC are you using? I use RealVNC. Perhaps try the VNC forums :)

Yes, add files to a project, like a dll so it can be used from iRidium.exe or iRidium server.

For COM integrations or other library integrations, there can be a DLL or as per the example above a header and a cpp file.

Hi

The protocol behind VNC does not work if the screen to be controlled has a full-screen app

Solution: Reduce the size of the iRidium app by 1 pixel, eg instead of 1024x768 change to 1023x768. You will not be able to see the difference and VNC will work :)

What about inverted states, or when it is not on or off, but true of false, or open or closed?

When is this going to be looked at?

Eg, a server project with 3 x AV receivers, lighting, global cache, a fire, and alarm system, blinds....

With so many this becomes almost unusable in the client, as all the commands / feedbacks are thrown into one huge iRidum server driver, making it very difficult to find anything.

Please at the very least, organise the commands / feedback for each drivers into FOLDERS under the iRidium Server driver.

Thanks

Hi Mike

I raised this as an issue some time ago, but cannot find it now. For iRidium to save a project token, the app must be closed, as the saving of tokens does not happen till then.

We use Windows Scheduler to power cycle a PC once a week, and then in iRidium, using schedule to close iRidium at the appropriate time. See attached project :) CloseiRidiumSchedule V1.irpz

cheers

glad you found a solution :)

In your project do you have 'Always on top' ticked? If so this may conflict with the keyboard trying to go on top

Alternative to Full Screen:

I set the landscape width and height eg to 1023 x 768, instead of 1024 x 768 as one pixel less than full screen allows VNC and TeamViewer to behave well (neither operates well with any application that has full resolution, and you cannot see one pixel difference) and then also custom position of 0,0. Leave 'Aways on top' unticked, this is only required in a kiosk situation.

cheers