fire command handler on replacement tab when a tab is closed

Bug #1089501 reported by Jason Etheridge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Low
Unassigned

Bug Description

Minor bug, and I'll come back to it eventually unless someone gets an itch to work on it before then.

Top-level tabs in the staff client have a handler for command events that
1) ensure that the tab is visible
2) set the help context for the UI within the tab
3) call the default_focus function for the UI within the tab if it exists

You can see this in action opening an Item Status interface, then opening a new tab, and switching back to the tab with the Item Status interface. The input focus will move from wherever it was back to the textbox in the Item Status interface, by virtue of the default_focus function.

However, let's say you have an Item Status interface in tab 2, and you're currently doing something in tab 1, and then close tab 1. Tab 2 will become visible, but its default_focus function will not be called, and the input focus will be left in limbo.

This is more important to me because I want to load extra stuff into the default_focus function for readying an interface for integration with 3rd party products that essentially script the staff client.

Tags: fixedinwebby
Revision history for this message
Jason Stephenson (jstephenson) wrote :

When you have such a powerful API available, "products that essentially script the staff client" seems about the most wrong way to do anything.

Changed in evergreen:
status: New → Triaged
importance: Undecided → Wishlist
importance: Wishlist → Low
Revision history for this message
Jason Etheridge (phasefx) wrote : Re: [Bug 1089501] [NEW] fire command handler on replacement tab when a tab is closed

Yeah, scripting the staff client might be overstating it, though I
know there are book vendors out there that do just that. In this
case, it'll be the staff client using someone else's API for RFID.
That'll get a different lp ticket. :)

On 12/13/12, Jason Stephenson <email address hidden> wrote:
> When you have such a powerful API available, "products that essentially
> script the staff client" seems about the most wrong way to do anything.
>
> ** Changed in: evergreen
> Status: New => Triaged
>
> ** Changed in: evergreen
> Importance: Undecided => Wishlist
>
> ** Changed in: evergreen
> Importance: Wishlist => Low
>
> --
> You received this bug notification because you are a member of Evergreen
> Bug Wranglers, which is subscribed to Evergreen.
> https://bugs.launchpad.net/bugs/1089501
>
> Title:
> fire command handler on replacement tab when a tab is closed
>
> Status in Evergreen - Open ILS:
> Triaged
>
> Bug description:
> Minor bug, and I'll come back to it eventually unless someone gets an
> itch to work on it before then.
>
> Top-level tabs in the staff client have a handler for command events that
> 1) ensure that the tab is visible
> 2) set the help context for the UI within the tab
> 3) call the default_focus function for the UI within the tab if it exists
>
> You can see this in action opening an Item Status interface, then
> opening a new tab, and switching back to the tab with the Item Status
> interface. The input focus will move from wherever it was back to the
> textbox in the Item Status interface, by virtue of the default_focus
> function.
>
> However, let's say you have an Item Status interface in tab 2, and
> you're currently doing something in tab 1, and then close tab 1. Tab
> 2 will become visible, but its default_focus function will not be
> called, and the input focus will be left in limbo.
>
> This is more important to me because I want to load extra stuff into
> the default_focus function for readying an interface for integration
> with 3rd party products that essentially script the staff client.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1089501/+subscriptions
>

--
Sent from my mobile device

Jason

Elaine Hardy (ehardy)
tags: added: fixedinwebby
Changed in evergreen:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.