BUG report - Inconsistent IR settings in Builder

Apex 4.0.2
Most of the reports used in the App Builder have been converted to use Interactive reports which is great. But I find that the IR settings are not consistent across all the reports. I had reported this during the tryapexnow.com beta phase. Now that we can use the new apex_application_install API to load up the Builder apps into our own workpace so we can review how they are built, the Region Utilities > Update Interactive Report Settings page shows this. Or just run the query
select
page_id, name, allow_save_rpt_public, show_finder_drop_down, show_display_row_count, show_search_bar, show_search_textbox, show_actions_menu, show_select_columns, show_rows_per_page, show_filter, show_sort, show_control_break, show_highlight, show_computation, show_aggregate, show_chart, show_notify, show_group_by, show_calendar, show_flashback, show_reset, show_download, show_help
from apex_040000.wwv_flow_worksheets
where flow_id=4000My main annoyance is the "Save Report Public" checkbox. The IR saved report list shouldn't be cluttered with all the report settings saved by all the workspace developers.

Please submit an official bug report to Adobe at:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Alexander.
Canon EOS 400D (aka. XTi) • 20" iMac Intel • 12" PowerBook G4 • OS X 10.4 • LR 1 • PSE 4

Similar Messages

Bug report and question about 2.0

ok I have 2 things I need to post about. First is a bug report.
Under settings, brightness category the slider does not function correctly. It refuses to slide like it did in 1.1.4.
Second the capacity has dropped from 14.84GB to 14.6GB. What is taking up 240 MB of space?

thanks for info. Sorry I didn't post this earlier but the slider has corrected itself. Also the is probably being used by the os

Strange behavior when Popup LOVs has read-only condition and Bug Report

Hi,
I observed an inconsistent behavior of Popup LOVs when the read-only condition is true. In that case the defined lov query is used to map the internal value of the page item to the display value defined in the lov query.
What is the reason for this behavior? Because if the Popup LOV is in "edit mode" the page item value is just displayed without looking up the display value. The display value is just used for the popup lov. Mapping the value is normally a behavior of the popup key lov.
-> The result is that different values are displayed if the page item is in edit or read-only mode. That's not really the behavior someone would expect.
BTW, there seems to be a bug with "Display Extra Values" set to "Yes" in the case read-only is true. If the lookup doesn't return a value it just displays [ ], but because the property is set to yes it should display the value. The Popup Key Lov has the same bug.
Thanks for bringing some light into that behavior
Patrick
Oracle APEX Essentials: http://essentials.oracleapex.info/
My Blog, APEX Builder Plugin, ApexLib Framework: http://www.oracleapex.info/

Patrick,
I've added your comments to a task already in our queue to examine all item types for correct behavior in read-only mode. I've noticed the quirks with display extra values also.
By the way, still interested in your thoughts re: Re: Bug Report: Images broke when using get_blob_file_src and not authentic .
Scott

Bug Report: The keyboard focus doesn't automatical...

Bug Report: When a conversation window opens, the focus doesn't automatically land in the chat entry text field.
Since the new interface for Skype was introduced officially in Skype 7.0, there is a bug with the system/keyboard focus for a new conversation window. When Skype is in "Split Window View" and each new conversation automatically pops up in a separate window, the system/keyboard focus doesn't land in the chat entry edit field. Instead, the user has to press Shift+TAB a couple of times, to move it there and reply to the chat message received. This especially problematic for screen reader users, who rely on keyboard navigation. This mainly occurs when a new conversation is started with an incoming message, but it sometimes occurs when moving the focus out of that conversation window and later back in it again (while it is still opened).
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Tell someone to send you a chat message. When the message arrives, Move the system focus to the conversation window in question, preferably with Alt+TAB. The system/keyboard will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should by default, but in some unknown place in the window.
7. Move the system/keyboard focus in the chat entry edit field and keep it there.
8. Switch to another window, preferably from another application.
9. With Alt+TAB, switch back to the window of the opened Skype conversation. There is a chance that the system/keyboard focus will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should do by default, but again in some unknown place in the conversation window. But that is harder to reproduce.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

Bug report: A keyboard layout is incorrect on the remote with Japanese keyboard

