ezcontentobject_attribute saves ezselection-index in data_text

Previous topic

Suggestions

Next topic

Author	Message
Thomas Brandl	Thursday 25 September 2003 8:08:07 am data_int would be more appropriate
Paul Forsyth	Thursday 25 September 2003 8:37:57 am File it as a bug. If the index is only ever an integer (which it sounds like it is) then it should be stored in data_int. If we used this as part of the sdk it would cause problems as we would expect it to be an integer and get a string in return causing '==' operations to fail. paul
Thomas Brandl	Thursday 25 September 2003 8:46:52 am I will! I guess the index will always be an integer, since you can't define it for ezselection. Maybe it's not true for other datatypes which have an integer, but at least not for ezselection.

Author

Message

Thomas Brandl

Thursday 25 September 2003 8:08:07 am

data_int would be more appropriate

Paul Forsyth

Thursday 25 September 2003 8:37:57 am

File it as a bug. If the index is only ever an integer (which it sounds like it is) then it should be stored in data_int.

If we used this as part of the sdk it would cause problems as we would expect it to be an integer and get a string in return causing '==' operations to fail.

paul

Thomas Brandl

Thursday 25 September 2003 8:46:52 am

I will!
I guess the index will always be an integer, since you can't define it for ezselection. Maybe it's not true for other datatypes which have an integer, but at least not for ezselection.