I think,I shall clear my point.
It's not about Python documentation which is wonderful and clear, as there's a large community behind it.
It's about the ArchiCAD API's documentation which suks. They dont allow me to address the object directly, like in the Adobe InDesign's script. They force me to work through their API calls. OK, the only one thing I need to do is to change the text in a text box. Very well, they have the CreateText (element, memo); which is fine. And they have ChangeText (element); which is not. It doesn't allow me to change the text contents of the text box. Why?
You say, the documentation is ok. Well, I cant agree with that. All they do is address me to the C++ API documentation. Why not add a simple example code in the end? BTW, they did add it for some functions, to be honest. Like getSelectedElement which is very well documented. But I spent some hours to figure out if there is a way to change the text in a text box. No way. Why don't they just say: «we don't want you to change the text in a text box: you can create one, but not change».
It could've been more honest to make it clear first. Not to mention the strange behaviour: why can I create but cannot change
It's not about Python documentation which is wonderful and clear, as there's a large community behind it.
It's about the ArchiCAD API's documentation which suks. They dont allow me to address the object directly, like in the Adobe InDesign's script. They force me to work through their API calls. OK, the only one thing I need to do is to change the text in a text box. Very well, they have the CreateText (element, memo); which is fine. And they have ChangeText (element); which is not. It doesn't allow me to change the text contents of the text box. Why?
You say, the documentation is ok. Well, I cant agree with that. All they do is address me to the C++ API documentation. Why not add a simple example code in the end? BTW, they did add it for some functions, to be honest. Like getSelectedElement which is very well documented. But I spent some hours to figure out if there is a way to change the text in a text box. No way. Why don't they just say: «we don't want you to change the text in a text box: you can create one, but not change».
It could've been more honest to make it clear first. Not to mention the strange behaviour: why can I create but cannot change
poco2013 wrote:
IvanIvan wrote:I have been wondering that myself? The present version of Python is so limited as not to be useful except with properties and some navigator access. Definitely a step backward from the experimental version -- 23.
The reference is so obscure. Who do you target it for? There are no appropriate examples.
FYI:
24 has no capability to address text. I assume the backward scope was necessary because of the workload needed to reorganize the product. The next release of Python should tell if we are going to see some meaningful capabilities, as promised.
As to the examples, I have to disagree, The examples referenced (IMNSHO) do adequately demo the present functions of python 24. Documentation is fairly good, but you must be familiar with Python not Javascript. There are a huge number of Python videos on YouTube, so it would not make sense for Graphisoft to reproduce. Unfortunately there is not much you can do with the present version, which might lead to the confusion. The present version is only the ground work needed for future efforts. Very little functionality.
With the preliminaries out of the way (Good Base), the next update should tell us if Python in Archicad is intended as a future productive tool or is just marketing hype?
Didn't find the answer?
Check other topics in this Forum
Back to ForumRead the latest accepted solutions!
Accepted SolutionsStart a new conversation!
