Unfortunately, I can reproduce it on my side, running Vegas 6.0a (Build 99). I've never understood it. Select a font, hit the arrow key, sometimes it works and you can scroll for a few fonts then it stops, and sometimes (like my test a few seconds ago) it doesn't work at all. There's a chance it MAY have something to do with the font itself. When it stops on a font, I have to choose another font manually (mouse pointing to it) and that bypasses whatever font it got "stuck" on. Then you can arrow through them again. Vegas is the only one of my progs that does that.

The bug appears only when working with selected text in the text edit window.

Steps to reproduce

1. right click - insert new text media on timeline
2. select the word "sample" in "sampled text"
3. click the font name box (where you select the font)
4. press arrow keys down or up.

It wont move.

If you jump to a font with the mouse... for example you select tahoma with the mouse after step 4, you can only move up or down a few fonts using the up and down keyboard arrows.

I see someone responded before i did. Just wanted to comment that it has nothign to do with the font itself, because it only happens when you highlight a word or letter in the text edit window. You can otherwise step through fonts for unselected text just fine.

The key to this bug is selecting text in the text edit window and then trying to step through the font list with keyboard arrows.

I've noticed this behavior since at least Vegas 5.

John

confirming
Jackie_Chan_Fan 's observations here - arrow keys will not work on first try - and after mousing to a particulat font the arrow keys will only work for a few different fonts and then freeze again

OK . ..

If I DON'T highlight any of the text, then I can scroll through the Fonts Styles AND see the different styles "reflected" in the Text. If I DO highlight the text then style changes can't be done.

This I feel is counter-intuitive to what happens elsewhere in the Windows experience. For example, in WORD I can highlight the text and apply a different style. Same for WORKS and other Text manipulation s/w I know. This is NOT the case for V4, V5 nor V6. I suppose it is up to SONY if it wishes the user experience, regarding this "feature", to be the same as other MS s/w. Maybe I would question that this is an actual "bug" - more a design feature of the s/w. Having this "work" the same as other MS text manipulation would be neat, otherwise I can live with it.

Summary: I can repro this. Ditto V4 & V5. However I would question that this is a "BUG" though.

Regards,

Grazie

Grazie, its a bug. Its not by design :)

You can have multiple font styles within a text object in vegas... so why cant you "step" through the font list while having selected text?

It's a bug. It's been there since v5. Hell, they probably know about it but have defered it. (A common thing in the bug testing world of software developement)

You cant tell me that they purposely designed it this way :) It's either something that has gone overlooked, or it is something that is logged already as a bug but defered. Either way it's a bug. One of many.

JCF, I disagree.

If I have something working in a previous versions and now NOT working then I would regard that as a bug. OR if SONY states that something SHOULD work a certain way and now it does not then THAT is a bug.

Your, "You can have multiple font styles within a text object in Vegas... so why cant you "step" through the font list while having selected text?" only goes to reinforce what I am saying. You might want something to work in a certain way, but that does not make it a bug, that makes it a product request? Yes?

Hey, I would really like to have this work in V6! But I can confirm this in Vegas4 and Vegas5, and it now being in Vegas6 only goes to show that this is part of how Vegas treats text formatting.

My recent experience has been that my SteadyHand files that work to External Monitor from Trimmer and Explorer, in V4 and V5, now don't work in V6. Now that I regard as a bug. Yes?

Best regards,

Grazie


( Edited by G: . .seesshh my spilling was ribbish! )

When i worked as a designer of tools/features for Discreet... Generally you would log this as a bug.

It would be logged as a bug, then reviewed, and marked as ""As Designed", "Defered" "Legacy" etc

It may be "as designed" by reason of a programmer simply not adding in the functionality but it is certainly a bug.

Bugs lead to workflow improvements as well as stability improvements. Technically we're both correct. It's symantecs but the general nature of the "feature" not working consistantly is still a bug that would be logged as a bug for future design or immediate attention based on a severity rating.

The fact that you cant step through the fonts when highlighted is a workflow bug... by design or by neglect.

Certainly, the issue of highlighting text, and then mouse clicking a font name and then trying to step through the list... ONLY to be limited by about 4 fonts in either direction... is certainly a bug.

It's not as designed, as in "we wanted it to be that way" It may be "as designed" out of neglect, oversight, or simple deferment but It is a bug, as it does not conform and breaks workflow in irregular ways. Either way... if it is "as by design" or "bug" In the eyes of the QA department.. it is logged, and then reviewed. Hopefully that is the case... because it should be fixed.

And on a side note, i really wish Vegas would improve its ui so it did not look so windowzy ;) That is certainly not a bug .. but as designed ;) Perhaps it should be up for review next cycle ;)

Actually i would be happy with being able to just change the ui colors... such as the background colors of the general ui. I know you can do it by changing ALL of window's colors through window's themes etc but... it would be nice to darken up the ui a little ;)

(sorry random wish)

You certainly have a background in the development! Ho, I'm impressed!

. .and I still disagree.

