MidiMagic

Empty tag pairs are not allowed. Different browsers waste them in different ways. Use styles to create blank spaces, instead of p tags with nonbreaking spaces inside.

The driver might be compatible, but the software to control and use the camera might not be. Take it as a rule of thumb that most software that needs real-time operation will not survive a changeover to Microsoft's next operating system, unless multiple version compatibility files are sold in the …

The correct form of the br tag is: [code]<br />[/code] Note the space before the /. This makes the tag work (actually fail invisibly) on older browsers. Single tags without closing tags or closing slashes are deprecated (a fancy word meaning they plan to discontinue it shortly). So we either …

Do your images together make a size larger than your IE browser cache setting? Try trading the images, and see if the other one displays instead. If your image is larger than the selected number of pixels in the tag, it won't display.

This might be a screen resolution error. In other words, if the content won't fit in the page width, the div repositions where it fits. Absolute positioning is also a cause of page mutilation when the screen resolution changes..

I come here only once a week. Check to see if they have Microsoft Excel export and import in common.

A few points: - 0px is an invalid style. It causes browser errors. Use 0 for values that are zero. - Convert all size and alignment tag attributes to styles. - Use classes, so each set of styles can be used on all tags needing it. - Use relative sizes, …

This is a setting in the Options dialog box.

Are you talking about the missing green lines in the borders? You have empty div pairs. Nothing is placed between the tags. This is a nonstandard use (a no-no in web page design). There is no guarantee that an empty pair of tags will be rendered. If there is room, …

This is a place where the browsers are not the same. The divs are inheriting the center attribute from the outside div in FF, but not IE. The second div is also too large, since it is wrapping. FF decided to give it maximum width by placing it below the …

Moving image players don't like to be under other things.

You have to call a function in the script from the body of the page for it to execute. Otherwise, it just sits there.

I hope the voting server can take the Independent Voting System (yes/no/abstain on each choice, score is yes minus no). The standard way people vote in elections is mathematically flawed.

Are you talking about Excel or Access? You can add a comment to an Excel cell.

Any software that removes other software is greedy, and belongs in the trash can.

Note that stacking stuff on top of each other is not yet perfected. Part of the problem is that some movie players automatically put themselves on top of everything else when they are running. This hides the button if you try to put it on top of the movie. Can …

I really don't see how any company that annoys you to death (or freezes your scrollbar) expects to gain customers.

This problem usually occurs when an image is changed between a palleted form and a non-paletted form. The conversion software does not know how to handle shadings made by alternating paletted pixel colors.

Note that many email browsers, and some ISPs, are set to disallow html for security purposes. So don't expect everyone to be able to see it.

Why the sudden interest in zip files? Some of us can't open them.

You are making a copy of the array with your function declaration. Then, when you return from the function, the copy is not copied back to the original. Either address the array globally (don't use it as a paramet4er, but just use it inside the function), or return it in …

Don't assume that everyone had the capability to open a compressed file. This ability is purposely banned from the computers I use.

You can also use a query.

Moving images usually can't be in the background. The player for a moving image will usually place itself on top.

The real problem is that you can't put size styles (width, height) and nonzero surrounding styles (margin, border. padding) on the same tag. IE renders them in the opposite nesting order to the standard order used by FF and other browsers.

Several facts: - The viewport height is not normally something the page rendering engine takes into account. It is expected to place things against the top, and then add them on downward until it runs out of material. The emphasis is in fitting things to the page horizontally. If it …

This is a place where you should use a query. With it, you can display data from different tables in the same screen.

That's to keep you from accidentally deleting an unsaved feature.

Did your hard disk get fuller?

You must put things on the left before things on the right.

Is this a question of IE opening by itself when you aren't browsing the web, or is it a case of a website being browsed in another browser (Netscape, Firefox, Opera) switching to IE when a particular link is opened? If it is the latter, it might be that the …

Reinstall. That's the only way to fix the boot. And you will have to boot from the CD to do that. Never compress files.

It depends on whether your browser image rendering setting is set to "shrink to fit" or "scroll large images." If it is shrinking to fit, text on a saved image may shrink too small for the display resolution on the screen you have.

They probably stuck something in the file to stop an ipod from copying the whole file.

They put the page into a frame, with the ads in another frame. But it also makes any page that was so carefully crafted to validate on W3c fail to validate when displayed on the combined page. This makes web page makers mad. Alternately, you could require that the page …

This is a case that needs a table. It is extremely difficult to do it with divs and css. But you can certainly use css to format the table. If the sides are empty, just use padding on the body tag. There is a misconception on removing tables from websites: …

This is a very difficult problem, because you are trying to create transparency on top of a moving image. Remember that text has either a colored background, or has a transparent background that shows what is behind it. But it becomes a huge task of working out for each pixel …

No, because all images are really rectangles. The rest of that image is transparent. But the browser has no idea where the content is within the rectangular image. I have some ideas: 1. Cut the image in two. But placement is tricky. 2. If the image is really solid green …

It's better to write code that works in all browsers.

Your scripts are putting other things on top of the video. Try to build pages with objects INSIDE other objects, not ON TOP of them. Layering is not yet fully implemented so it works well.

You need a for or while loop to repeat all of the records. But why don't you just use the export function under File.

That sounds like a job that would never be done, because while you are writing the huge amount of code to do that, the services will change their pages, so you would have to start over.

Use a regular button with the word RESET on the face. Use it to call a function to put default values in the ones you want to reset. I wrote several of these.

It's never going to work with absolute settings. Different browsers will render it differently. Different screen resolutions and window sizes also cause trouble with absolute settings. Use percentage of page settings instead. You may also be seeing the IE/FF incompatibility. Placing both size styles (width, height) and surrounding styles (margin, …

Remember that some people are totally sick of hover effects. They are cute little tricks that are quickly becoming annoying, and they are accessibility problems for people with dyslexia. They will flee your page with the back button.

This is exactly what is wrong with Microsoft. They keep introducing incompatibilities.

Unmean yourself to use IE. :icon_biggrin: Note that there are several settings for different kinds of text. You might have to change a setting for monospace fonts. It might also be that a font size is specified in the page.

I can think of several reasons: - Different browser communications settings. - Different methods for the way the browser assembles the page. - Different handshaking orders. - Different methods of resizing images to fit. - Different methods of displaying (maybe one waits until the entire image is downloaded before displaying …

It's the same (and working) in both browsers for me.

Just like Microsoft, who also can't seem to leave stuff alone.