This is a bug report for Microst Remote Desktop
===================================================
## Summary
A keyboard layout is incorrect on the remote with Japanese keyboard
## Version Information, I tested
* Client
   * Case 1
       * MacBook Pro with JIS106 Keyboard
       * Mac OS X Lion 10.7.5
       * Microsoft Remote Desktop 8.0.24308
   * Case 2
       * MacBook Pro with JIS106 Keyboard
       * Mac OS X Mavericks 10.9.1
       * Microsoft Remote Desktop 8.0.24308
* Remote
   * Case 1
       * Windows 7 Professional Japanese
   * Case 2
       * Windows Server 2008R2 Datacenter Japanese
   * Case 3
       * Windows Server 2012R2 Datacenter Japanese
## Detail of bug
When login from Mac OS X with Microsoft Remote Desktop, the keyboard layout is always incorrect on the remote.
The client machine have a built-in keyboard of JIS 106 layout,
and the primary language is set to Japanese.
But on the remote, the keyboard layout is US 101.
So a input of Shift+2 does not result " but @.
I've seen the above behavior on the 3 remote enviornments described the above.
This bug did not occcur with Microsoft Remote Desktop Connection Client for Mac 2.1.1, even if the system language is English and keyboard layout is Japanese.
## Captures
I've took some of screen captures.
I'm sorry for the capture includes Japanese words, so I added description in English.
Capture 1:
Mac OS X Keyboard Setting
Capture 2:
Windows Server 2012R2 Screen Keyboard
Capture 3:
Windows Server 2012R2 Screen Keyboard, with a additional registry key configured.

This bug also affects the Canadian English settings. If the client is set to Canadian English with a US keyboard the remote server is setup using a Canadian French keyboard. Using the language selection in the toolbar you can temporarily correct
the problem but the keyboard resets to french at the most inopportune times. The was a problem in the earlier RDP client and was fixed so it's sad to see it reoccur in the new client.
Lawrence

Bug Report

On the bug report section on the Adobe website there is no way to select Muse.
Mavericks OS 10.9.1
Muse: v7.2, build 232, CL 779928
I click Browser Fill > image, then when I attempt to select an image, I can't scroll through my files. Then all scrolling on the page stopped working until I restarted the program.

Hi Muse Team!
It seems that Muse Preview, Preview Page and Preview Site in Browser are not working in a proper way. Everything is OK in Design Mode but logos and some other elements move to strange places in all Preview features.
Best Regards
Jarmo

Bug Report: New conversation window stills the sys...

Bug Report: Skype Desktop: New conversation window stills the system/keyboard focus.
When the UI is in multi-window mode and a conversation window pops up (due for example to a newly received chat message), that window steals the system/keyboard focus, even though it appears in a minimized state in the Windows taskbar. And this should not happen by default, because it is impractical (especially for screen reader users). And it didn't happen in Skype 6.21 and earlier. But since the new UI was introduced officially in Skype 7.0, it started happening constantly.
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Move the system focus to another application.
7. Tell someone to send you a chat message. When the message arrives and the conversation window pops up minimized in the Windows Taskbar, everything seams to be as it should. A few seconds after that however, the system/keyboard focus gets moved to that new conversation window, even though it is neither restored/maximized (it is minimized), nor it is visible on the screen (except as a button in the taskbar).
Actual results:
When a new conversation window pops up in the Windows taskbar, it stills the system/keyboard focus to itself from the currently focused application.
Expected results:
Skype's popping up new conversation windows should not still the system/keyboard focus to themselfs from the currently focused application.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

The new Synaptics UltraNav: a few workarounds and minor bug report.

