Gvim - slow redraw

Hello!
Since 3 weeks of updates, gvim from testing has been redrawing the screen very slowly, especially after resize of the window.
The problem lays probably in cairo, because with cairo-ubuntu and cairo-ubuntu-xcb gvim works flawlessly.
Does anybody encoutered the problem or maybe know what ubuntu patches actually do?
If that matters I'm using nvidia proprietary driver;

Sounds like the same problem I have/had,
https://bbs.archlinux.org/viewtopic.php?id=138942
I filed a bug report at freedesktop.org.
https://bugs.freedesktop.org/show_bug.cgi?id=48395
If your problem is the same as mine, it lies in the nvidia driver. It has been fixed, but the fix is not available yet afaik. I haven't checked testing though. In my case it is only a problem when I use bitmap fonts, so for now I use another font. I also tried qvim for a while, but that didn't work so well for me.
Last edited by FreeTheBee (2012-04-17 18:41:33)

Similar Messages

Qt applications over ssh tunnel: very slow redrawing

Regularly I do not use many Qt applications, mostly Skype. I run it over ssh tunnel from another computer within the same local network for long time. After recent system update I noticed it became very slow refreshing its graphics. I checked several Gtk and Qt applications and found that Gtk ones work almost with the "native" speed, while Qt ones with that damn slow redrawing...
I tried ssh with both "ForwardX11" and "ForwardX11Trusted" - there is no difference. I'm using no DE with xmonad WM (tried TWM - no difference either) in x86_64 box.
Any directions/advices/ideas?
Thanks!

Regularly I do not use many Qt applications, mostly Skype. I run it over ssh tunnel from another computer within the same local network for long time. After recent system update I noticed it became very slow refreshing its graphics. I checked several Gtk and Qt applications and found that Gtk ones work almost with the "native" speed, while Qt ones with that damn slow redrawing...
I tried ssh with both "ForwardX11" and "ForwardX11Trusted" - there is no difference. I'm using no DE with xmonad WM (tried TWM - no difference either) in x86_64 box.
Any directions/advices/ideas?
Thanks!

CS4: Super Slow Redraw on Windows 7