Your, "ONLY to be limited by about 4 fonts in either direction... is certainly a bug." . . again, supports my case that THIS is in itself is the bug. Maybe you shouldn't even see this? Maybe the idea was that you should ONLY see 4 either way. See? I can argue both ways. But hey . .what do I know?

Best regards

Grazie

On the other hand, even if that is the way the programmers decided it should be, i can't comprehend a single benefit that it brings to the users. It is an annoyance and a workflow impedence. So, whether it fits the definition of bug or not, it's probably something that should be changed.

As far as Vegas being "windowsy", i feel this is one of it's greatest strengths! Almost anyone can sit down and start tinkering with it and immediately start accomplishing things. Why? Because they don't have to decipher the interface. Menus and controls are all layed out where people expect to find them. I've seen plenty of other software that has it's own custom GUI and the comments that i and many others always make is, "What did they do that for? it makes everything so hard to find!"

Remember that "elegant" does not always mean "beautiful". Elegance defines function as well as form. In this case, functionality is vastly more important than form.

"So, whether it fits the definition of bug or not, it's probably something that should be changed."

Of course I agree - a no brainer with that Kelly. I didn't disagree with that something SHOULD be improved - it's HOW Sony react to that which Users call a bug and that which they recieve as product request. I see the difference. Don't you Kelly? ok . . . .

Deciding that which is Form OR Function is in itself an elegant approach - but once observed is a thing of beauty!

Hey, Bertrand Russell had it right - eh?

Grazie

I have this behaviour as well and have noted that I can't continue scrolling through the fonts once a font "family" is encountered eg a font like arial that has four or five similar variants (bold, condensed, black etc). Once you reach the end of that family, you cannot continue to scroll. If you click away from that font family, scrolling can continue until another font "family" is encountered.

It is annoying regardless of whether you want to call it a bug or a design feature.

Cheers

gb

I totally agree! I've been here before. And guess what? They are all True Type Fonts too! Why Vegas doesn't recognise these is well beyond me.

Grazie

NOW here's a thought!

I just looked at my Font folder .. guess what? The file names aren't ALL in CAPITAL LETTERS. Ring any bells for anybody? We've had issues with lower case stuff in the past - yeah? And I haven't totally checked this out, but where the MEnu hits a lower or then UPPERCASE file name I get font family ignore .. . only a thought .. . anybopdy wanna chewck this out? I tried to changed the case of the filenames in WINDOWS folder but couldn't do it. . .

Any thoughts on this one? Maybe a sideways look at things?

Grazie

Grazie,

I dont think they intended to limit the user to only 4 fonts in either direction ;)

Though that is how it is designed? They have even got a greyed out Synch Cursor Lock. That was designed-in. And it is still there! Waiting to be actioned by the great programer in the sky I guess? What on Earth is a poor boy to think then? If it is there then it has to be correct - as per the design. Been there since - gawd - ever!

As to 4 fonts in any direction there must be a reason - and a jolly good one, is all I can say. Maybe it is the lower case file names that are doing it?

Funny, my simple Notepad shows all the fonts styles.

Best regards,

Grazie

Let me get this straight:

If a problem has been present since at least Vegas 3 or 4, then it is NOT a bug.

Boy, that says it all.

John

Thank you John! - Yes, simple isn't it. Grazie

I have noticed this problem, and find it annoying as well. However, I have not reported it (just didn't get around to it).

Have any of you reported this bug (via the Support -> Email Support button at the top of this screen)?? Posting in this forum doesn't guarantee that the bug will get logged.

Also, this bug may not be entirely Sony's "fault." The Windows font system has been dicey since the product was conceived. When I ran a desktop publishing company in the late 1980s, we refused to use Windows until version 3, and when we switched over, the font conventions were absolute hell to work with. While many improvements have been made since that time, what I think you are seeing here is that when Vegas encounters a non-Roman font (Dinbats, for instance) that consists mostly of non-alphabetic characters, it interacts with the application in a slightly different manner. Vegas, of course, should be able to handle this, so I'm not making an excuse for the rough spot in the design. However, I am suggesting that if you want to devise a workaround, you could simply delete the offending font. Personally, I haven't used a dingbat font since I left the DTP industry. Actually, I should probably go through and delete a lot of fonts anyway. I can't believe how many useless have accumulated over the two years since I bought this computer. Extra fonts slow down things such as switching from one printer to another.

Have you guys tried using the scroll wheel instead of the up/down arrows. This has been a bug/feature that drives me nuts in both 5 and 6. Sometimes I can use the arrows to scroll thru all of the fonts, other times I can't. The scroll wheel seems to work all the time. I might be wrong, but try it.

Interesting, I would have never known this bug existed if I hadn't read this thread. I have always used the dropdown arrow and mouse when making font changes/selections. Never had a problem at all.

I guess working with Windows for so long I've just naturally found workarounds for so many problems, so I'll stick with the mouse and not worry about the arrow key thing. I agree, it needs to be fixed, but it seems a miniscule problem for a video editing system.