| 00:00.33 | mpictor | ...but can't you pass that value to measure_value, then use the measure_value whereever you need it? |
| 00:03.57 | mpictor | btw, instead of ObjCreate, you can use config_control_design::t_measure_value->NewSTEPentity() |
| 00:04.15 | mpictor | then set the entity's eDesc to t_measure_value |
| 00:05.04 | starseeker | ah - so that might let me create a plane_angle_measure? |
| 00:05.33 | mpictor | one sec |
| 00:05.41 | starseeker | I can pass it to measure_value, but I can't assign the type of the measure valeu to plane_angle_measure |
| 00:05.51 | starseeker | I think it writes out MASS_MEASURE by default... |
| 00:05.52 | starseeker | sure |
| 00:11.55 | mpictor | I'm not sure what you need to do :/ |
| 00:12.16 | mpictor | I was looking at the code from a smaller schema, and it looked straightforward |
| 00:13.08 | mpictor | but with measure_value, there are several types that map to SDAI_Real and it has one constructor for all of those |
| 00:15.38 | mpictor | ohhh |
| 00:17.03 | mpictor | nevermind. I was going to suggest SdaiMeasure_value::AssignEntity, but it just prints a warning |
| 00:17.30 | mpictor | wonders what inherits from SdaiMeasure_value |
| 00:19.09 | mpictor | just remembered... two classes are generated for SELECTs |
| 00:20.03 | mpictor | SdaiMeasure_value_agg inherits SelectAggregate |
| 00:20.55 | starseeker | dunno about inheriting - the thing I was working on in that exporter used it, but I don't think it inherited |
| 00:21.31 | starseeker | there doesn't seem to be a lot of documentation on SDAI_Select and how it does or doesn't relate to the application instances |
| 00:22.43 | starseeker | the constructor for SdaiMeasure_value seems to insist on a SelectTypeDescriptor - so far I haven't found any way to use a regular TypeDescriptor... |
| 00:23.14 | mpictor | SdaiMeasure_value has a SelectTypeDescriptor |
| 00:23.19 | mpictor | t_measure_value |
| 00:23.40 | starseeker | right - if I use that, STEPwrite ends up using MASS_MEASURE instead of PLANE_ANGLE_MEASURE |
| 00:24.18 | starseeker | I was wondering if plane_angle_measure is supposed to be of type t_measure_value or something like that |
| 00:24.32 | mpictor | when an SdaiMeasure_value_agg (or other SelectAggregate) is read, a SelectNode is added to it |
| 00:24.45 | mpictor | I don't think so |
| 00:25.02 | mpictor | I think *_agg is the key... just haven't figured out how yet |
| 00:26.13 | mpictor | I'll see if I can create a file with a valid instance of a select, then step through with a debugger |
| 00:30.15 | starseeker | mpictor: cool - thanks! |
| 00:31.29 | starseeker | fwiw, I'm trying to re-create #170 in this file: http://www.steptools.com/support/stdev_docs/stpfiles/ap203/block.stp |
| 00:33.08 | starseeker | I can make the Plane_angle_measure_with_unit without too much trouble, and I can create the STEPcomplex for the #172 bit, but apperently the plane_angle_measure is a required piece (grr...) |
| 00:38.18 | mpictor | wait a minute... have you tried SdaiMeasure_value::SetUnderlyingType()? |
| 00:38.29 | mpictor | it takes an entityDescriptor |
| 00:38.42 | mpictor | TypeDescriptor, I mean |
| 00:40.53 | mpictor | create an SdaiMeasure_value with t_measure_value for the SelectTypeDescriptor, then call its SetUnderlyingType method with t_plane_angle_measure |
| 00:51.55 | mpictor | haven't tried it, but I think this would work: http://pastebin.com/MSrP3X2G |
| 00:52.32 | mpictor | seems strange to assign a value and *then* set the type |
| 00:53.49 | mpictor | I suppose it would be best to rename p_ang_meas to reduce confusion - p_ang_meas_select ? |
| 00:56.43 | mpictor | but you need plane_angle_measure_with_unit... |
| 01:03.30 | mpictor | is calling it a night. I'll see what I can figure out in the morning |
| 11:39.17 | *** join/#stepcode mpictor (~mark@2601:d:b280:b5:d63d:7eff:fe2d:2505) |
| 17:37.34 | *** join/#stepcode mpictor (~mark@2601:d:b280:b5:d63d:7eff:fe2d:2505) |
| 19:10.43 | *** join/#stepcode kesha_ (~kesha@117.226.220.34) |
| 19:33.20 | kesha_ | mpictor: https://github.com/stepcode/stepcode/blob/ks/headers/include/CMakeLists.txt#L38 https://github.com/stepcode/stepcode/blob/ks/headers/include/CMakeLists.txt#L39 .. are these at right locations ? |
| 19:33.31 | kesha_ | or they need to be in include/stepcode ? |
| 20:10.43 | mpictor | kesha_: sorry I missed you |
| 20:10.54 | mpictor | I'll comment on the commits |
| 20:16.47 | mpictor | starseeker: (or brlcad) do you know why cmake vars like ${LIBSTEPEDITOR_PRIVATE_HDRS} are named as private? |
| 20:17.28 | mpictor | going through kesha_'s commits and noticed that |
| 21:01.35 | *** join/#stepcode kesha__ (~kesha@117.226.220.34) |
| 21:07.35 | *** join/#stepcode kesha__ (~kesha@117.226.220.34) |
| 21:09.46 | starseeker | mpictor: not really - when I did the original CMake build, it wasn't immediately clear to me which pieces would need to be in a system installed stepcode |
| 21:09.57 | starseeker | still isn't, for that matter... |
| 21:10.21 | starseeker | has always thought the SCL code design was a bit odd and intertwined... |
| 21:12.25 | mpictor | ok |
| 21:12.46 | mpictor | yea it isn't organized very well |
| 21:13.14 | mpictor | much better now than it originally was though! :O |
| 21:14.33 | mpictor | I see you're making more progress |
| 21:15.04 | mpictor | hi kesha__ |
| 21:16.07 | mpictor | bye kesha__ |
| 21:16.48 | mpictor | I tried to use andChat on my android phone, but it often fails to connect or disconnects |
| 21:16.59 | mpictor | I think kehsa__ has tried it as well |
| 21:34.35 | *** join/#stepcode kesha_ (~kesha@117.226.220.34) |
| 22:16.29 | *** join/#stepcode kesha_ (~kesha@117.226.220.34) |
| 22:30.58 | *** join/#stepcode kesha_ (~kesha@117.226.220.34) |
| 22:44.43 | *** join/#stepcode kesha_ (~kesha@117.226.220.34) |
| 22:58.18 | *** join/#stepcode kesha_ (~kesha@117.226.220.34) |
| 23:02.17 | mpictor | kesha_: I made two comments on github, and spoke with starseeker. Go ahead and rename the variables that you use that contain _PRIVATE_. |
| 23:02.40 | mpictor | LIBSTEPEDITOR_PRIVATE_HDRS -> LIBSTEPEDITOR_HDRS, for example |
| 23:11.17 | *** join/#stepcode kesha_ (~kesha@117.226.220.34) |
| 23:13.59 | *** join/#stepcode kesha_ (~kesha@117.226.220.34) |