I only wanted to file bug report, but then decided to also share what I did with my touchpad configuration to make it more convenient for me. I have Thinkpad T540p so this might work differently or not work at all for other notebooks.
#1 Regedit
Configure as much as you can using UltraNav tab in mouse settings dialog. (It is mostly self-explanatory.)
If you didn't find some option, start regedit (using Win+R) and navigate to
HKEY_CURRENT_USER\Software\Synaptics\SynTP\something
This something is TouchPadSMB2c on T540p but you can find one you need by changing something in settings dialog and looking for changed values in regedit.
All the touchpad configuration registry keys are there. You need to relogin to apply changes made there.
But it might take a lot of trial and error to find out how these registry keys work.
#2 3-finger tap
As for me, I prefer tapping over clicking. While 3-finger press option is in settings dialog, 3-finger tap is not. But you can change it.
Set whatever option you want for 3-finger press. Then go to regedit and copy value from 3FingerPressButtonAction key to 3FingerTapAction.
#3 Button sizes and locations
You can change button bounds with keys like LeftButtonZoneX where X is L for left, R for right, T for top and B for bottom bounds. 0xFFFFFFFF ultimately means "unlimited in that direction". For finding other values defaults might be helpful. Trackpoint buttons keys are SlaveSomeButtonZoneX.
What for?
First, trackpoint buttons can cover the whole trackpad only when trackpad itself is disabled. By changing button sizes manually you can overcome this restriction. It is useful because trackpad does not respond well to pressing corners and when buttons cover it all you can press it somewhere in the middle.
Second, the same corner pressing problem exists for normal trackpad buttons so it is more convenient to use multi-finger taps or clicks. You can still hold trackpad pressed with one finger and use yet another finger to move mouse pointer.
At the same time when you tap or press with multiple fingers and one of them touches one of the buttons you get that button pressed instead of whatever you intended. It frustrated me a lot when I got context menu popups while trying to close chrome tabs with middle mouse button click. The solution is to set top bounds for left and right buttons to zero.
BUG (With the latest UltraNav drivers from support page)
When the middle trackpoint button (used for scrolling) is enabled, it is always enabled, no matter if you are using trackpont or touchpad. Left and right trackpoint buttons are properly disabled when you don't need them.
Even if you disable trackpoint completely without disabling that middle button first, it will remain enabled and will do nothing. (Blocking single- and multi-finger presses that touch it.)
I could not find a way to fix that problem with regedit.

Any problem can get official response and follow-up through a SR on Metalink/MOS (if you have a DB support contract), else you can post here and hope someone from development picks it up.
Regards,
K.

Bug Report: DW CS5.5 Crashes Every Time On An Image Map

I am posting this in lieu of contacting Adobe support. I went to my account to send Adobe a bug report and was told I needed to contact support via phone. That's pretty crappy. As a licensed user who's owned it less than three months, there's no direct path to tell you guys that your software is broken?
Here's the deal: I am working on an HTML landing page with one image map attached to one image. Literally, every time I make a modification to the code near the image (tied to the image map) then click into the live preview window, Dreamweaver CS5.5 crashes like a 70-year old on a bar of soap on the floor of the shower. It crashes hard. My only relief is to save the file before clicking into the live preview window. That's my only workaround to the problem.
But I'm left amazed that I can crash it every single time over an image map, flicking from the code to the preview pane. You would think that at version 11.5, a minor thing like that wouldn't hemorrage the supposed creme de la creme of web design software.
Here's the code I'm editing that causes it to crash:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
          <?php
          require_once("/var/www/html/c/index.php");
          $recip_name = $subscriber['first_name'].' '.$subscriber['last_name'];
          ?>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link href="/c/print.css" type="text/css" rel="stylesheet" media="print">
