Development Open House

Note: The following catalog of content covered in this webinar is time stamped to allow you to follow along or skip to sections of the video that are relevant to your questions. You can also search for content on this page using the FIND command in your browser (CTRL + F in Windows, Command + F in Mac OS.)

• Intro/TOC
• How a Wishlist Becomes a Feature
• Tentative Production Schedule for 2022
• Show Off Some Features Under Construction
• Suggestions, Ideas, and Wishlists

0:00 – 3:39: Intro/TOC

3:40 – 25:09: How a Wishlist Becomes a Feature

• Step 1: User suggests a feature
• Step 2: Wishlist is filed and prioritized
• Step 3: Clarifying requests, assessing viability
• Step 4: Monthly development meeting sets priorities
• Step 5: Feature is coded
• Step 6: Determine whether feature is done or not
• Step 7: Test, test, test
• Step 8: Screenshot and document
• Step 9: Celebrate when a user appreciates

Tracing through an actual feature's history (example: Reference Note Stadium callout style) (12:54)

• Step 1: Analyze what's there
• Step 2: Update two dialog boxes, freshening hundreds of lines of code, just to get ready
• Step 3: Write the actual code
• Final step: Power Tip video

Side note: Why the RefNote callout box isn't a block (21:54)

25:10 – 30:11: Tentative Production Schedule for 2022

• Update all schedules
• Multiple detail references
• Native Unicode support
• Switch all callouts to MLeaders
• Native metric irrigation calculations
• Material/color picker for amenities
• Planting F/X for Revit
• Update Grading tools
• Revise all hatch libraries
• Advanced "MIRV" Nuke

30:12 – 40:10: Show Off Some Features Under Construction

• Stadium style RefNote callout (30:42)
• Overhauled True Color system and Site Color tool (31:52)
• Updated Irrigation Schedule (34:54)

Question: Will the new table schedule style fix the issue where if a description is is too long an it wraps the unit of measure to the next line? (38:24)

Answer: Yes it will!

40:11 – end: Suggestions, Ideas, and Wishlists

Discussion about the orange "Infection detected" dialog box and why it's necessary (41:00)

Question: Any chance that assigning emitter by plant rather than container is in development? (44:24)

Answer: We've been looking at implementing this option, although it will cause the plant list to be excessively long. Also note that we originally designed emitters to be assigned by container to ensure the plan is clear for the contractor.

It's always a good idea to post your feature requests on our community forum. If other users chime in and say it's a good idea, we may be more likely to make it a priority. (50:07)