Screen draw bugs?

Has anybody experienced these bugs in Dreamweaver CSS for the
Macintosh:
a.) When you have multiple windows open at once and you "step
back" from them in Expose to view them all at once, some or all of
them display as blank white sheets.
b.) When you drag a window to reposition it on your screen,
it displays in both locations until you click on it in its new
location.
c.) Sometimes when you mousedown + drag your cursor over a
bit of text to highlight it, the highlighting fails to show on the
screen, although the text you have chosen is in fact selected and
can be cut, copied, etc.
d.) Suddenly and inexplicably a page of text will start
displaying in a different font than the one you chose, and you have
to quit and reopen the document to get the font back.
I'm curious to know if I am unique in experiencing these
problems, or whether they are common. I suspect the latter, since I
am using a Mac Pro that is pretty much out-of-box, with the
original graphics card and so forth. Or is there some other
software I could have on my computer that could possibly interfere
with DW working properly.

Has anybody experienced these bugs in Dreamweaver CSS for the
Macintosh:
a.) When you have multiple windows open at once and you "step
back" from them in Expose to view them all at once, some or all of
them display as blank white sheets.
b.) When you drag a window to reposition it on your screen,
it displays in both locations until you click on it in its new
location.
c.) Sometimes when you mousedown + drag your cursor over a
bit of text to highlight it, the highlighting fails to show on the
screen, although the text you have chosen is in fact selected and
can be cut, copied, etc.
d.) Suddenly and inexplicably a page of text will start
displaying in a different font than the one you chose, and you have
to quit and reopen the document to get the font back.
I'm curious to know if I am unique in experiencing these
problems, or whether they are common. I suspect the latter, since I
am using a Mac Pro that is pretty much out-of-box, with the
original graphics card and so forth. Or is there some other
software I could have on my computer that could possibly interfere
with DW working properly.