Hello all,
Photoshop is running very slowly, even with tiny files (50k). I haven't had the need to run large CMYK files as yet, but I am guessing those will drastically slow the already molasses-like redraw. When I say redraw, it's actually the rulers that are taking the longest to render, after which the actual artwork appears.
Photoshop settings:
Photoshop is using 75% of my system's resources
'Available RAM' = 1603MB
'History States' = 30
'Cache Levels' = 4
Compatibility = Windows XP (Service Pack 2)
Windows Settings:
Virtual memory: check (per Adobe's instructions)
Scratch Disk: check
'Enable Open GL Drawing': check (off)
Hardware:
Dell Optiplex GX 620
Intel 3.00GHz
4.00GB RAM (3.5GB usable)
32-bit OS (Windows 7 Ultimate)
I did not experience any problems installing Windows 7 or CS4. Neither crash or are glitchy in any other way... I spend 90% of my work day in PS, so it is mandatory, for my personal sanity and productivity, that PS run as fast or faster than when installed on XP.
I've attached screen captures of my PS preferences/performance and the Windows 7 basic info dialogs.
Your help is appreciated!
TIA,
Mark

All, thank you for your replies. I apologize for the delay in responding - I have been swamped.
dec9 wrote:
Change your scratch disk to D drive.
Update your video card drivers.
your video card not up to snuff with opengl?
also why are you running CS4 in XP service pack 2 mode for?
There's plenty of space on the C drive and that's the drive PS is installed on... is there a reason I should change to D?
Video card drivers are current, however, it's a 256mb unit. I went to my local Fry's and picked up a Radeon 4670 and 500w power supply only to find that both are too big for my Dell Optiplex. Argh! Now, not only am I still lagging a little (read below for the semi-solution), but I have to stand in that dern Fry's 'returns' line.
I was trying all the different compatibility options hoping one would resolve the issue...
Thanks again for your input.

Tons of Script Errors and Slow Redraw

I recently setup CS 5.5 with Bridge 4.1.0.54 on a new MacBook Pro.
When I launch Bridge I get the following messages:
I'm confident of a few things. First, it's obviously somewhat related to this issue:
http://forums.adobe.com/message/3083307
Second, it has nothing to do with CFS or Samba shares.
Lastly, the error has something to do with the output module script- if I startup without it on, no errors.
Currently I have my MBP setup with two drives. A SSD for the system software and a second SATA drive for content. All my system software is on the SSD boot drive, however, my users folder is split between the two. Everything but ~/users/xxx/library is symbolicly linked on the second drive.
If you look closely at the thread referenced above, all the errors are the same except for the "could not create" error. In the thread, it lists a specific user, my error lists Volumes/Null/...
Here is what I've tried so far:
Reset the app
Trashed the prefs
Started up w/o scripts
reinstalled the entire CS 5.5 Suite after Uninstalling and using the cleaner tool
To add insult to injury, When the output script is off and bridge does load, it does it painfully slow to the point where it is not usalbe. It is also having a ton of redraw issues.
Any advice?

I think I may have found a workaround.
I've been racking my brain over the past few days to figure this one out. I've tried at least a dozen permsissions fixes, both through the apple utility and manually. I've reinstalled both bridge and CS 5.5 three times using the cleaner script and a fresh install. NOTHING.
So I went back to the original error message:
One thing I noticed was that everytime Bridge was starting, it created a folder in /volumes called "null". I checked three other macs setup the same was as mine and NONE of them created this folder during bridge startup.
I still have not figured out why my laptop is doing this.
However, I looked at the error and it seemed that bridge was looking for a path that didn't exists, which was /volumes/null/Adobe/Adobe Bridge CS5.1/Adobe Output Module/Mediagallery
the path Adobe/Adobe Bridge CS5.1/... is the same path as my ~/library/application support/... folder for adobe.
First I created a regular alias to that folder to create the fake path. No dice. Then I tried a symlink to creat the fake path /volumes/null/Adobe/Adobe Bridge CS5.1/Adobe Output Module/Mediagallery
Voila. Worked like a charm. I can now start up Bridge without any errors, script errors, etc. I also have all the functionality of my Output panel back and I'm able to use it without getting the insufficiant disk space error.
Now to figure out why Bridge is creating a "Null" folder.

Very slow redraw

Hi - this video shows Photoshop CS4 (without Open GL enabled - since it's completely useless with a fully updated Nvidia 7300) trying to hide and show guides on a simple image.
This has to be the first time since my old IBM that I'm the one waiting for the computer to finish.

Well If I was that update, I'd be pissed for only giving me a .0.1 status. I may not be a full version update like the big guys, but it sure would have been nice to be a respectable .0.5
Thanks, worked like a charm.

IPhoto slow redraw compared to iBook

Well, I'm going from a 1.2Ghz iBook G4 with 1GB ram to a 1.8Ghz MacBook CoreDuo with 2GB ram... I imported my user account using the utility and couldn't wait to see how iPhoto performed. On the iBook, scrolling through the library thumbnails was pretty smooth.. however when I scroll up/down on the MacBook, the thumbnails look blurred for a second.. then clear up.. like there's a little delay procesing the image. Also the color shifts a little when they clear up. Does anyone else experience this? Does this have anything to do with the MacBook not having a dedicated graphics card?

Possibly. Tried trashing the prefs? My iPhoto library is pretty snappy.
I have files of around 6MB too. Sorry I can't be of more help but at least you feel like there's someone here!

GVim 7.2.368-3 cursor bug

Hi all. After I upgraded to the latest version of Vim a couple of days ago, I started experiencing what looks like gVim cursor redraw bug. When I move the cursor in gVim, it obstructs the letter it is on:
I do not experience this in plain Vim. There are things that can make the cursor exhibit normal behavior, such as 1) me pressing Esc key 2) Awesome WM clock updating 3) scrot taking a screenshot (I had to Gimp the screenshot above because the cursor goes back to normal the moment a screenshot is taken).
Vim and Xorg packages were upgraded during my last update, but Awesome WM was not.
Is anybody else experiencing this? How should I go about finding the culprit?

