Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Pull scanner properties out into ScannerModel separate from MainModel.

#32

Scanner properties should be migrated into a ScannerModel, which is managed by MainModel in the same way that PageModel is managed by DocumentModel. Individual scanners will each have a ScannerModel and the one being observed (the 'active_scanner') will be switched on by the MainController.

This will allow for much cleaner and more natural setting of property states on the hardware and hopefully eliminate some of the cruft in the MainModel's property setters.

(Keep in mind that the active scanner will need to be explicitly opened in closed if the device is to remain available to other applications while not in use by NoStaples.)

Reported by onyxfish · March 5th, 2009 @ 10:21 PM

State: resolved
Milestone: 0.5
Assigned to: onyxfish onyxfish

Activity

  1. onyxfish
    onyxfish
    • State changed from new to open

    March 5th, 2009 @ 10:21 PM

  2. onyxfish
    onyxfish
    • State changed from open to resolved

    On further review, this doesn't turn out to be sensible. SANE's notion of a scanner is something which only maintains state when it is open. Each time a fresh device list is queried all previous device states are lost. The fallout of this is that any attempt to wrap devices is going to require a huge amount of arm-twisting to keep the state objects in sync with the SANE objects. Rather than deal with this, I've elected to stick with the "one state for all devices" model and I've cleaned up the logic in MainModel so that I can mor easily trace the process of selecting devices.

    March 6th, 2009 @ 09:14 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.