I'm trying (actively) to repair the broken 'Auto Flow-Label' setting before integrating the new Flow-Labels into the existing architecture. SInce I won't be removing anything just yet, it would be a bit sloppy to continue adding on top of something that needs fixing.
Unfortunately, whatever broke the 'Productivity' setting that automatically creates Flow-Labels with Constraints & Connections, has been an elusive adversary. I just spent the last 2 days of development attempting to isolate & repair that issue. This last sprint was my third attempt to fix it. There's so much legacy source code and logical bloating in that system, I can't even believe it still works.
As I'm searching for the cause of the issue, I'm also refactoring the code to make the whole system (Flow-Labels) run a little more efficiently, without changing the data-flow or signatures of any functions. I'm getting too technical. Sorry...
I'd just really like to resolve this 'Productivity' issue before the next update goes out, which needs to be before the end of April.
I'll keep you and other interested parties in-the loop. After it's resolved I'll probably be so happy that I'll email you immediately! 😁
That's been a known issue for a while, but it doesn't look like it got published. Sorry for the oversight. I'll add that ASAP. However, here's what happened...
After we changed the database schema for the Design Markers and Paving system, we discovered the Flow Labels productivity setting wasn't compatible. We tried to fix it, but it turned out to be far more complex than we anticipated. Restoring that functionality is going to be next to impossible moving forward.
Our recommendation is to just turn that setting off. It'll do nothing but cause you problems. In the next update, it'll be gone anyway.
The brighter side though is that we're going to replace that functionality altogether. You won't miss the productivity setting after the new feature is in-place.
Hi Chris,
I'm trying (actively) to repair the broken 'Auto Flow-Label' setting before integrating the new Flow-Labels into the existing architecture. SInce I won't be removing anything just yet, it would be a bit sloppy to continue adding on top of something that needs fixing.
Unfortunately, whatever broke the 'Productivity' setting that automatically creates Flow-Labels with Constraints & Connections, has been an elusive adversary. I just spent the last 2 days of development attempting to isolate & repair that issue. This last sprint was my third attempt to fix it. There's so much legacy source code and logical bloating in that system, I can't even believe it still works.
As I'm searching for the cause of the issue, I'm also refactoring the code to make the whole system (Flow-Labels) run a little more efficiently, without changing the data-flow or signatures of any functions. I'm getting too technical. Sorry...
I'd just really like to resolve this 'Productivity' issue before the next update goes out, which needs to be before the end of April.
I'll keep you and other interested parties in-the loop. After it's resolved I'll probably be so happy that I'll email you immediately! 😁
Nick
Any word on the New Feature to replace Auto Flow Labels?
That's been a known issue for a while, but it doesn't look like it got published. Sorry for the oversight. I'll add that ASAP. However, here's what happened...
After we changed the database schema for the Design Markers and Paving system, we discovered the Flow Labels productivity setting wasn't compatible. We tried to fix it, but it turned out to be far more complex than we anticipated. Restoring that functionality is going to be next to impossible moving forward.
Our recommendation is to just turn that setting off. It'll do nothing but cause you problems. In the next update, it'll be gone anyway.
The brighter side though is that we're going to replace that functionality altogether. You won't miss the productivity setting after the new feature is in-place.
-Nick