Stupid unnecessary bugs
-
Just spent some hours today tracking down what I felt was a really odd and unexpected error that turned out to be really simple. I made a webpage that contained a chart, so far no problem. But when I moved the code over to the server the chart titles turned out smaller than on my devmachine. So identical code rendered as images turned out having different size of the text on two machines that I thought had the same settings. :doh: Well, to the story belong that I got a new devmachine last week. It's a 14" laptop with 1920x1080 resolution (and a ridiculously fast harddrive compared to my old machine), so the clever people at Dell thought that as you obviously don't buy high resolution to get more real estate, had set the default DPI at 120 instead of 96. So I immediately set it down to 96DPI and thought no more of it. Problem was just that the IIS Worker Process uses a separate account that still had the default 120 DPI setting. And the rendering of text uses that default setting on the Worker Process Account rather than the setting on my account So whose fault is this? Mine for not setting the font size in pixels instead of points? Or Dells for having a stupid default setting? Perhaps Devexpress for using a local environment setting for something that should have a standard translation in the Control? Your call. Whose fault is it? But more important, how should something like DPI be handled on the net? It shouldn't be set at the server, but rather use the setting from the client, or? /Rant over.
Wrong is evil and must be defeated. - Jeff Ello[^]
-
Just spent some hours today tracking down what I felt was a really odd and unexpected error that turned out to be really simple. I made a webpage that contained a chart, so far no problem. But when I moved the code over to the server the chart titles turned out smaller than on my devmachine. So identical code rendered as images turned out having different size of the text on two machines that I thought had the same settings. :doh: Well, to the story belong that I got a new devmachine last week. It's a 14" laptop with 1920x1080 resolution (and a ridiculously fast harddrive compared to my old machine), so the clever people at Dell thought that as you obviously don't buy high resolution to get more real estate, had set the default DPI at 120 instead of 96. So I immediately set it down to 96DPI and thought no more of it. Problem was just that the IIS Worker Process uses a separate account that still had the default 120 DPI setting. And the rendering of text uses that default setting on the Worker Process Account rather than the setting on my account So whose fault is this? Mine for not setting the font size in pixels instead of points? Or Dells for having a stupid default setting? Perhaps Devexpress for using a local environment setting for something that should have a standard translation in the Control? Your call. Whose fault is it? But more important, how should something like DPI be handled on the net? It shouldn't be set at the server, but rather use the setting from the client, or? /Rant over.
Wrong is evil and must be defeated. - Jeff Ello[^]
I always thought web pages should be scaled by using the browser zoom option. So if the user wants it bigger, they hit Ctrl++. The challenge, then, is to construct a web page that behaves appropriately at 75%, 100%, 150% zoom and everywhere in between.
-
Just spent some hours today tracking down what I felt was a really odd and unexpected error that turned out to be really simple. I made a webpage that contained a chart, so far no problem. But when I moved the code over to the server the chart titles turned out smaller than on my devmachine. So identical code rendered as images turned out having different size of the text on two machines that I thought had the same settings. :doh: Well, to the story belong that I got a new devmachine last week. It's a 14" laptop with 1920x1080 resolution (and a ridiculously fast harddrive compared to my old machine), so the clever people at Dell thought that as you obviously don't buy high resolution to get more real estate, had set the default DPI at 120 instead of 96. So I immediately set it down to 96DPI and thought no more of it. Problem was just that the IIS Worker Process uses a separate account that still had the default 120 DPI setting. And the rendering of text uses that default setting on the Worker Process Account rather than the setting on my account So whose fault is this? Mine for not setting the font size in pixels instead of points? Or Dells for having a stupid default setting? Perhaps Devexpress for using a local environment setting for something that should have a standard translation in the Control? Your call. Whose fault is it? But more important, how should something like DPI be handled on the net? It shouldn't be set at the server, but rather use the setting from the client, or? /Rant over.
Wrong is evil and must be defeated. - Jeff Ello[^]
Bugs are never-ever unnecessary! You only have to know how much to create! I always say to my group - the bugs you create today are the bread-and-butter of tomorrow! :-D
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
Bugs are never-ever unnecessary! You only have to know how much to create! I always say to my group - the bugs you create today are the bread-and-butter of tomorrow! :-D
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
Please remind me, what's your product?
Wrong is evil and must be defeated. - Jeff Ello[^]
-
Bugs are never-ever unnecessary! You only have to know how much to create! I always say to my group - the bugs you create today are the bread-and-butter of tomorrow! :-D
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
You'll never get very far if all you do is follow instructions.
-
Please remind me, what's your product?
Wrong is evil and must be defeated. - Jeff Ello[^]
ERP for educational institutes including - and our customers are universities and colleges...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
You'll never get very far if all you do is follow instructions.
"I'm gonna write me a mini-van this afternoon" classic. :)
Along with Antimatter and Dark Matter they've discovered the existence of Doesn't Matter which appears to have no effect on the universe whatsoever! Rich Tennant 5th Wave
-
Just spent some hours today tracking down what I felt was a really odd and unexpected error that turned out to be really simple. I made a webpage that contained a chart, so far no problem. But when I moved the code over to the server the chart titles turned out smaller than on my devmachine. So identical code rendered as images turned out having different size of the text on two machines that I thought had the same settings. :doh: Well, to the story belong that I got a new devmachine last week. It's a 14" laptop with 1920x1080 resolution (and a ridiculously fast harddrive compared to my old machine), so the clever people at Dell thought that as you obviously don't buy high resolution to get more real estate, had set the default DPI at 120 instead of 96. So I immediately set it down to 96DPI and thought no more of it. Problem was just that the IIS Worker Process uses a separate account that still had the default 120 DPI setting. And the rendering of text uses that default setting on the Worker Process Account rather than the setting on my account So whose fault is this? Mine for not setting the font size in pixels instead of points? Or Dells for having a stupid default setting? Perhaps Devexpress for using a local environment setting for something that should have a standard translation in the Control? Your call. Whose fault is it? But more important, how should something like DPI be handled on the net? It shouldn't be set at the server, but rather use the setting from the client, or? /Rant over.
Wrong is evil and must be defeated. - Jeff Ello[^]
The DPI of the server or the IIS instance should be irrelevant. You should be rendering that chart in a machine-independent way. I guess the component is designed to be used as an embedded UI control so it kind of makes sense that it picks up your local DPI setting by default. It's mostly your fault I suppose (assuming setting a pixel size makes it work right) but definitely an understandable mistake to make!
-
I always thought web pages should be scaled by using the browser zoom option. So if the user wants it bigger, they hit Ctrl++. The challenge, then, is to construct a web page that behaves appropriately at 75%, 100%, 150% zoom and everywhere in between.
-
The DPI of the server or the IIS instance should be irrelevant. You should be rendering that chart in a machine-independent way. I guess the component is designed to be used as an embedded UI control so it kind of makes sense that it picks up your local DPI setting by default. It's mostly your fault I suppose (assuming setting a pixel size makes it work right) but definitely an understandable mistake to make!
I would guess that the root of the problem is that he is using some control that makes an image on the fly. (As opposed to creating a drawing on HTML canvas.) If that is the case, then the image will most likely use the GDI of the server in rendering the image before sending it. Thus, the server settings begin to matter.
-
Just spent some hours today tracking down what I felt was a really odd and unexpected error that turned out to be really simple. I made a webpage that contained a chart, so far no problem. But when I moved the code over to the server the chart titles turned out smaller than on my devmachine. So identical code rendered as images turned out having different size of the text on two machines that I thought had the same settings. :doh: Well, to the story belong that I got a new devmachine last week. It's a 14" laptop with 1920x1080 resolution (and a ridiculously fast harddrive compared to my old machine), so the clever people at Dell thought that as you obviously don't buy high resolution to get more real estate, had set the default DPI at 120 instead of 96. So I immediately set it down to 96DPI and thought no more of it. Problem was just that the IIS Worker Process uses a separate account that still had the default 120 DPI setting. And the rendering of text uses that default setting on the Worker Process Account rather than the setting on my account So whose fault is this? Mine for not setting the font size in pixels instead of points? Or Dells for having a stupid default setting? Perhaps Devexpress for using a local environment setting for something that should have a standard translation in the Control? Your call. Whose fault is it? But more important, how should something like DPI be handled on the net? It shouldn't be set at the server, but rather use the setting from the client, or? /Rant over.
Wrong is evil and must be defeated. - Jeff Ello[^]
Most likely Devexpress' fault, if you report this as a bug today it may be fixed in... 3 years if you're lucky... ;P
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
Just spent some hours today tracking down what I felt was a really odd and unexpected error that turned out to be really simple. I made a webpage that contained a chart, so far no problem. But when I moved the code over to the server the chart titles turned out smaller than on my devmachine. So identical code rendered as images turned out having different size of the text on two machines that I thought had the same settings. :doh: Well, to the story belong that I got a new devmachine last week. It's a 14" laptop with 1920x1080 resolution (and a ridiculously fast harddrive compared to my old machine), so the clever people at Dell thought that as you obviously don't buy high resolution to get more real estate, had set the default DPI at 120 instead of 96. So I immediately set it down to 96DPI and thought no more of it. Problem was just that the IIS Worker Process uses a separate account that still had the default 120 DPI setting. And the rendering of text uses that default setting on the Worker Process Account rather than the setting on my account So whose fault is this? Mine for not setting the font size in pixels instead of points? Or Dells for having a stupid default setting? Perhaps Devexpress for using a local environment setting for something that should have a standard translation in the Control? Your call. Whose fault is it? But more important, how should something like DPI be handled on the net? It shouldn't be set at the server, but rather use the setting from the client, or? /Rant over.
Wrong is evil and must be defeated. - Jeff Ello[^]
Your fault
-
Just spent some hours today tracking down what I felt was a really odd and unexpected error that turned out to be really simple. I made a webpage that contained a chart, so far no problem. But when I moved the code over to the server the chart titles turned out smaller than on my devmachine. So identical code rendered as images turned out having different size of the text on two machines that I thought had the same settings. :doh: Well, to the story belong that I got a new devmachine last week. It's a 14" laptop with 1920x1080 resolution (and a ridiculously fast harddrive compared to my old machine), so the clever people at Dell thought that as you obviously don't buy high resolution to get more real estate, had set the default DPI at 120 instead of 96. So I immediately set it down to 96DPI and thought no more of it. Problem was just that the IIS Worker Process uses a separate account that still had the default 120 DPI setting. And the rendering of text uses that default setting on the Worker Process Account rather than the setting on my account So whose fault is this? Mine for not setting the font size in pixels instead of points? Or Dells for having a stupid default setting? Perhaps Devexpress for using a local environment setting for something that should have a standard translation in the Control? Your call. Whose fault is it? But more important, how should something like DPI be handled on the net? It shouldn't be set at the server, but rather use the setting from the client, or? /Rant over.
Wrong is evil and must be defeated. - Jeff Ello[^]
Jörgen Andersson wrote:
Problem was just that the IIS Worker Process uses a separate account that still had the default 120 DPI setting
This isn't really the problem. The problem is that the IIS Worker Process uses a locally sourced DPI value AT ALL. There is no single answer that will be correct for all the platforms that it will render for. Sure, you just fixed it for platforms set to 96 DPI, but that means you just broke it for platforms set to 120 DPI.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
-
The DPI of the server or the IIS instance should be irrelevant. You should be rendering that chart in a machine-independent way. I guess the component is designed to be used as an embedded UI control so it kind of makes sense that it picks up your local DPI setting by default. It's mostly your fault I suppose (assuming setting a pixel size makes it work right) but definitely an understandable mistake to make!
Just reading up on CSS and found out that a pixel is not a pixel because it is set to a specific size in the browser. So this setting is a browser setting so that when you define a page in pixels (as we all seem to do) it renders 'consistently' across multiple different resolutions. So the whole thing is not as simple as it sounds.
