Ticket #2238 (closed bug: obsolete)
scripts can't be run from link hud
Reported by: | danvisel | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | M12_RELEASE |
Component: | SCRIPTING | Version: | 2.0 |
Keywords: | Cc: | ||
Category: | unknown | Effort: | |
Importance: | Ticket_group: | ||
Estimated Number of Hours: | 0 | Add Hours to Ticket: | 0 |
Billable?: | yes | Total Hours: | 0 |
Analysis_owners: | danvisel | Design_owners: | deni |
Imp._owners: | deni | Test_owners: | |
Analysis_reviewers: | deni | Changelog: | |
Design_reviewers: | pap | Imp._reviewers: | pap |
Test_reviewers: | Analysis_score: | 5 | |
Design_score: | 4 | Imp._score: | 4 |
Test_score: | 0 |
Description
- Make a new book.
- Add a new script - write your own or import one.
- Add a frame to the page.
- Open the frame's link HUD, add a link that "on mouse pressed" "run script".
The drop-down script menu has nothing in it that can be selected. This is true of both frame-based links and text-based links.
Attachments
Change History
comment:1 Changed 15 years ago by danvisel
- Status changed from new to s1b_analysis_finished
- Analysis_owners set to danvisel
comment:3 Changed 15 years ago by deni
- Design_owners set to deni
- Status changed from s1b_analysis_finished to s2a_design_started
- Imp._owners set to deni
- Analysis_reviewers set to deni
- Analysis_score changed from 0 to 5
comment:4 Changed 15 years ago by deni
- Status changed from s2a_design_started to s3b_implementation_finished
- In RunScriptConfigurationPanel :
- Use AppViewUtil.getCurrentBookDocView(this) instead of findParentElement(BookDocView.class) to find the responsible BookDocView.
- When searching for the selected script, take into account that the ResourceRefs link actions hold are relative from the link holder. Otherwise, when you create a link rule 'MOUSE RELEASED - Run Script A', the next time you select this rule as current, you will not see the script name (although in the model it will be correct).
- In ON_RUN_SCRIPT_ACTION operation in RunScriptLogic use the access parameter of the event, instead of the ResourceView context. Otherwise, 'Run script...' actions will not work for text links.
Note: See
TracTickets for help on using
tickets.