Issue 76051 - copy not possible in database beamer
Summary: copy not possible in database beamer
Status: CONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
: 75354 (view as issue list)
Depends on:
Blocks:
 
Reported: 2007-04-03 12:33 UTC by marc.neumann
Modified: 2017-05-20 10:47 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description marc.neumann 2007-04-03 12:33:51 UTC
1. open a new document
2. open the database beamer (F4)
3. open any table
4. select any entry in a database field
==>> the COPY icon is disabled
==>> CTRL + C does also not work
Comment 1 Frank Schönheit 2007-04-03 14:27:45 UTC
accepting
Comment 2 Frank Schönheit 2007-09-05 14:22:33 UTC
*** Issue 75354 has been marked as a duplicate of this issue. ***
Comment 3 Frank Schönheit 2007-09-06 11:12:43 UTC
since copying is sometimes possible and sometimes not, here's a way how to get
into a *not working* situation reliably:
- display the table data of Bibliography/biblio
- set the focus into an arbitrary cell on the table data view (right hand
  side of the data source browser)
- press Cursor Down or Up to focus the cell above or below the current one
=> the copy slot is disabled, though it should be enabled, since the
   text in the cell is completely selected
Comment 4 Frank Schönheit 2007-09-06 11:21:12 UTC
fs->mba:
Basically, the slots are disabled since our code thinks that our frame (the
"beamer" frame) is inactive.
When focusing another cell as described in my previous comment, then we get *6*
frame action (XFrameActionListener::frameAction) events from the frame:
- 2 deactivation calls (FRAME_DEACTIVATING resp. FRAME_UI_DEACTIVATING)
- 2 activation calls (FRAME_ACTIVATED resp. FRAME_UI_ACTIVATED)
- 2 deactivation calls

Now the controller assumes that its frame is inactive, which in fact is wrong.

The stack of the last deactivation is as follows:
dbaui::SbaXDataBrowserController::frameAction(...)
dbaui::SbaTableQueryBrowser::frameAction(...)
framework::Frame::implts_sendFrameActionEvent(...)
framework::Frame::deactivate(...)
framework::Frame::setActiveFrame(...)
SfxViewFrame::MakeActive_Impl(...)
SfxTopWindow_Impl::Notify(...)
Window::Notify(...)
DockingWindow::Notify(...)
Window::Notify(...)

Note that the evenbeing notified here is a GETFOCUS event, for the cell control
getting the focus.

For some reason, SfxViewFrame::MakeActive_Impl decides to call a
setActiveFrame(NULL) at the XFrame belonging to SfxViewFrame::Current. Not sure
what this is good for, but that seems (to me) to be the reason for the "beamer"
frame being de-activated.
Comment 5 Mathias_Bauer 2008-01-11 10:14:18 UTC
target 3.x
Comment 6 Marcus 2017-05-20 10:47:45 UTC
Reset assigne to the default "issues@openoffice.apache.org".