<title>Membership Special - No Commitment</title>
</head>
          <?php // Google Link Tracking Code ?>
          <script type='text/javascript' src='/c/google-analytics-code.js'></script>
          <?php // End Google Link Tracking Code ?>
    
          <link rel="stylesheet" type="text/css" href="http://yui.yahooapis.com/2.9.0/build/reset/reset-min.css">
    <style type="text/css">
                    body {font:normal 14px/1.25em Georgia, "Times New Roman", Times, serif;}
                    h1,h2,h3,h4,h5,h6 {font-weight:bold;color:#333333;}
                    h1 {font:normal 28px/1.5em "Trebuchet MS", Arial, Helvetica, sans-serif;}
                    h2 {font:normal 24px/1.5em "Trebuchet MS", Arial, Helvetica, sans-serif;}
                    h3 {font:normal 20px/1.5em "Trebuchet MS", Arial, Helvetica, sans-serif;}
                    h4 {font:normal 16px/1.5em "Trebuchet MS", Arial, Helvetica, sans-serif;}
                    h5 {font:normal 12px/1.5em "Trebuchet MS", Arial, Helvetica, sans-serif;}
                    h6 {font:normal 8px/1.5em "Trebuchet MS", Arial, Helvetica, sans-serif;}
                    a, a:link, a:visited, a:active {color:#0055FF;}
                    a:hover {color: #002AFF;}
                    #wrapper {margin:0 auto;width:432px;}
                    #header, #footer {margin:20px auto;text-align:center;position:relative;}
                    #footer {margin:40px auto;}
                    #coupon {position:relative;}
                    #coupon, #coupon img {margin:0 auto;text-align:center;}
                    .personalization {position:absolute;width:100%;text-align:center;text-transform:uppercase;}
                    .printcoupon {text-transform:uppercase;}
          </style>
<body>
<div id="wrapper">
<div id="header">
          <h3 class="printcoupon"><a href="javascript:window.print();">Click here to print your coupon</a></h3>
</div>
<div id="coupon">
          <img src="images/19415coupon-01.jpg" width="432" height="432" />          
<img src="images/19357coupon-02.jpg" width="550" height="602" usemap="#imagemap" class="dontprint"/>
</div>
<div id="footer">
          <h3 class="printcoupon"><a href="javascript:window.print();">Click here to print your coupon</a></h3>
</div>
</div>
<map name="imagemap">
          <area coords="29,69,521,197" shape="rect" href="javascript:window.print();">
          <area coords="29,212,521,339" shape="rect" href="http://www.google.com" target="_blank" onClick="recordOutboundLink(this, 'Landing Page', 'http://www.google.com');return false;">
                    </map>
</body>
</html>

Bug Report and Feature Request https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

How do i use the bug reporter in ios 8

im trying to use the bug reporter for the beta ios 8 but i dont get to input anything. Maybe i dont understand how this works,so can someone please explain.either way i figure i should say somthing now.
-the infinity blade 2 app does not load
-my settings button doesnt load all the time,
-most of the apps dont load the first time i open them,if i switch to another menu then back it will load.
-just now i shut off my phone, plugged it into the charger. My phone then turned itself back on and had me reactivate it.
-the "sample" button in the ibooks app doesnt seem to do anything either
-most of the time scrolling down on anything rather large(e.g.songs,articles,facebook) there is alot of skipping or lagging effect
-when on safari i turn my phone sidways and it totally messes up where things should go and it wont return i have to exit and close to fix
anyways id just thought id put that out there

You need to ask this question in the Developer's forum, which as a registered developer you have access to. If you're not a registered developer, then you have no business messing with iOS Beta software, & discussing such, even bug reporting, is PROHIBITED in this public forum.
But, as a registered developer, you already knew that, correct?

Since I can not log in bug report page, not even getting an error message, I'll write all my issues with ios8 here...

Since I can not log in bug report page, not even getting an error message, I'll write all my issues with ios8 here... I have an iphone 4S and I did the last update. Now I am in trouble.
1. When I move the "sound on/off" button, I get it buzzing 10 times before the setting is changed and I can do anything else, just not reacting to the round button on screen touches.
2. Impossible to copy text from most websites into notes.
3. Impossible to delete an email account in settings.
4. Uses up the battery twice as fast as before. I have "update apps" setting turned off, just reading a couple of mails, making a couple of photos and open maps apps twice a day, and the battery is dead well before the evening.
5. Got extremely slow, and it was getting slower and slower with every system update.
I'm sure I forgot something... But well, that already a lot.

Well, actually number 3 in my list is not true any more, I just tried to delete my account 15 times, then I've written my post, then half an hour later my Settings finally updated my accounts list. Whohoo
I did not try restoring it yet, thank you for the link!

Display Bug in LV 8.20 Application Builder

There seems to be a minor bug in the displaying of the "VI Settings" in the application builder for LabVIEW 8.20.
The problem is in an executable build spec, in the "Source File Settings" category.
Select a sub VI in the tree, then uncheck the select box for the "Remove Panel" property. Now select any other VI in the tree, then go back to the one you unchecked the "Remove Panel" box. You should see that the box is now checked.
If you don't do anything else and just select "OK, then go back into the build spec, you'll see that the property was correctly saved as unchecked. So it looks like it's just a display problem.
I've made sure the VI I try this with does not use any property nodes and it is not marked as a dynamic VI. I can reproduce this on two machines running Windows XP Pro SP2 and LabVIEW 8.20.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

In addition to Ed's
comment, I would like to say that this unexpected behaviour is not
always appearing. I have just seen following while editing this text :
I have unchecked the Remove Panel box for all the UI VIs (all are
located in the same directory). When scrolling through the different UI
VIs in the Soure File Settings, the box was unchecked for all the VIs.
Without closing the Source File Settings window, I switched to
Developer Zone and switched back to the Source File Settings. For some
UI VIs, the Remove Panel box was checked. I closed the window and
opened it again, the box was unchecked again for all the UI VIs.
But I have also encountered the case that when scrolling through the
VIs to try to uncheck this setting for all of them, it suddenly appears
checked again for a VI for which it was unchecked or unchecked for a
before checked VI.
You finally end with a very unclear situation and it may be that the
Remove Panel is really checked for some VIs. At least, in some cases,
the built EXE could not run because of missing front panels. I can't
remember the exact error messages when running the EXE but they
mentionned the name of the VI and something about missing ressources. I
opened the .lvproj file and noticed that the "Remove Panel" property of
these VIs was set to TRUE. After modifying these settings and
rebuilding the EXE, it ran as expected.
In development, I
normally uncheck "Allow user to resize window" of the UI VIs because
this setting can unfortunately not be changed when configuring the
executable. In the "Source File Settings" I uncheck all options of "Use
VI Setting" for these UI VIs and I only check "Auto-Center" (all VIs)
and "Window is Modal" (some VIs).
There is another problem with the application builder that I would like
to mention. For (at least) following settings, the development settings
of a VI will not be overwritten by the Source File Settings when
building the executable :
- Window has title bar
- Show Menu bar
- Show Toolbar
- Show Scroll Bars
This is also very annoying because you will need to change these
settings in the development environement in order to get the expected
appearance in the executable.
LV8.2 English / WXP SP2

Bug Report - Windows 8.0 - 6.0.1 USB arbitration causes USB keyboard driver failure

Can't find a place to submit a bug report. So here goes.
Full Error Message:
Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory.
Problem Occurs:
Windows 8.0 x64
Vmware Player 6.0.1 build-1379776
Problem:
A USB keyboard ceases to function on the host operating system following the first host OS reboot after installing 6.0.1 on Windows 8.0. This issue does not occur with 6.0.0. The issue disappears upon uninstalling Player 6.0.1. Reinstallation allows Player to operate as expected, but issue re-appears after host OS reboot.
The issue happens immediately after host OS loads, and continues irrespective of whether VMWare Player is launched.
Looking at the keyboard drivers, the usb keyboard's driver has not loaded (see attached images). The built-in keyboard driver however reports no errors and continues to operate as usual.
Changing the USB keyboard device to that of a different manufacturer does not resolve the issue. Any USB keyboard driver appears to fail.
Work Around:
1) Launch msconfig
2) Disable VMWare USB arbitration service
3) Reboot
4) USB Keyboard works. VMWare Player continues to operate as normal, minus the ability to mount USB storage devices on the guest OS.