jichuan89 wrote:
I am getting the same bug here. However, it only seems to occur when I use bitmap fonts like Dina or Terminus. Using a TrueType font like Courier New or Nimbus Mono works perfectly. Confused
This seems to be a bug specific to the intel driver for X11. When I reboot the machine and switch to my discrete ATI graphics card (my laptop has dual integrated/discrete graphics cards) the problem disappears completely. Also forwarding Vim through SSH from this laptop to other computers works as well. Could you confirm this? What X11 video driver are you using?
Thank you for pointing this out. I have changed the font and now the cursor works again. Hope this bug will be fixed soon. I am missing my dina fonts.
Last edited by ArchArael (2010-03-16 08:16:24)

Premiere Elements 11 + Windows 8 pro = slow timeline scrolling!

Hi!
I experience slow redraw of the timeline clips when I scroll,
which makes it very difficult, slow and unpleasant to edit!
This in nothing new to you all, as I have read in many posts about this problem!
And everyone is asking (below these posts) questions like:
"do you have the latest QuickTime codecs?" or "do you have the latest graphics drivers?"
or that our pc are slow or that we work with strange video formats or to change to no thumbnail in the clips or that its
the antivirus fault or whatever.
It is not all these!
As I have read:
-It can happen in many versions of Premiere Elements(maybe in all of them, I don't know)
-It can happen in both ATI/AMD and NVIDIA graphics cards
-It can happen in all hardware configurations CPU/motherboards
-It can happen in all windows versions and both 32/64 bit
So I am guessing it is not our fault.
Can Adobe finally fix this problem with an update? It's been so many versions until now!
please... Is it so difficult?
Can't the programmers see what are we talking about? Can't they fix the programme?
Before I bought Premiere Elements 11 I had the 9 version in windows 7(64bit)
The same problem, slow/laggy timeline redraw when moving back and forth.
The solution I found was to disable the Aero feature in windows 7!
And oh my god... the timeline then was so fast and smooth, I was so happy to edit!
So I compromised with that(disabling aero).
Recently I have upgrad the same PC to windows 8 pro(64 bit) AND bought Premiere Elements 11. (hoping for speed in every possible way!)
The slow timeline scrolling still happens in both PRE9 and in PRE11.
And guess what? in windows 8 pro you can't disable the "aero feature"!!!
You can only change some visual settings, and even if I disable all of them, nothing changes!
So are we really stuck with the laggy timeline scrolling in windows 8???
Premiere Elements 11 is so much faster in all other things (exept the timeline scrolling)
In the preview window for example. It can play really smooth, in real time WITHOUT render preview
some pretty difficult compositions I make! multiple layers, with greenbox and many other filter effects!
Which in Premiere Elements 9 (in the same PC) the preview play was very laggy!
(don't forget that with aero disabled in PE9(win7), same PC, same complicated compositions, timeline scrolling superfast!)
I think they made some pretty good graphic card use in the preview play in PRE11!
I present and edit a youtube show with Premiere Elements with demanding compositing and everyone thinks I use Premiere Pro CS
version or After Effects CS. But I don't, I want to be legal and I can't aford the prices of these applications
so I buy and use the Elements series which are very powerful as well, if you know what to do and HOW to do it!
See for youselves my show I posted today(in Greek, I am from Greece), which I edited in PRE11.(pefrect greenbox, perfect!)
http://youtu.be/HdKAKI6P8tU?hd=1&t=1m28s (open in a new window)
or move time to 1:28 from the below youtube video window.
But unfortunattely the timeline scrolling made my editing unpleasant and slow!
My question is: Will I, (now that I have upgraded to windows 8 pro 64bit) have to edit ALL my next shows/videos
with the slow/laggy timeline scrolling??? please tell me something to hope for...

I have an ATI/AMD FirePro v4800 1GB GDDR5 with the latest drivers for this card (8.982.8.3)
Is my video card not compatible?
this slow redraw of the timeline happened way before
and everytime a new driver version came up I had installed it but that didn't change anything.
Only with aero disabled I would enjoy a fast timeline scrolling in windows 7. (now, not possible in windows 8 pro)
Bill how can you explain this? Same video card and everytime with the SAME NEW drivers, aero on=slow timeline, aero off=fast timeline!
Is there some kind of a fix that we can always wait from our graphics card companies to include to new drivers??? (for how long???)
or maybe is it all up to Adobe and its own programme?
Are we all supposed to have old video display drivers?
Can someone make some kind of a poll for people who have this problem to vote to see where this problem apears, in which configurations, in which graphics cards? (assuming they have latest drivers)
so we all finally know what/where is the problem.
I love the premiere elements series and thats why I want this to be solved.

Windows 8 - Slow Quicktime Prores Performance - Timeline delay

Hello all,
I am a long time Adobe user. For a long llong time I used it solely on mac but recently have been slowly making the move to Windows for everything (previously just for fun).
Anyway I am having some issues getting quicktime to work well on Windows, even on the very same computer that the same project works fine in OS X. I know quicktime is "native" to apple and osx, but in talking to other windows users my experience isn't normal.
First, I am on Premiere Pro CS6 up to date, Windows 8 Pro (and os x 10.8.4), up to date, on a 2008 Mac Pro 8x 2.8ghx 16GB ram, with a gtx 680 (4gb). GPU drivers are also up to date. I use eSet Smart Security for my antivirus. I have made sure that my project/media drive as well as the ssd I use for the media cache are ignored by the eset realtime scanning. Quicktime (pro) and the ProRes codecs are installed. Not a superstar rig but still a capable machine.
The project in question is a short compilation of stock footage. There is a total of 25 clips, the longest of which is 4 minutes, the shortest a few seconds. All are quicktimes, most are prores, some are photo-jpeg and there are a few other codes in there as well. All 720p or 1080p. They are edited down to about 1 minute in the timeline, using a 720p23.976 preset.
On my mac, everything is as expected. I can smoothly play back my timeline, and quickly open clips in the viewer panel. This is instant. Occasionally on the first open of a clip I will get a brief "media pending" screen but never more than a few seconds and only when the clip is first accessed.
In windows, however, there is a very long delay when choosing many but not all clips -- both to open in the viewer OR even just to select or scrub in the timeline. If I have my playhead parked on 1 clip, then move it to another, there will be a delay of anywhere from 5-10 seconds before I get an image. I can see my media cache showing some activity, and sometimes I get the 'media pending' screen during this. Audio uslly works during this time, but no image. If I leave the clip and come right back to it, it will be instant, but if I go to a few clips, when I come back there will be another delay.
It seems like something is going on with my media cache, but only in Windows. I have formatted and reset it to no avail. It seems odd that on mac it would "remember" that it has loaded clips from the cache but on windows it has trouble with the same clips and has to re-cache frequently.
I can try to get a screen grab of the behavior if it will help. I can say that I don't think it is isolated to ProRes because I have had this problem in the past with a project that only used animation clips. I haven't had time to try with a whole project, but I don't seem to have the same problem with avi's, but I need to stay cross platform for now and most people I work with use ProRes.

I have an ATI/AMD FirePro v4800 1GB GDDR5 with the latest drivers for this card (8.982.8.3)
Is my video card not compatible?
this slow redraw of the timeline happened way before
and everytime a new driver version came up I had installed it but that didn't change anything.
Only with aero disabled I would enjoy a fast timeline scrolling in windows 7. (now, not possible in windows 8 pro)
Bill how can you explain this? Same video card and everytime with the SAME NEW drivers, aero on=slow timeline, aero off=fast timeline!
Is there some kind of a fix that we can always wait from our graphics card companies to include to new drivers??? (for how long???)
or maybe is it all up to Adobe and its own programme?
Are we all supposed to have old video display drivers?
Can someone make some kind of a poll for people who have this problem to vote to see where this problem apears, in which configurations, in which graphics cards? (assuming they have latest drivers)
so we all finally know what/where is the problem.
I love the premiere elements series and thats why I want this to be solved.

Slowness in repainting and scrolling

OK. I probably know everything about repainting and paint that you know. Just trust me there :). so this isn't a newbie "why is my redraw slow" question. I am interested to hear from anyone who has noticed this or who, after reading this, notices that it explains their situation.
First I'll give you the symptom, then I'll give you the cure for the symptom then I'll ask about the disease, then present some evidence that it's not such a simple problem.
Symptom- very slow redrawing and scrolling.
Cure- stop running certain other programs which are essentially non-malware TSRs (Terminate and Stay Resident) programs. In my particular case, its FastStone's capture utility but I am pretty sure it's not specific to that program.
The disease- it only manifests itself while doing plain old launches from the development environment - in other words, write any simple GUI app in your development environment and launch it while running the TSR, as opposed to say, java programs like IntelliJ or Netbeans which have full installers etc. It does effect FreeMind however.
Some clues:
I have to say it's not the amount of memory, since the smallest GUI tester program run via a PSVM (public static void main) will elicit the effect and anyways my machine has a disgusting amount of RAM.
The effect of closing (or opening the TSR) is instantaneous. There's a clear cause and effect at work.
It does not effect Netbeans that I can tell nor IntelliJ (just to stay concrete). It devastates FreeMind and any stupid little GUI tester, as I said.
It does not effect non- Java programs.
So here is my thinking. Suppose there's something that windows programs can tap into- some resource, function call, whatever, that has the side effect (MS would never do this deliberately) of really undermining the Java VM in some way or forcing resources away from it.. it feels like a resource starvation scenario of some sort-- either CPU or RAM or thread priority or whatever.
On top of the why does this happen question, there's the why are some Java programs immune question. It makes me think there's something about the way those programs are installed or launched that's different from the plain old PSVM that makes them immune. AFAIK, PSVM is how things are ultimately launched in Java, period, after all the scripts and whatever have run.
So I am asking
does anyone notice this themselves?
is this a well known problem that other people know the solution to and understand?
now that I've described it in the way I have, does it shed light on any mysteries that anyone else has?
Really just trying to spark a discussion / line of investigation.
many thanks.

So here is my thinking. Suppose there's something that windows programs can tap into- some resource, function call, whatever, that has the side effect (MS would never do this deliberately) of really undermining the Java VM in some way or forcing resources away from it.. it feels like a resource starvation scenario of some sort-- either CPU or RAM or thread priority or whatever.
I love a good conspiracy theory as much as anyone, and MS being the butt of the folly makes it even better, but I don't think so. I have not noticed that my Java applications over the last 10 years have been affected any more or less than any "native code application" (such as those developed in C/C++ or .Net and compiled specifically for the MS environment.
On top of the why does this happen question, there's the why are some Java programs immune question. It makes me think there's something about the way those programs are installed or launched that's different from the plain old PSVM that makes them immune. AFAIK, PSVM is how things are ultimately launched in Java, period, after all the scripts and whatever have run.
I would have to say, some Java applications are immune probably because their structure is better for that specific environment.
So I am asking
does anyone notice this themselves?
My system degradations seem to be non-discriminatory and even several of the MS products suffer way more than any of the Java based applications.
is this a well known problem that other people know the solution to and understand?
now that I've described it in the way I have, does it shed light on any mysteries that anyone else has?
Not really, the MS bloat-ware that I run seem to suffer the symptoms you have described too. As do other companies' products equally.
I had part of the problem explained to me one time by a Senior Engineer from Digital, concerning OLE: You have a cooperative interface standard that asks one company to expose their proprietary interfaces so other companies can gain from their use. Not everyone will share nor will what they share always be totally accurate. It's just not viewed as being in their best interest to give it all away.

My CS4 seems to be running SLOWER on 64-bit. Any ideas?

I'm running:
AMD Phenom 9550 Quad-Core processor 2.20GHz
4GB Ram
Windows Vista 64
My graphics card: Dual SLI Geforce 9600 GT (1GB Ram)
I booted up CS4 last night expecting to see an amazing difference, and well I did. It ended up seeing slower redraw rates and it chugs when I pan through big images.
I have a feeling there's some setting that I'm not doing right. I updated my Geforce drivers.
In the Nvidia control panel, there are a ton of settings for the Photoshop CS4 applications that I've been playing with but cant seem to get a favorable solution. Anyone have an Easy Button for this?

That's assuming PS was build to not do it. Scratch disks and display tiles are a fundamental principle of the program and I don't consider them a workaround for anything. You know, over in the video apps forums we poor souls have been begging for years that After Effects would be half as smart as PS in that regard. I also tend to think that your alleged "do it all in RAM" would fall apart as soon as you begin to deal with a number of images and document sizes that exhaust that RAM. One might say that in foreseeable time RAM will be so dirt cheap, that 32GB machines will be commonplace even for home users, but it's not there yet. And then it's the question: Do I burn 1000 Watts of electricity even in idle state just to work on a monster machine with lots of RAM or do I use just 300 Watts on a normal system with a scratch disk and energy saving options. It's the same gag as with multicore processors or those monstrous graphics cards (Quadro CX, anyone?): the marketing may tell you, you need those things, but it must not necessarily do anything for your personal workflow. Those arguments really have no value if this Quadro CX has nothing to do most of the time or of 16 cores only 1 barely even peaks while you paint and likewise you wouldn't need those tons of RAM, if all you ever do is adjusting a few photos from digital cameras. You have to differentiate between "average" users and extreme "power users", but nowhere is it written that 1% of power users must or can dictate what's good for the 99% other users, a dilemma software devs face every day... I would tend to think that 64bit and its possible advantages are in fact very low on the list for those 99% of users, but other things are much more important to them.
Mylenium

Photoshop CS4 - new report, old problems

Hi there,
although i have posted many of the following problems in another thread, i will recall them here, because the other thread has gone slightly off-topic.
I have been "using" Photoshop CS4 that came as part of my Production Suite Premium Package for as long as it is out now and i have to say, that for me it is the worst release ever.
I work with Photoshop since Version 3 and every new release has had it's flaws that were fixed after a while. So i really hope this might also be the case with CS4.
So here are my System Specs again:
Intel Dualcore E8600
NVIDIA Geforce 9800 GX2 (Driver: 180.48)
MSI P35 Neo-2 Motherboard (Bios: 1.90)
3 GB RAM
Wacom Intuos 3 A4 (Driver: pro610-5)
Windows XP (Service Pack 3)
The System is brandnew, the Windows-Installation is fresh, before the CS4 Suite there has not been another Adobe-Program on the machine.
While I am quiet happy with the other programs (Illustrator, Flash, After Effects..even Bridge is starting to become useful), Photoshop CS4 shows several glitches and problems on my system. These are:
- If activated, the GPU-OpenGL setting deactivates randomly. There's no obvious reason for this, just in the middle of work, the rotate canvas-tool is no longer available, zooming is no longer smooth. While the box in the preferences is still checked for OpenGL and my graphics-card is recognized correctly, OpenGL features just stop working. After I close and restart Photoshop everything is normal again, until the next time settings are deactivated.
I am so far not able to trace the reason for this behavior, seems to happen quiet random.
- No "marching ants". In the same matter, the "marching ants" of selections sometimes disappear. While this is not a big problem I think i should note it here for reasons of being accurate.
- Brush tool stops working. I have this quiet a lot. While I paint, the Brush suddenly stops working completely. It produces neither strokes nor blotches anymore. In some cases hefty drawing can result in some strange straight lines but the brush tool can only be revived by restarting Photoshop.
- Crashes. I truly honestly haven't had a crash with CS2 and CS3 ONCE. With CS4 crashes seem to be quiet normal at this point. The application simply freezes, mostly while using the transformation tool. Killing it via the windows task manager is the only option.
- Slow redraw. All the above mentioned problems did occur with OpenGL enabled AND disabled. It really makes no difference. So deactivating this new thing doesn't convert Photoshop back into something useful, but into a slower version of CS3. Redraw of images is considerably slower on CS4 without OpenGL, than it was on CS3, although it gets better after some time working with it. Moving a maximized Image around feels very strange, because the build up of the tiles is somehow slow and sluggish.
- Features I used are no longer there or no longer functional. I use Layer-Comps a lot. With activated OpenGL the Script "Layer Comps to Files" does not work. It produces an error-message that reads:
Error 1: Unable to create Window - OS error (1400) Line: 234 -> dlgMain = new Window("dialog", strTitle);
With OpenGL deactivated it suddenly works... no idea why.
In addition some features like the automatic web gallery creation have been removed from Photoshop, but i figured out how to get them back.
While these are the really bad things about the new version (on my system that is, I heard from Mac-Users who are quiet happy with PS CS4 and keep telling me how fast it is on a Mac.....) there are other things, that i don't understand. I reckon, Photoshop cs4 is first of all a Mac-product and the PC-Version is somehow adapted or converted.
Proof of this for me is the new window behavior. Windows steeling focus and blocking sight on palettes is new for a long time PC-User like me. I also don't understand, why maximizing an image does fill the complete screen thus exterminatin

While I can not help remedy your problems, Pickman, I can tell you I have mostly the same problems as you. I am not the only one either. I hear this from my students. Marching ants disappearing is normal now, palettes hiding behind windows seems common nowadays. Photoshop losing focus, a document suddenly refusing to be the front one and having to minimize the other document(s) to have it back, lasso tool suddenly not showing it's tracing mark, it's all horrible. The error 'unable to create window' is very common.
I didn't even mention the fact that it's no longer possible to downsize the Photoshop window by it's top edge, which is utterly annoying when you have multiple windows open as I often have or the fact that when I scale the main Photoshop window, the documents stay in place and that the tooltips often don't work which is confusing for the novices that I train. I thought they had remedied that in CS3, but it's back in CS4. I have been using Photoshop since version 3 (briefly) then 4, 5 et cetera. This is one of the worst releases ever.

N97 v12 and 5800 v30 .. YAWN

You see, I have to say 'YAWN' because when I actually yawn, you don't get it do you Nokia..
Two phones. Both bought directly from Nokia "sim-free".. BOTH stuck on the old firmware.. how old is the 5800 v30 firmware now? 3 weeks old?
I'm hopefully getting my hands on a Sony Ericsson Satio in the next few days. A Symbian phone from another Vendor! Hopefully I'll see how a competitor to Nokia might've managed to have released a phone on the same platform that does not suck so unbelievably...
Get a move on with your mind numbingly convoluted release cycle with its secret change log and even more secret release dates..
Still no Mac support for the N97, ey... tut.. no chance you could add the USB Id's of the N97 to the existing Mac software so it would just work? I doubt very much it requires a code change and lets face it.. what's the worst it'd do.. break the phone and I'd need to *#7370* it? ooooooh.. not for the 85th time then?!
grrrrrr

Just follow up.. I did play with a pre-release satio at the weekend and I have to say it's actually pretty nice!
The screen is much more shiny than the N97 sort of like comparing a matte and gloss laptop screen.
It feels a little bit snappier too.. I put this down to a lack of theme effects (which were disabled. The screen rotate with the theme options turned off was "atomic" rotate the phone and almost immediately the screen swapped.. no slow redraw or fade to black..
The home screen was obviously very different and geared towards the SE look and feel but the main menu app felt almost identical to the N97. To be fair, the phone felt a bit more like a 5800 than a N97.
Size wise it is very similar, thinner but that would be down to the N97 keyboard.. It is certainly larger than the 5800. No micro USB.. that's a bit odd.. perhaps it will change in the final release? I thought SE was in on the standardising connectors effort.
It had a google maps app, but not much else GPS wise.. This I think was down to the fact it was really pre-release..
The camera (12.1mp) was phenominal, but what do you expect.. The slide on the back does look a bit like a blister.. but it does an infinitely better job of protecting the camera.. the flash is xenon too.. and shares no flat plastic for that **bleep** bleed problem (maaan. that really irritates me on the N97!) It has extra hardware buttons too.. more than the camera and volume. Although they're geared towards media functions, I'm sure that could be helpful when trying to map functions (like missing pencil button, for example)
On the whole, I was actually really impressed. I loved playing with the R&D tools Neat for looking around the parts of the OS that are hidden. It didn't have a file manager app so I couldn't tell you how much free memory it has.. I've asked for a follow up on that (especially as my N97 is back under 10meg again .grrrrr)
Compared to the rather old 5800, I *think* I'd prefer the Satio.. however.. the N97 and its keyboard (albeit a keyboard without a damn control key!!! COPY AND PASTE DAMN IT!) still beats it on the hardware stakes.. (asides from the **bleep** keyboard cover does and the loose screen/vibrate does anyone dislike the N97 hardware?)
Software wise, it was really very stable! At no stage did it play the Nokia ring tone instead of the ring tone set in the profile
What was really great was seeing yet another Symbian phone.. Forgetting the PC software (which really isn't of much interest to mac user's anyway.. the mac user base is large.. considerable larger than say the N97 userbase! Nokia, stop ignoring or atleast update your mac software!) the phone is a really usable symbian phone. For the day to day, stock symbian stuff you'd hardly notice the difference.. I'm not sure Nokia or SE would be please about that fact, but as a Symbian fan.. I'm really pleased
The software on the phone suggest that some of the N97 bugs are Nokia bugs.. This is good because it puts the blame at Nokia's door.. by that I mean Symbian aren't to blame, its what Nokia do that's causing a problem..
As more and more Symbian handsets are released and if Nokia don't fix their attitude to testing this will become more and more apparently.. the good news for the Symbian fans out there is that you might now have a choice of vendors..

Why is my photo so pixelated?

I'm using a photo i took on my camera then edited in photoshop CS6 and i'm now trying to paste that photo into indesign but the quality is so bad. I've already changed the display performance and it made a small difference but not much.
The image is quite small but hopefully you can see the difference.

You can also change the way InDesign displays the image with View>Display Performance, where the default is Typical Display (low res), High Quality Display (better, but slower redraw) or Fast Display (gray outline of the image with no detail, but will scroll faster than typical). I usually leave it on Typical unless I need very precise placement of the image, and then I temporarily switch to High Quality, then back after the image is in position.

NB 6.1 and Google Maps

I've looked all over and can't seem to find tutorial on Google Maps for NB 6.1 There is tut for NB 5.5 but it can't be applied to NB 6.1 as Netbeans developers said themselves:
- No Support for Ajax Sample Components
- Google Map - Planned for futureI've tried to work with NB 5.5 but the tut for Ajax Map Viewer isn't working quite right and the map component is the reason.
Ajax Map Viewer component does not work properly under NetBeans Visual Web Pack 5.5.1.
    Description: The BluePrints Ajax complib needs to be updated and re-added to the project for this component to work properly.
    Workaround: To fix this issue:
       1. Update the BluePrints Ajax Components library from Update Center as described in Downloading and Importing Ajax Components.
       2. Remove the BluePrints Ajax Components library from the project: Under Component Libraries, right-click BluePrints AJAX Components (0.1.1) and choose Remove.
       3. Add the newly updated BluePrints Ajax Components library: Right-click Component Libraries and choose Add Component Library.
       4. Undeploy the web application.
       5. Stop the application server, clean and build the project, and restart the application server.
       6. Redeploy the web application. Tried it and now sometimes it works and sometimes it doesn't. Am I forced to abandon NB if I want to develop google map type of app?
Edited by: najob on Sep 5, 2008 3:46 AM

Hooo, speew, you are optimistic.
I've definitely got the problem: ultra slow redraw, takes up to 40 seconds to activate when you click on an action such as 'directions from here' in a contextual menu, takes 30 seconds for a route to be drawn, takes 10 seconds for a zoom change, and more. 10 seconds may not sound like a lot, but to give you a reference, 90% of voicemails left are only 4-6 seconds. Give it a try.
That's all without satellite view or any other services options turned on (hotels, show me etc)

Gvim - slow redraw

Similar Messages

Maybe you are looking for