I' developing an access database, and I've tested it with different Access versions and different computers and everything worked well. Until by chance I found out that I get a problem with small screens, even when the have exactly the same resolution than my other screens. (Full HD Laptop screen) It seems to me that Access 'zooms' in at my forms. The forms look rather clumsy, and I get loads of errors because of form with (maybe the twips changed?). Fields, who can normally show a number, now show #### because of bigger font.
Is there an easy way to get Access showing the forms at the same scale?
(Also I found out that the Ribbon-Text is much smaller than the form text on this screen. On a normal screen it's not like that)
Thanks for your help!
Thanks for your help, found out that this is caused by the windows 'feature' text zoom. Disabling it solves the problem.
Related
I am currently trying to build a personal profile page. It's a work in progress, and I know little HTML, but I'm getting there.
I'm having an issue with my webpage with regards to how it scales with changes of the browser window size. On my (quite wide) screen at university, it looks fine. However, reducing the browser window size manually - or simply viewing it in a full size browser window on a smaller screen - appears to mess everything up - it doesn't look very nice. Text goes close to my pictures, and it all looks a bit tatty.
I think this is probably because my design is quite poor.
1. Is it because my design is bad or is there something else I'm doing blatantly wrong?
My current idea for a solution is to resize things so that they would look more reasonable on a smaller screen (i.e. on a normal sized laptop). I'm worried that this might end up making things look a bit odd on a bigger screen, though.
2. Is it possible/within reason for a beginner to have two different designs, one for smaller screens and one for big screens, which could be detected and then utilised depending on what screen size viewer is using? Should my page be designed to simply work with whatever screen size?
3. If I do reorganize the page such that it works better with smaller
screens, is there a way to "lock" this design in place, so that it
doesn't get messed up if someone views my page in a wider window?
Perhaps a way to ensure that only the boundaries of the page increase
in width?
What I'm essentially asking is how I should go about designing my page in order to resolve the evident issue - where the issue is that it looks rubbish when the browser window is any smaller than the max size of my screen at university.
You've created your page using tables. It is not a good practise nowadays exactly due to the problems your are facing. In practise, tables should not be used for layout purposes.
To make your layout fluid it'd be better to develop using div with float and relative positioning.
You can see another discussion related to this topic here
https://webmasters.stackexchange.com/questions/6036/why-arent-we-supposed-to-use-table-in-a-design/6037
You could use css property #media, to handle different styles for different screen width: https://www.w3schools.com/cssref/css3_pr_mediaquery.asp
I have a website which looks good if viewed the way I designed it. Every time I visit it from Chrome on Android, I am given a prompt along the bottom of the screen to "Show Simplified View". If I click that prompt to actually see it in simplified view, the site will only display 1 news item (there are supposed to be 25 on a page), it removes all controls (log in, add news item, comments), and scrolling doesn't work anymore. There are multiple other problems as well (headlines/images/article excerpts are not matched together, color scheme is missing, etc.) This happens only on Google Chrome, no other browser I've tested does this.
I don't see the prompt to switch to simplified view on other sites. My preference would be to place a tag on my site to never show this prompt. I have googled around for that, but I have only found articles about how to turn the feature on from Chrome, nothing about how to disable the feature from the server side.
My second thought might be to work with this simplified view and get it functional for people who want to use it. However, I have read that it also blocks all advertising and my site is supported solely by ads, so this is a distant second if I absolutely can't prevent the prompt from appearing.
TO SUM UP:
How can I prevent the "Show simplified view" prompt from appearing or
Failing that, how do I set up my site to work with simplified view?
Replace P tags with div in your page. this mode is also known as Reader mode. Probably this answer might help you.
The answer I found for this was to change the font size based on the media width, and once the font size was big enough to be readable on the mobile device I was using, it stopped suggesting the simplified view. The exact code used was:
#media (max-width: 540px) {
body {
font-size:18px !important;
}
}
Simple enough.
Also check your viewport settings for mobile devices. I received this popup when I changed the initial scale of the viewport to 0.6.
Basically Google recognised that the font size is too small. Looks good to me but probably not for visitors without perfect eyesight.
<meta name="viewport" content="width=device-width, initial-scale=0.6, maximum-scale=2">
In this case, changing initial-scale=1 will fix this
A much better solution I ended up with
p { display: table; }
Just change the paragraphs to any of the generic blocks in my case I made it a table.
Show Simplified Views prompts when there is more text, Chrome prompts if it thinks it is a paragraph website where user is to read (by detecting texts (more than 700 approx)
If you truncate or remove texts, and make it less. Chrome won't prompt.
G'day mate. There's a permanent solution. Go into chrome://flags and search 'reader mode' and disable both flags which has 'reader mode' on it's name. And then, it's done, you'll never be annoyed by that pop-up again(unless you will uninstall and reinstall that chrome browser and then. ........ .... you'll have to do it again).
Thanks mate,bye.
I take several photos using iPad. I take them in different orientations (rotate iPad every time on 90 degrees).
Then I download them to my Windows laptop and what I see? I don't see them as I saw them on the screen of iPad. Actually, there is only one valid image. Others are rotated.
I found this problem in browser (FF & Chrome). When you display image using img html tag it is rotated. But if you display it by entering image's full URL - it's totally OK.
I checked pictures via Safari on iPad - they look fine (in img tag), but don't in Windows.
Is there some metadata which shows that image should be rotated or smth like this?
As you know, the iPad has a hardware device in it that tells it the device orientation, which is how it determines how to display the screen to the user. While the hardware instantly knows how it's positioned at any given time, they seem to have engineered a lag into the software registering this change to improve the user experience (so the screen doesn't flip back and forth several times in a single second). However, this lag might lead to some unexpected results when taking a photo.
I have found that the orientation is most often unexpected with the iPhone / iPad when I am taking photos with my screen facing downward (i.e. taking a picture of something on a tabletop, for example). I assume landscape but get portrait, and vice versa. In that scenario (downward / flat), it is more difficult for the device to know what my intended orientation is.
I find the best way to resolve this is to hold the device in the clear orientation that I want for a second before I take the photo, then point the camera downward and snap.
The orientation data is included in an image's metadata (AKA exif data). You can take a look here for more information:
http://www.daveperrett.com/articles/2012/07/28/exif-orientation-handling-is-a-ghetto/
It is relatively easy to retrieve (and modify) the exif data in software. If you are doing lots of batch processing in some type of custom way, libraries are available to help with this for a variety of frameworks. But for small jobs, the absolute most simple way is to click the little "rotate" icon in the image viewer software within Windows which will make the update for you.
Background:
I am creating an application in Ms-Access that is to be launched on a multi-user platform - This means many screens and many different resolutions etc.
Question:
Is it possible to have my application that automatically adjusts to the right size of the screen/resolution and the font size to be proportional to that of the % increased or decreased?
Similar to my answer here, yes, you can use the On Resize event of a form to move controls around, change the size of subforms, and perform other similar operations. Those adjustments are applied to each individual object, so the coding would be somewhat tedious and a bit "fussy", but it can be done (at least to some extent).
The font size will not automatically change based on screen resolution in any version of Access, but starting with Microsoft Access 2007 you can use new properties of controls to make them stretch, shrink or move based on the size of a form (described here)
Try using the VBA code in this answer to see if it gives you what you want. It works basically the way that Gord Thompson recommended. When the form is resized, all the controls and the text on the form will be proportionally resized too so that it looks the same no matter what size the window is, or what the user has their monitor resolution set to.
I know you can fake full screen by expanding a window and eliminating the title bar , status bar , and other stuff, I'm not interested in this, I want to know about "real" full screen mode (I don't know how to call it else) , like in games.
what exactly is full screen mode?
what win-api should I use to achieve this?
can this be used to play movies in full screen ? I know windows media player uses a fake full screen because I can "cut" thru it and see the desktop (using regions win-api).
can I "cut" thru "real" full screen like I thru a window (using regions win-api) ore is this directly writing to video memory and there is nothing "under" it?
Thanks!
If you want to make games on Windows in full-screen, the best option is XNA. This uses DirectX underneath, but hides a lot of the implementation details and plumbing to make it easy for the developer to start working on his game.
XNA is freely downloadable, and has good documentation.
XNA Game Studio 4.0 can be downloaded here.
...and you might want to support the "fake" fullscreen mode in addition to "real" fullscreen - it's very nice for those of us that run multi-monitor systems.
If you don't want to use DirectX, create window and call ChangeDisplaySettings with CDS_FULLSCREEN flag. OpenGL applications use this way to go fullscreen.
As far as a user is concerned, full screen is just when a window takes up the entire screen such that they no longer see any window borders or other desktop stuff.
As you know, not all full screens are created equal.
'proper' full screen is where the program takes control of the screen. When a game uses this mode, it can change the resolution of you screen. If you have ever played an old game and existed to see your icons all messed up, this is; for the duration of playing the game, your desktop was at a lower resolution.
with 'borderless full screen' the program window is striped of any borders, the title bar and frame etc., and is just a rectangle of pure rendering. If you then set this rendering context to be the same size as your desktop, you get the effect of full screen.
Doing border-less is usually the more user friendly way these days, as it is easier to 'tab out' as the other programs are still graphically around. 'proper' full screen gives you full control of the hardware, so in theory you have more power for your program, but it means you have to wait for things to reinitialise when you tab out.
what you do with your rendering context is up to you, so yes, you can use it play videos. It would not matter if you are in 'proper' full screen or not, the rendering code would be the same.
As for cutting through proper full screen windows, I am not sure, but I think there would be nothing else to see, there is only your program.
as for what win-api, there is only one windows api, but I think you mean, what windowing library; as this is getting to be a long answer already, I shall just say it depends a lot on what you want from it.
Please feel free to leave comments if you need me to clarify or expand on any points.