This issue was fixed on my PC as follows.
1) Taking ownership of the above usb*.sys files in the drivers folder
2) renaming them to usb*.sysold
3) Using Device Manager to uninstall all USB devices with the yellow warning ! next to them
4) Doing a Scan for Hardware changes via the Device Manager toolbar and then waiting a few moments whilst the USB devices are re-installed with signed drivers.
Hope this helps you....
usb drivers files in my drivers folder after the above process:
12/02/2013 04:12            19,968 usb8023.sys
21/11/2010 03:24            32,896 USBCAMD2.sys
27/11/2013 01:41            99,840 usbccgp.sys
12/07/2013 10:41           100,864 usbcir.sys
27/11/2013 01:41             7,808 usbd.sys
27/11/2013 01:41            53,248 usbehci.sys
25/03/2011 03:29            52,736 usbehci.sysold
27/11/2013 01:41           343,040 usbhub.sys
25/03/2011 03:29           343,040 usbhub.sysold
25/03/2011 03:29            25,600 usbohci.sys
27/11/2013 01:41           325,120 usbport.sys
25/03/2011 03:29           325,120 usbport.sysold
14/07/2009 00:38            25,088 usbprint.sysold
11/03/2011 04:37            91,648 USBSTOR.SYS
25/03/2011 03:29            30,720 usbuhci.sys
21/11/2010 03:23           184,960 usbvideo.sys
              19 File(s)      2,783,104 bytes
The .sysold files are the ones I renamed, I think also renamed the usbccgp.sys - but accidentally deleted it after the rename..

Acrobat X Scanning Cancelled Problem / WORKAROUND / BUG REPORT

