hexagon logo

Idea Center

All,

I posted a topic in the idea center. Has to do with adding a checkbox in the CONSTRUCTION dialog box for "USE .HIT DATA". If you use the ".numhits" or ".hit[1..blahblah] commands to hardcode features together, this will save you time (if Hex brings this to fruition).

Would appreciate it if all could take a look and consider using one of your votes to help advance this to the developers.




Thanks!
-Dan

https://hexagonmi.userecho.com/en/co...ed-to-hardcode




  • All,

    I posted a topic in the idea center. Has to do with adding a checkbox in the CONSTRUCTION dialog box for "USE .HIT DATA". If you use the ".numhits" or ".hit[1..blahblah] commands to hardcode features together, this will save you time (if Hex brings this to fruition).

    Would appreciate it if all could take a look and consider using one of your votes to help advance this to the developers.




    Thanks!
    -Dan

    https://hexagonmi.userecho.com/en/co...ed-to-hardcode




    {"alt":"Click image for larger version Name:\tCapture.JPG Views:\t0 Size:\t39.3 KB ID:\t484320","data-align":"none","data-attachmentid":"484320","data-size":"full"}


    What do you want to accomplish with this? I assume if you click .HIT data, it automatically creates the .hit[1..feature.numhits] so there is less manually typing? Or something else?


  • What do you want to accomplish with this? I assume if you click .HIT data, it automatically creates the .hit[1..feature.numhits] so there is less manually typing? Or something else?


    yes, exactly, automagically create the ".hit[1..feature.numhits]" thanks to a proposed "checkbox" inside of the CONSTRUCT dialogue box.
  • Thanks go throw me a like on the Idea Center! Slight smileSlight smileSlight smile


    What??? Likes here don't count?!?!?!

    To add to this idea, make it so the .HIT data doesn't count against characters used. Currently I can only add eight .HITS[1..NUMHITS.(FEATURE#)] so I have to create multiple constructed feature sets to get what I need profiled.


  • What??? Likes here don't count?!?!?!

    To add to this idea, make it so the .HIT data doesn't count against characters used. Currently I can only add eight .HITS[1..NUMHITS.(FEATURE#)] so I have to create multiple constructed feature sets to get what I need profiled.


    Totally agree, LINELENGTH errors have forced me to make some BIG featuresets in the past. I have one job where I combine 67 features, the hardcoding on that one was redonkulous

    No here doesn't really count, want the votes on idea center so MAYBE Hex will do this at some point before I retire =)
  • This is a nice idea , I assume we will still need to hard-code when we don't wish to iterate through the total number of hits? For example, on a circle with 20 hits we may wish to omit the first and last. Perhaps Hexagon can find a way to allow for point limits along with the checkbox that you propose...
  • This is a nice idea , I assume we will still need to hard-code when we don't wish to iterate through the total number of hits? For example, on a circle with 20 hits we may wish to omit the first and last. Perhaps Hexagon can find a way to allow for point limits along with the checkbox that you propose...


    Thanks! My suggestion executed as asked, yes a user would have to iterate through if they wanted to specify certain hits, but that could be easily resolved with a txt box tweak as well and make that a clickable task for the user


  • Totally agree, LINELENGTH errors have forced me to make some BIG featuresets in the past. I have one job where I combine 67 features, the hardcoding on that one was redonkulous

    No here doesn't really count, want the votes on idea center so MAYBE Hex will do this at some point before I retire =)


    I'm just glad I'm not the only person who considers redonkulous a word. Sunglasses


  • I'm just glad I'm not the only person who considers redonkulous a word. Sunglasses


    Webster who? Rolling eyes