Book a Demo

Author Topic: Shapescript flame  (Read 2888 times)

beginner

  • Guest
Shapescript flame
« on: August 25, 2010, 08:42:12 pm »
Why is it that each concept in EA is different to others? There is a crude Transformation macro language which complies to nothing. Then you have an API which offers quite some, but not all possibilities of manual intervention. And there is ShapeScript which obviously was designed by some ancient Pascal freak (or one of its relatives). Well, it's nice to have shapescript at all. But why can't it be integrated with the rest? I can't hook my own scripts to display/draw elements based on "external" computation. Then you don't have access to elementary things. I was looking for the parent to display that like for "normal" classes in italic. But you can't get that. Classifier looked like what I needed but it yields nothing. Then, why is there a plain classifier and a couple of dotted ones? Why aren't these properties described at all??? I'm not very good in guessing. Further: when I have a tagged value with Classifier this scrappy thing yields the GUID, not the name. How meaningful!!!

Oh yes my dear. The steak was wonderful. Especially the part between the burned and the raw meat.

b.

P.S. I forgot: no possibility to change fonts?!
« Last Edit: August 25, 2010, 08:50:10 pm by beginner »