As you have read in other threads, Acrobat X on Windows has a serious scanning problem with HP and possibly other scanners.
Whereas in Acrobat 9 scanning worked reasonably well, Acrobat X seems to be unable to cope with scanning documents from the flat bed of a multifunction scanner.
So, if you are scanning from the feeder, scanning works, but if you are scanning from the flatbed, you will get a brief pause and the phrase SCANNING CANCELLED.
This is, of course, not acceptable.
The problem is that Acrobat X does not play nicely with the scanner drivers. Previously, Acrobat 9 would "auto-detect" the source of a document, using the feeder if loaded, and "falling back" to the flatbed otherwise. However, Acrobat X does not fall back. If there is nothing loaded in the document feeder, the scan will be cancelled by Acrobat X.
The workaround - and I would NOT call this a "solution" - is to use only the "Custom Scan" command from Acrobat X. When the window pops up, choose the "Options" button and select "Native Mode" and "Show Scanner's Native Interface" from the two menus. (Acrobat X does seem to remember these settings at least within a session, so if you're scanning multiple documents you only need to do this once.) Then scan.
You will see a new window pop up - the scanner's "native interface." On my computer, this window shows up BEHIND the Acrobat X screen (annoyingly) so you have to watch for it and click forward. Be sure to select "flat bed" from the "document source" menu. On my computer, this setting is NOT remembered between scans, so you have to do this for EVERY SCAN. Then, the document will scan, and you can do what you want with it in Acrobat X.
Needless to say, this is a long, painful, slow process, especially if you're scanning lots of flatbed items, as I do. Hence it's a "workaround" and NOT a "solution".
The SOLUTION will be for Adobe to FIX this. ADOBE: THIS IS A BUG REPORT. PLEASE LOG THIS IN AND FIX IT. Acrobat 9 with CS5 worked perfectly, as did Acrobat 8 before it. Moving to CS5.5 with Acrobat X broke this. Sloppy. Please fix! Thank you!
Glen Barney

I used your workaround (thank you!) but it was very annoying. Although I set up the options for a single multi-page document, Adobe gave me separate files and I had to consolidate them. I also had to fill out the options (color, flatbed vs feeder) for each page. This function was working for me at some point, so I don't know what happened to make my HP Multifunction and Adobe part ways. I hope Adobe comes up with a successful patch for this problem.

Bug (reported to Apple) - Slide to unlock occasionally fails!

Hello folks,
Below is a copy of my bug report, I just missed an urgent call (with no call back number)... so I was prompted to finally report this problem!
Has anyone experienced this (I noticed some similar reports but none that exactly match my description).
NOTE: Please do not suggest that I turn off the "Slide to unlock" feature. I need to engage it, otherwise I will lose access to my corporate email.
Report----------------
Phone: iPhone 4
iOS: 4.3 (8F190)
I am experiencing a problem with the Slide to Unlock feature.
It is an inconsistent problem which is hard to repeat intentionally. However, it seems to occur randomly, about every 1 in 15 calls.
I believe the conditions related to the problem are as follows:
- Phone enters Auto-Lock mode (5 minutes)
Password Lock is engaged
- Screen off (phone not in use for more than 5 minutes)
Problem description:
When I receive phone call, I attempt to slide the "Slide to unlock" slider to the right. The slider does move to the right as intended, however, it has no affect on displaying the keypad.
The expected result should be the numeric keypad so that I can enter my keycode. As previously mention, these actions to answer a call do work more than 90% of time.
Additionally, pressing the Home button or the power button also has no affect while the phone is still ringing.
Only after the ringing has stopped do I regain control of the phone.
Note: This is not a new problem with iOS: 4.3 (8F190), rather, this did begin with the last iOS version.

Mine did it too, I would swipe the slide to unlock and the first attempt
failed usually 50% of time. I've since reactivated my old Nokia N95 until
we see what the next gen iPhone holds for us. My iPhone 4 was nothing
but trouble.
Despite this problem (which occurs rarely) and a few other idiosyncrasies, I can't agree with your statement. Since upgrading from the Android platform, the iPhone 4 is (by far) the very best phone I have ever owned!
It is hard to feel sorry for all those Android 'suckers' out there still complaining and hating their service providers for not releasing the latest aOS fixes. Complaining about bugs that will likely never get fixed...that is unless they upgrade to new Android hardware. Android... NEVER AGAIN!
BTW, I am no fanboy... I am just pleased with the iPhone user experience!

BUG report - Inconsistent IR settings in Builder

Similar Messages

Maybe you are looking for