hmmm. 1 screen, scaled down to look smaller, another (hidden, shown with a button) that would show the screen distatched from said calculator?
LuxenD wrote:
hmmm. 1 screen, scaled down to look smaller, another (hidden, shown with a button) that would show the screen distatched from said calculator?
That's another option I considered. I know that calculator programmers would probably not love that, but math users likely wouldn't mind.
ajcord wrote:
Or just make the skin bigger proportionately to the LCD and sacrifice the actual-size-ness.
I examined that option. It would make the skin be 1280 pixels tall. 
blech. my laptop wouldnt even show half of that. maybe an in-between would work. scale up the skin by a tiny bit, and scale down the screen, too.
LuxenD wrote:
blech. my laptop wouldnt even show half of that. maybe an in-between would work. scale up the skin by a tiny bit, and scale down the screen, too.
I think if any scaling is done, I'd prefer to keep the skin normal size and scale down the screen, then switch to the alternative that I posted for users that request a full-sized screen. LuxenD wrote:
maybe an in-between would work. scale up the skin by a tiny bit, and scale down the screen, too.
I agree with this. I did some quick testing, and it seems like scaling the CSE screen down to 75% still gives good quality. To make it fit the skin, it would have to be closer to 60%, which is pretty poor for readability. Scaling up the skin to 133% to fit a screen scaled down to 75% would make the skin 967 pixels tall, which is just a bit larger than the inner height of an average browser. This would preserve the quality of the screen image while simplifying the interface.
EDIT: The skin would actually only need to be scaled up to about 125%, in which case the skin would be around 900 pixels tall, which is pretty close to the average browser inner height.
ajcord wrote:
LuxenD wrote:
maybe an in-between would work. scale up the skin by a tiny bit, and scale down the screen, too.
I agree with this. I did some quick testing, and it seems like scaling the CSE screen down to 75% still gives good quality.
The thing is that if you scale by 25% you omit one line out of every 4. Sure it might look good in post but while running a live emulation it can be hell. What do you do on the 4th line? Do you omit it? Move it to Line 3 or 5? I'm no expert but that is what I'm thinking. I think it'll be much easier to decide on a screen size once we get TI84C support working with the full screen size then start working on a proper screen size and skin to finalize; this doesn't need to be available on Day 1.
There are two types of people in the world: those who can extrapolate data from incomplete data
comicIDIOT wrote:
ajcord wrote:
LuxenD wrote:
maybe an in-between would work. scale up the skin by a tiny bit, and scale down the screen, too.
I agree with this. I did some quick testing, and it seems like scaling the CSE screen down to 75% still gives good quality.
The thing is that if you scale by 25% you omit one line out of every 4. Sure it might look good in post but while running a live emulation it can be hell. What do you do on the 4th line? Do you omit it? Move it to Line 3 or 5? I'm no expert but that is what I'm thinking. I think it'll be much easier to decide on a screen size once we get TI84C support working with the full screen size then start working on a proper screen size and skin to finalize; this doesn't need to be available on Day 1.
comicIDIOT wrote:
The thing is that if you scale by 25% you omit one line out of every 4. Sure it might look good in post but while running a live emulation it can be hell. What do you do on the 4th line? Do you omit it? Move it to Line 3 or 5? I'm no expert but that is what I'm thinking.
This was using cubic scaling, not nearest neighbor. So from what I understand, the lines are merged together to create the appearance of being 4 lines while really there are only 3.
ajcord wrote:
comicIDIOT wrote:
The thing is that if you scale by 25% you omit one line out of every 4. Sure it might look good in post but while running a live emulation it can be hell. What do you do on the 4th line? Do you omit it? Move it to Line 3 or 5? I'm no expert but that is what I'm thinking.
This was using cubic scaling, not nearest neighbor. So from what I understand, the lines are merged together to create the appearance of being 4 lines while really there are only 3.
Register to Join the Conversation
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Advertisement