Similar Messages

  • Lumia 900 Screen Draw bug

    Found an interesting bug on a few lumia 900's (i have tried it on 4 and all show it) that may affect certain games, especially Harbor Master for me since it involved drawing lines to the screen edge.
    The problem is that if you draw one straight line from the left edge of the screen to the right edge (or the  other way around), the end of the right edge (about 1 cm wide)  doesnt acknowledge the line drawing unless the line is drawn very slowly.
    To reproduce the bug, open the nokia diagnostic tools and run the 'Touch' test. To get the diagnostics tool if you dont, just dial ##634# using the touchpad.
    Draw a line fro the left edge to the right edge quickly and you will see what i mean. Or from the right to left. The same thing happens if drawn from top to bottom.

    1. I notice it is when I go to unlick my phone there is a noticable lag. When I pres the first digit of the PIN it doesn't register until after I have tapped the second characetr of the PIN. 
    2a. When the phone is charging it is VERY laggy. This is especaiily noticable when scrolling the start screen. Instead of the buttery smooth scrolling it is very choppy.
    2b. I have also noticed the slow response when plugging/unplugging the phone. Just today after I unplugged my phone it toook several minutes for it to acknowledge it had been unplugged. As long as that occurs I see the issua of 2a (choppy scrolling, etc.) as is if it were still plugged in.
    3. The entire device seems to momentarily freeze when the brightness automatically adjusts.
    4. At times the typing in any text box (email, text meassage, etc.) seems to fall behind. It is most noticable when first starting the message (maybe the brightness is changing?).
    I have those EXACT Same issues too.  Will also not that the brightness (when on auto) is SLOW to adjust to the lightting enviroment.  The biggest pain is #1 - as i usually have to enter my PIN in twice..
    I love my purple screen, 1/2 day battery, sketchy touch screen and $800 price tag - I call it my Lumia 900

  • KT880 Slow Screen Draw and other problems

    Is there a performance issue with the Kt880 boards that causes it to draw the screen slow, and causes the onboard LAN to fight with the USB controllers?
    Do I need to reduce the FSB of my RAM @333 to the FSB of the 2400+ @266?
    Maybe there are some BIOS tweaks that fix this problem?

    Not sure yet but I think I have sorted out most of the bugs.
    Changing the FSB speeds and removing a stick of ram does nothing, except to reduce the system performance slightly.
    Updated BIOS to latest. No change.
    Repair install after removing Symantec AV 9 Corp, and System Works 2005. helped some.
    Removing the NIC, uninstalling all Networking components then putting it all back really made an improvment.
    Then I turned on the SATA controller and let it install the PCI to IDE bridges and that helped. Removed the VIA CPU to AGP driver and it reinstalled it's self. slight improvment on the screen draw problem.
    Getting the USB to stop messing with the PCI bus was easy. I removed all the PCI cards RESET Bios data, reinstall VIA 4.53, added the PCI cards in one at a time then added on the 2 extra drives. Will change the drives to SATA next week.
    I think the whole problem comes from the install CD I made with NLight. Nlight has an option to remove components, turn off SFP and modify the UXTHEME.dll, and the TCPIP.sys file.
    After work Monday I will try a fresh install of Win XP OEM original on a spare drive, and update it to SP1, then SP2 and see how it goes.
    So far game play is excellent with good frame rates and no crashes. My team mates were complaining of poor frame rates on a custom BF1942 DC Map with frames of under 10FPS where I was at 65 to 100FPS.
    That poor KT600 I had was probably fine

  • Excel 2013 BeforeRightClick Event fails on Windows 8.1 Tablet (it's an Excel 2013 tablet touch screen interface bug)

    I have developed customized table context menus in an Excel 2013 workbook on my Laptop. They work just fine on my laptop and my work desktop. But when I try to run them on my tablet PC the Worksheet_BeforeRightClick event in Excel 2013 never fires. Other
    worksheet events appear to work okay. I have fully reinstalled Office 2013 Pro and that does not make any difference.
    I have read other comments regarding this same problem going back to 2013, but have never seen Microsoft respond to this issue. Nor have I been able to find a resolution. Has anyone else run into this and found a solution?
    Additional Discoveries: Testing on my tablet shows that adding one custom CommandBarButton to either the top or the bottom of the default "List Range Popup" context menu causes the Worksheet_BeforeRightClick event to fail.  The basic context
    menu commands still show up, but the default dropdown button for additional context menu commands disappears. The event is perhaps firing, but any customized code for the context menu is not being handled properly by Excel. This does appear to be a bug and
    not a question of coding error. Perhaps someone else with a tablet PC running WIndows 8.1 could test this.
    Based on comments
    here this bug was introduced in Excel 2013 because others find the problem does not exist when using Excel 2010 on a tablet PC. Note that all the commenters on the linked thread that are experiencing this problem are using tablet PCs.
    Update 3-13-15: I stand corrected. The Worksheet_BeforeRightClick does work on Excel 2013 Windows 8.1 tablets. I happen to own an Asus VivoTab Note 8, which comes with a Wacom stylus. If I use the Wacom sylus to right click on an Excel 2013 worksheet cell,
    the Worksheet_BeforeRightClick event fires and modified context menu code runs just fine. But the code will not run if one uses their finger to right click a worksheet cell. This explains why this problem only shows up on tablet PCs. So the "bug"
    introduced in Excel 2013 is a general user touch screen interface bug and not an Excel events programming bug.
    Update 3-21-15: Switched to a  Toshiba Protege laptop with touch screen. Same issue with finger touch screen interface on the Toshiba touch screen as with the Asus VivoTab touch screen.
    Laptop: Toshiba Protege (with touch screen), Windows 8.1 64bit and MSOffice 2013 Pro 32bit
    Tablet: Asus VivoTab Note 8, Windows 8.1 32bit and MSOffice 2013 Pro 32 bit
    Desktop: Generic, Windows 7 64bit and MSOffice 2013 Pro 64bit
    phillfri

    Hello Phil,
    Command bars were deprecated and shouldn't be used any longer. Instead, you need to use the Fluent UI (aka Ribbon UI) instead. You can read more about the new UI in the following series of articles in MSDN:
    Customizing Context Menus in Office 2010
    Customizing the 2007 Office Fluent Ribbon for Developers (Part 1 of 3)
    Customizing the 2007 Office Fluent Ribbon for Developers (Part 2 of 3)
    Customizing the 2007 Office Fluent Ribbon for Developers (Part 3 of 3)
    As a workaround you can add a custom control to the context
    menu with the getEnabled or getVisible callback which will be invoked before the context menu is shown.

  • Delayed live screen drawing with tools in Photoshop. Video driver update?

    Delayed live screen drawing with tools in Photoshop CS5 on my iMac running system 10.6.7.
    Hi there. Recently, I've been having issues with the tools. There's a distinct DELAY in the live drawing. For example, if I open a random image, take the pencil, paintbrush, or even eraser tool, and I draw a large line across the image, I don't see anything. If I zoom in or out 1 click, I see the line. If I draw ANOTHER line, same thing - I need to zoom in or out to see it. With all of the tools. I've never had this issue before and it's incredibly frustrating (that might be an understatement as you can imagine - I use PS daily as I am a full-time designer.) Any ideas or solutions? I've already TRASHED my preferences and reset the tool. If it IS a driver issue (which is weird, because this issue just recently started happening) I contacted the driver manufacturer (AMD) and was told:
    "Unfortunately, Apple does not authorize us to release drivers for their products.
    All drivers are provided to Apple who then customize and release them to their customers.
    You will need to contact Apple to obtain the most current drivers for your product."

    You are correct - only Apple can deliver display drivers to you.  That's what you get with a Mac as Apple wants to be your "one stop shop" for support..
    Just curious:  Are you painting with large brushes and very small Spacing values?  That can cause some delay, though it normally catches up on its own - you don't have to do anything to make it happen.
    Have you tried disabling OpenGL Drawing in your Photoshop Edit - Preferences - Performance menu.  Restart Photoshop after making that change and before testing.
    -Noel

  • KT880 Screen Draw problem

    Someone else posted a similar thread, but his issue got resolved.  Here's the deal.
    I have the system described in my signature.  The PSU is not mentioned, but it is an Antec 400W PSU that I bought specifically because it met the suggested requirements set forth in the Trouble Shooting guide (I'd list the amps, but I really don't want to open my computer up right now).  Anyways, the screen draw performance is horrible, particularly in Windows Media Player 10 and at http://www.pcpitstop.com during the video test.  The odd thing is that when I play games (Rainbox Six 3 Raven Shield for example) I see no problem in video performance.  I just reinstalled windows, updated it, and then installed the latest 4in1s and nVidia driver (66.93) and tried it: same problem occurs.  I have tried my Mushkin memory as well as some cheap SimpleTech stuff I have, and both give problems.  Any suggestions?  Do you think this may be a problematic board?  Does any other KT880 Delta user have this problem?

    Quote from: drummer13 on 07-March-05, 15:53:33
    https://forum-en.msi.com/index.php?action=dlattach;topic=74852.0;id=448
    There is the URL to the beta bios. It is named as index.zip, but I downloaded it and it is fine. In case the .exe file doesn't work, just download the 1.8 bios file from the kt880 webpage and use it. That was the one I used.
    I don't think this is a quality of memory issue. I set one up for my friend with some corsair memory in it and it did the same thing. And the beta bios here (1.9b6) fixed it and mine. I am not sure what exactly it fixes, but it does fix it. My computer was the same. good on games, bad on desktop. It's got me, but all I know is my system is a beast now.
    Hope this helps... but remember, don't cry if you blow stuff up using beta anything.
    I'm crying now... I recently got a KT880 with 512MB x2 Corsair PC3200 value RAM. Right now not overclocked, DDR set to SPD mode. I was using bios 1.8 and I couldn't install WinXP SP1 or SP2 with "Vlink8X" enabled in the bios. Once disable I can install everything. Even then sometimes my PC will restart itself for no apparent reason, even with onboard Gigabit and AC97 disabled. I tried bios 1.96 and now my PC reboots itself again and again during POST. How I know, the keyboard lights blink every 5 seconds or so. Anyone else experiencing this?
    XP1800+ stock
    MSI KT880
    Corsair Value PC3200 at SPD timings
    Sapphire Radeon 9800 Pro 128MB
    80GB Seagate SATA with NCQ
    LG DVD-DL burner
    Surecom 10/100 PCI

  • My macbook pro for over an hour has on the screen report bug, setting up  and processing log in

    my macbook profor over an hour has on the screen report bug, setting up and processing log in? what should i do

    my macbook profor over an hour has on the screen report bug, setting up and processing log in? what should i do

  • 2D Screen Draw Issues - KT880 Delta

    Ok, here I am again after resolving all the other issues.
    It would appear that I am having some slight 2D screen draw issues.  As with everyone else that has posted in these forums along the same lines with the KT880 Delta everything is fine with 3D.  For some reason it is only with 3D.
    So far I have done the following:
    Moved my Soundblaster Live Card to the 5th PCI Slot to avoid any conflict.
    Installed, Uninstalled and reinstalled both sound and nVidia drivers
    Disabled VLink 8x in the bios
    Set AGP to 4x in the bios (I only have a 4x AGP card currently)
    Set the cache to 128mb
    First installed the correct 4-in-1 drivers, then superceded thoses with the Hyperion drivers instead.
    Despite all this I am still getting draw issues when minimising and maximizing windows, scrolling through web sites, and dragging open windows around the desktop.  However, I have tried 2d drawing tests on windows media player 10, as well as pitstop (that actually told me I had a good setup!!)
    So, not too sure what to do...any more help would be great.
    Specs are:
    MSI KT880 Board
    Sempron 2800+ 2.0ghz CPU
    1.5Ghz DDR333 memory
    Gainward MX440 128Mb 4x AGP card
    Creative Soundblaster Live! 1024 card
    350w PSU (Not sure what type it is!!!)
    I hope thats enough information

    This appears to be a recurring problem with the KT880 across several different graphic cards (mostly NVIDIA).  I've never seen so many complaints specific to 2D graphics collectively as have been reported here for just one particular mainboard.  There is talk of a BETA BIOS that solved at least one case, but not others:
    KT880 Slow 2D Performance with Leadtek 6600GT AGP
    KT880 Screen Draw problem
    KT880 DELTA mainboard and 2D speed decrease
    MSI kt880 Delta + Graphics card = problems
    KT880 Slow Screen Draw and other problems
    KT880 DELTA FSR Problem with graphics in Win XP
    The number of reported cases is more than the # of threads because some users entered into existing threads to report they had the same problem with KT880.  MSI should be investigating this issue.

  • Screen redraw bug when panning in Loupe view at high magnification

    I think I've found a bug in Lightroom.
    Using the Loupe view at higher than 1:1 magnification and panning whilst zoomed seems to cause screen redraw artifacts. It is most noticable at high zoom (say 11:1) when panning diagonally. The edges being revealed draw incorrectly. Seems to only happen once the 1:1 preview rendering has been completed, initial panning whilst the preview is being rendered looks fine. Zooming out and back in redraws the screen correctly, but subsequent panning still causes artifacts.
    I first thought it must be my graphics drivers, but have updated to the latest available driver (version 7.2 21 Feb 2007) for my ATI Radeon 9800 and the problem remains. I have also tried this on my laptop a Sony VAIO VGN-S3HP (with NVidia GeForce 6200 based graphics) with the same problem. Therefore as this happens on both a NVidia and an ATI card I can't blame my graphics drivers any more.
    Can anyone reproduce?
    Best regards,
    Andrew

    I've just seen a similar problem on my DELL laptop. Anything at 2:1 or greater magification gets the jagged edges whilst panning up and down in loupe mode. This makes the compare mode to be worthless as the two images can't be compared as they each suffer different amounts of jaggies.
    Windows XP, Intel Mobile 915GM/GMS, 910GML Express Chipset.
    I'm going to raise a bug report.

  • Full screen mode bug in Safari?

    In Safari, running in full screen mode, if a link opens a file (eg an Excel workbook), sometimes the Excel (non full screen) window will open over the top of the Safari full screen window. When that happens it's impossible to get access to the Excel window, as clicking on it will jump to the desktop "space" (where the window should have opened?). The only way out of the problem is to move to the Safari full screen "space" and take Safari out of full screen mode using the button in the top right corner (Esc doesn't work in this case). After that I can access both Safari and the Excel window no problem.
    This doesn't always happen, but it has happened enough times to be annoying, and also happens with other apps (eg Preview), not just Excel.
    Anyone else had the same problem?

    It is a bug. If you start to search for something with the Safari not in full screen mode the history and predictive search functionality is there. If you then expand the application window to full screen it the search field will continue to work as expected. However, if you open the application and first expand it to full screen view before using the search field it will not work properly; the history will be inaccessable and the predictive search will fail.  In order to restore functionality, hit 'control+command+F' to return to non-full-screen mode, type something in the search field or access your search history via the hour glass and then return to full screnn mode. The search field will now function normally again. This is definitely a bug and this behavior explains why the search seems to be fixed at times, and broken at others.

  • IPod Nano Screen Lock bug

    I think I have discovered a bug in the iPod Nano software. I'm using the latest software available as for today.
    I lock the iPod Nano's screen and as expected, the graphical display of a combination lock appears. I insert the iPod Nano on to the Universal Dock and then proceed to control the Nano from the Apple Remote. It works partly. I am able to pause and play music and after a song finishes, it goes to the next one. I am not, however, able to fast forward, rewind, or skip tracks. I am able to play and pause, plus the Nano goes to the next track automatically after it finishes play the current one.
    Seems to me a bug! I would imagine that the screen lock is supposed to lock all kinds of control to the iPod except entering password.

    connect it to itunes and it will unlock

  • 24" iMac Screen Brightness Bug and others

    Hi,
    There seems to be some serious issues with the 24" iMac. About 6 days ago I bought a 24" iMac (2.66 Mhz model w/4 GB RAM + 640HD).
    Out of the box it had Leopard 10.5.5 installed; there were several problems.
    1. Screen brightness was way too BRIGHT. Display preferences would not pull brightness down. At least not down far enough so that the screen could be viewed without extreme discomfort. Plus add insult to injury a reboot would reset the preferences to maximum brightness. NOTE: An upgrade to 10.6.1 did NOT fix the issue.
    2. Viewing a browser page via either Safari or Firefox (latest versions of each) was not good. A vertical scrolling would be jumpy and appear pixelated. Upgrade to 10.6.1 seemed to fix most of the issue in Safari, but Firefox was still not working properly. The issue appeared like a horizontal "ripple" in about the bottom 2/3 of the browser window. The effect did NOT extend outside of browser window. Changing screen resolutions did not work.
    3. Connecting a USB Logitech head set caused issues with Sound preferences.
    If the head set was connected during startup the machine would recognize them as main sound. The internals speakers did NOT appear in the Sound preferences. as an optional choice. Removing USB headset and reboot would return the internal speakers to the Sound preferences. Plugging in headseat would work for a while. We could repeat and same problem would occur.
    These are all in 10.6.1 - definate bugs.
    Returned with the iMac to the Apple store. Bottom line, after nearly three hours; the Apple technician, and everyone could see what we were talking about.
    Regarding the screen brightness. Nothing they could do about it. They stated that "not too many people have complained about it, to their knowledge." They stated that the electronics in the "florescent" panel could not be turned down the same way. TRANSLATION: The programers at Apple let this one slip past them. As a customer (software programmer & network analyst) I expected a bit more of an intelligent answer.
    However.
    Examining the 20" model I noticed that we could turn down the screen brightness - at least to a level that my wife and I could live with. PLUS the settings remained after a restart. Something that was NOT happening with the 24" model.
    So - we exchanged the 24" for a 20". Frankly we are a LOT happier. The Safari/Firefox issue is still carried over to the 20". However it is not nearly so noticable on the smaller screen.
    Plus the USB headset did not cause the same Sound Preference issues.
    So - Thanks for the speedy return/exchange of the iMac. But someone needs to look at this from the programming side of things.

    HI, in response to 1_pixelperson, we've returned TWO iMacs with 24 inch screens, both so bright our eyes bugged out ... the current 20 inch is our third computer in 8 days ... he reported specifics
    We did find a SCREEN DIMMER app <www.adpartnership.net/DarkAdapted/> ... no solution via Apple ... iPhoto migration funky, dates out of sync, not valid, but thankfully Time Machine really works ... Firefox remains wobbly, not smooth ...
    Also, be careful when loading pics from phone with Bluetooth, it sucked my entire address book into my phone.
    People at Apple store were nice, today's 20 minute scheduled Genius meeting morphed into two hours+ ... including return ... would have preferred 20 inch with larger HD, came with 320 ... they couldn't do, upgraded ram while there.

  • System Preferences Screen Saver Bug

    I recently purchased a new iMac running Mountain Lion (previous computer was first gen intel Macbook Pro running Lion) and have noticed that a bug that persisted on my previous computer now exists on my new one!
    Essentially, when I browse to the Screen Saver Tab in System Preferences, it says "There was a problem connecting to the server X" which was an old networked computer (which has never been mapped ever to my new iMac) and the prompt refuses to go away until I close system preferences.
    I have restored my Pictures, Movies, Music using my previous time machine backup (no migration assistant used) and selecting the previous volume... but I don't know how that would cause the following? (See image):
    Any assistance would be greatly appreciated!

    FIXED IT!!!
    Ok - so in case anybody else suffers this problem it turned out the iPhoto Library was referencing a folder of files on a (non existant) other computer. This explains why:
    1. It always happened when I went into Wallpaper prefs (was looking for these non existent photos)
    2. It didn't appear in Disk Utility (because it was within the iPhoto Library package itself (i.e. the database)
    3. It happened on a new computer as the iPhoto library was restored from a previous computer.
    In order to find this, I troubleshooted by moving the iPhoto Library to desktop (without opening it) and wall/screensaver prefs worked fine. Then, I used terminal and the grep command (screenshot attached) to find where it was referencing "kitch_n_stage" (I.e. the windows share). Then I moved those files to the trash, but the iPhoto library back and opened iPhoto. It had to rebuild the database as I removed the photos folder and the library.adpb file.
    The command was grep -lr "name of shared computer" *
    (Would suggest backing up your iphoto library before doing this)

  • How to squash a nasty screen blackout bug

    Hi Mac experts,
    I've been trying, without success, to squash a nasty Mac bug that causes my screen to black out during work or causes it to never wake up after sleep, the latter being more frequent. It's supremely annoying since it interrupts work a couple of times a week and, embarrassingly, happens more often during public presentations, possibly due to the 2nd screen. In some cases a single hard reset revives the MacBook, in others I have to reset several times for the screen to become accessible again. When the bug happens, the OS is still running (key feedback sound, keyboard backlighting can be adjusted) but the screen is completely black.
    It's been an unfixed bug through several OS versions from 10.8, 10.9, to the latest 10.10 (Yosemite). The usual remedies suggested in forums did not work (see below). I'm out of ideas here, hopefully you are not.
    My specs: MacBook Pro Retina 15'', purchased 2012.
    My recent crash reports can be viewed here: https://drive.google.com/folderview?id=0B_EEMeI_SbKxMlZSVHhXdm1QZWs&usp=sharing
    I have tried the following:
    udpates did nothing; crashes under all OSs (10.8, 10.9, 10.10)
    reinstalled 10.9 fresh and migrated my data; still bugged
    startup in Safe mode (disables kernel extensions); crash on the same day
    adjusting the energy prefs (disable switching, deactive all additional wake up conditions); did nothing
    SMC and NVRAM resets did nothing
    This is a bug shared by many users. Apple obviously is not fixing it. One user reported that in his specific case it wasn't a hardware issue. Replacing the motherboard did nothing (http://bit.ly/1E5cEAR). Here are some related reports:  forums.macrumors.com/showthread.php?t=1722832 (2014-4; solution: detaching from ext. screen before sleep), discussions.apple.com/thread/6014780?start=0&tstart=0 (2014-03; not resolved), discussions.apple.com/thread/5665501 (2013-12, not resolved), discussions.apple.com/thread/5548226 (2013-11 to 2014, not resolved), forums.macrumors.com/showthread.php?t=1553654 (2013-03; solution: removal of Bresink driver), bit.ly/1wdVO1C (2012-8, problem w Bluetooth, fixed by OS update 10.8.1),..
    I hope somebody has a suggestion. Looking forward to your expert insights.
    All the best

    skywalkr,
    Have you taken some screen captures of the trap and dump information?
    ThinkPads: S30, T43, X60t, X1, W700ds, IdeaPad Y710, IdeaCentre: A300, IdeaPad K1
    Mark Hopkins
    Program Manager, Lenovo Social Media (Services)
    twitter @lenovoforums
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Screen drawing in as3

    Hi
    In my latest project im trying to have the player draw on the screen and that the line he drew will fade out form the end to the start
    i've done an animation to explain what im trying to do im your still confused
    http://www.swfcabin.com/open/1307457211
    off corse i wnat this to happen totally through the code with no animation involved
    what i have so far is the drawing mechanism, whenever the player presses down and moves the mouse the it draws a line on the screen,
    but i dont have a clue on how to erase it afterwards and that it will look cool like in the animation.
    here's the code:
                   stage.addEventListener(MouseEvent.MOUSE_MOVE, DrawMouseLine);
                   stage.addEventListener(MouseEvent.MOUSE_DOWN, MouseDownHandler);
                   stage.addEventListener(MouseEvent.MOUSE_UP, MouseUpHandler);
                   addChild(lineDrawing);
              function MouseDownHandler(event:MouseEvent):void
                   bDraw = true;
              function MouseUpHandler(event:MouseEvent):void
                   bDraw = false;
              public function DrawMouseLine(event:MouseEvent)
                   if (bDraw)
                        lineDrawing.graphics.moveTo(last_X,last_Y);
                        lineDrawing.graphics.lineStyle(4, 0xff9933);
                        lineDrawing.graphics.lineTo(mouseX, mouseY);
                   last_X = mouseX;
                   last_Y = mouseY;
    i did something similar in C# with a queue, i saved the locations of the mose movement , and on every frame drew the whole queue of points and discarded the last couple of points however in as3 this is not possible nor right to do.
    i really hope you can help me

    Try the code below. It is perfect but just illustrates a concept.
    Timeline code:
    import flash.display.Graphics;
    import flash.display.Shape;
    import flash.display.Sprite;
    import flash.events.Event;
    import flash.events.MouseEvent;
    import flash.geom.Point;
    var lineDrawing:Shape;
    var lineWidth:Number = 150;
    var lineHegith:Number = 4;
    var begin:Point = new Point();
    var end:Point = new Point();
    var conversion:Number = 180 / Math.PI;
    init();
    function init():void
         drawLine();
         stage.addEventListener(MouseEvent.MOUSE_DOWN, mouseDownHandler);
         stage.addEventListener(MouseEvent.MOUSE_UP, mouseUpHandler);
         addChild(lineDrawing);
    function drawLine():void
         lineDrawing = new Shape();
         var g:Graphics = lineDrawing.graphics;
         g.beginFill(0x000000);
         g.moveTo(-lineWidth, 0);
         g.lineTo(0, -lineHegith * .5);
         g.lineTo(0, lineHegith * .5);
         g.endFill();
         addChild(lineDrawing);
         lineDrawing.scaleX = 0;
    function mouseUpHandler(e:MouseEvent):void
         stage.removeEventListener(MouseEvent.MOUSE_MOVE, drawMouseLine);
         addEventListener(Event.ENTER_FRAME, removeLine);
    function removeLine(e:Event):void
         if (lineDrawing.scaleX > 0) lineDrawing.scaleX *= .03;
         else removeEventListener(Event.ENTER_FRAME, removeLine);
    function mouseDownHandler(e:MouseEvent):void
         stage.addEventListener(MouseEvent.MOUSE_MOVE, drawMouseLine);
         removeEventListener(Event.ENTER_FRAME, removeLine);
         begin.x = mouseX;
         begin.y = mouseY;
         lineDrawing.scaleX = 0;
    function drawMouseLine(e:MouseEvent):void
         end.x = lineDrawing.x = mouseX;
         end.y = lineDrawing.y = mouseY;
         lineDrawing.rotation =  Math.atan2(mouseY - begin.y, mouseX - begin.x) *  conversion;
         if (lineDrawing.scaleX < 1) {
              lineDrawing.width = Point.distance(begin, end);
         e.updateAfterEvent();
    Doc class:
    package
         import flash.display.Graphics;
         import flash.display.Shape;
         import flash.display.Sprite;
         import flash.events.Event;
         import flash.events.MouseEvent;
         import flash.geom.Point;
         public class MouseDrawing extends Sprite
              private var lineDrawing:Shape;
              private var lineWidth:Number = 150;
              private var lineHegith:Number = 4;
              private var begin:Point = new Point();
              private var end:Point = new Point();
              private var conversion:Number = 180 / Math.PI;
              public function MouseDrawing()
                   init();
              private function init():void
                   drawLine();
                   stage.addEventListener(MouseEvent.MOUSE_DOWN, mouseDownHandler);
                   stage.addEventListener(MouseEvent.MOUSE_UP, mouseUpHandler);
                   addChild(lineDrawing);
              private function drawLine():void
                   lineDrawing = new Shape();
                   var g:Graphics = lineDrawing.graphics;
                   g.beginFill(0x000000);
                   g.moveTo(-lineWidth, 0);
                   g.lineTo(0, -lineHegith * .5);
                   g.lineTo(0, lineHegith * .5);
                   g.endFill();
                   addChild(lineDrawing);
                   lineDrawing.scaleX = 0;
              private function mouseUpHandler(e:MouseEvent):void
                   stage.removeEventListener(MouseEvent.MOUSE_MOVE, drawMouseLine);
                   addEventListener(Event.ENTER_FRAME, removeLine);
              private function removeLine(e:Event):void
                   if (lineDrawing.scaleX > 0) {
                        lineDrawing.scaleX *= .03;
                   else {
                        removeEventListener(Event.ENTER_FRAME, removeLine);
              private function mouseDownHandler(e:MouseEvent):void
                   stage.addEventListener(MouseEvent.MOUSE_MOVE, drawMouseLine);
                   removeEventListener(Event.ENTER_FRAME, removeLine);
                   begin.x = mouseX;
                   begin.y = mouseY;
                   lineDrawing.scaleX = 0;
              private function drawMouseLine(e:MouseEvent):void
                   end.x = lineDrawing.x = mouseX;
                   end.y = lineDrawing.y = mouseY;
                   lineDrawing.rotation =  Math.atan2(mouseY - begin.y, mouseX - begin.x) *  conversion;
                   if (lineDrawing.scaleX < 1) {
                        lineDrawing.width = Point.distance(begin, end);
                   e.updateAfterEvent();
    I added e.updateAfterEvent();

Maybe you are looking for