Suggestion for next version

I agree that this could be quite handy. It has been added to our system as issue #13193

 

I am not sure exactly what you mean by this. Can you give an example of the sort of thing you want to be able to do ?

The Pascal logic engine is not object oriented.

 

The best example I can think of at present is the new security command interface. If I could inherit the functions directly, I could override the methods etc and create my own. This would mean that interfacing to other none supported systems could be done easily and only require a single programme. All you would need to do is add in the correct function set.

Im sure this could be applied to other areas such as audio, hvac or irrigation where direct communication with non cbus hardware is achieved using RS232 or eth.

However, as you say, its not object oriented so not too sure how this could be done.

 

Verify continued

Would this also verify the toolkit project changes as well????

 

development module(s)

Sorry to keep flogging this thread to death BUT....

It would be really nice to add a check box next to each module to enable it to run (and unchecked not to run), so if a module is 'under construction' or needs some research, we can transfer any other changes which have been made in the session to the CTC / PAC.

Or possibly a module group called "development world" where any module which is being edited, or not yet been compiled. can be kept within the PICED software and not transferred to the unit.

WHY...

At present, if you compile a module that has an error, you cannot transfer to the unit (i think, but either way you get error messages). and if you have made various changes to several modules in the session and only one has an error you do not have time to correct, before transferring to the unit, you can rest safe in the thought the logic engine is not trying to run some 'buggy' code.

This would also ease the my mind and the minds of other installers who may be pestered by end users as to "unusual behavior since you were last here", and them questioning themselves as there is a bit of code not functioning quite as they would like.

BTW the workaround i currently use is to cut the text out of the logic editor into word or notepad, until it works.

Just another 2 cents worth...

Thanks

Grant

 

development module(s)

Sorry to keep flogging this thread to death BUT....

It would be really nice to add a check box next to each module to enable it to run (and unchecked not to run), so if a module is 'under construction' or needs some research, we can transfer any other changes which have been made in the session to the CTC / PAC.

Or possibly a module group called "development world" where any module which is being edited, or not yet been compiled. can be kept within the PICED software and not transferred to the unit.

WHY...

At present, if you compile a module that has an error, you cannot transfer to the unit (i think, but either way you get error messages). and if you have made various changes to several modules in the session and only one has an error but you do not have time to correct it, before transferring to the unit, you simply disable it and rest safe in the thought the logic engine is not trying to run some 'buggy' code.

This would also ease the my mind and the minds of other installers who may be pestered by end users as to "unusual behavior since you were last here", and them questioning themselves as there is a bit of code not functioning quite as they would like.

BTW the workaround i currently use is to cut the text out of the logic editor into word or notepad, until it works.

Just another 2 cents worth...

Thanks

Grant