

Isaac Harned
Member
Forum Replies Created
-
Isaac Harned
MemberOctober 26, 2022 at 5:00 pm in reply to: Isaac Harned – Here for forms with javascriptPoints: 8,282Rank: UC2 Brainery Purple Belt IIIThe struggle continues, Children layers do not want to activate and deactivate.
I have tried switching tactics by using substrings to try and match some of these values, using the dash as a placeholder for values before and after. I attempt to grab before the dash to match with the parent, and after the dash to determine if the applicable “NumberOfTaps” dropdown signals the layer to be on or off. Nothing seems to be working on this front
Now also having an issue where layers print settings turn off when I change the initState, even though these are set to “Use Default”. tried submitting this issue to Bluebeam, however they tell me they cannot provide assistance with custom code. I guess I must find a way to change the print setting for the layer as well. I have tried modifying the code so that it ONLY targets the initState, but this does not help.
There is also now a third array of OCGs, this is to turn off all children of parents that have been deactivated. This one is also having the same difficulty as the other loop targeting children layers.
I am getting no specific errors, except for the console displaying a single “false”
-
Isaac Harned
MemberOctober 24, 2022 at 1:28 pm in reply to: Isaac Harned – Here for forms with javascriptPoints: 8,282Rank: UC2 Brainery Purple Belt IIIHere is the latest update to the code and the file. Major thanks to Liz for all the help!
-
Points: 8,282Rank: UC2 Brainery Purple Belt III
Thank you David, and I will keep you guys posted on the Autosize!
-
Isaac Harned
MemberOctober 10, 2022 at 8:28 am in reply to: Isaac Harned – Here for forms with javascriptPoints: 8,282Rank: UC2 Brainery Purple Belt IIIThank you Troy!
-
Points: 8,282Rank: UC2 Brainery Purple Belt III
Thank you Troy!
-
Isaac Harned
MemberOctober 10, 2022 at 8:28 am in reply to: Isaac Harned – Here for forms with javascriptPoints: 8,282Rank: UC2 Brainery Purple Belt IIIThank you David, and I will keep you guys posted on the Autosize!
-
Points: 8,282Rank: UC2 Brainery Purple Belt III
Thank you so much for taking time Liz, You may just save the day on this one.
The “On blur” was actually a work around to make iPad feasible (no mouse, no mouse up), but that may not even be possible with the amount of layers. Testing to come on this.
I am going to add the scripts to the dropdowns today, will post back and let you know.
Regex in java may take me a bit to learn, but maybe some progress here by the end of week.
-
Isaac Harned
MemberOctober 10, 2022 at 8:27 am in reply to: Isaac Harned – Here for forms with javascriptPoints: 8,282Rank: UC2 Brainery Purple Belt IIIThank you so much for taking time Liz, You may just save the day on this one.
The “On blur” was actually a work around to make iPad feasible (no mouse, no mouse up), but that may not even be possible with the amount of layers. Testing to come on this.
I am going to add the scripts to the dropdowns today, will post back and let you know.
Regex in java may take me a bit to learn, but maybe some progress here by the end of week.
-
Points: 8,282Rank: UC2 Brainery Purple Belt III
I am actually making progress, once I get everything positioned right on the reduced page size and flatten the boxes, I am hopeful that will reduce a lot of the strain. Did a small test with the larger page size and it loaded pretty quick. I think the dropdown issue is not necessarily a coding problem, but hopefully the Engineering team can get back to me with some kind of answer.
I am now having a separate issue with form fields created in Revu 21. It seems the Auto text size is broken, and doesn’t fix itself when opened in Revu 20. Support tried telling me it only adjusts vertically NOT horizontally. Was pretty thrown off by that response, so I’m escalating.
-
Isaac Harned
MemberOctober 6, 2022 at 9:42 am in reply to: Isaac Harned – Here for forms with javascriptPoints: 8,282Rank: UC2 Brainery Purple Belt IIII am actually making progress, once I get everything positioned right on the reduced page size and flatten the boxes, I am hopeful that will reduce a lot of the strain. Did a small test with the larger page size and it loaded pretty quick. I think the dropdown issue is not necessarily a coding problem, but hopefully the Engineering team can get back to me with some kind of answer.
I am now having a separate issue with form fields created in Revu 21. It seems the Auto text size is broken, and doesn’t fix itself when opened in Revu 20. Support tried telling me it only adjusts vertically NOT horizontally. Was pretty thrown off by that response, so I’m escalating.