I'm developing an Access 2007 Form. It's main purpose is to display records (usually more than 1 page) with a Close button at the bottom. Some highlights:
It is Continuous
Scroll Bars are enabled.
I'm testing this with 41 records. About a page and a half.
The problem is: If you keep scrolling after the last record, the screen returns to about the middle record. This doesn't seem like any standard GUI behavior I'm familiar with.
How can I get it to just stop scrolling when the last record is at the top of the screen?
Edit
I didn't even think about it when I posted this, but I get the expected behavior with Page Down and arrow keys. It seems to be only with the mouse wheel that I get this behavior.
Related
I have pop-up form for data entry. The form has a subform on it that is surrounded by blank cells of equal sizes similar to padding. (Why not use padding instead? Because I want to add functionality to those cells later on). When I view the form in form view (opening it), part of the right hand side is cut off such that it no longer looks like equally sized padding.
What's weird is that if I look at the form in layout view, the form is not cut off. And if I then open the form FROM Layout view, the form is also not cut off. But if I open the form in any other way (from a button, vba, right click open from navigator etc.), it is being cut off every time.
Does anybody know why this might be happening and how I might fix it?
Form being cut off
Form not cut off in layout view
Form not cut off when opened FROM layout view
I found this issue occurs when working in access with a higher display resolution than 1920x1080. 3440x1440 in my case.
The only solutions I have found is what you described by opening the form in layout view then switching to form view then save the form.
Only other option is changing display resolution.
I'd like to share a "work around" on this same subject, hopefully it may help in certain cases where the issue is NOT due to Form Sizing through VBA code, which is determined to be the cause inadvertently.
My scenario:
Popup forms, set to auto center, auto resize, fit to screen = truncated, or overcropped form (and DESPITE my own VBA sizing code, which doesn't seemingly "take" or correct the issue).
I usually/often have the scrollbars property set to "neither", so I tried setting "both" on, and the popup form is no longer truncated. I then tried with ONLY the "Horizonal" bar set to on, and it still worked correctly. I then turned both BACK OFF and the form still sized correctly. I saved the form and it appears to have retained the "sizing" properly going forward.
It's as if when you turn these options to neither, the space normally occupied by those scrollbars is "taken off" the borders of the form "again" so maybe toggling that property to both/vertical only/horizontal only/neither "resets" and corrects it. Just a guess.
Hope this helps, spread the word of this little "work around."
O.W. Khan
Let me explain the situation.
I need to copy a lot of instances of a text inside a project of PhpStorm. So, I perform a 'Find in Path' action and a floating window appears with the matching results.
Now my problem is that after copying once from the floating window, if I click on another app window, then PhpStorm's main window/PhpStorm itself go to background, then if I want to copy text from the floating window again, I can not use any keyboard shortcut, I can not modify any line in the floating window because PhpStorm stays in background/inactive-mode even if I click on its floating window.
If I click anywhere in the PhpStorm except the main top-white bar of PhpStorm, then the floating window disappear, which causes me to perform the search again.
It is reducing my productivity a lot. Is there any way to make the PhpStorm active or bring it foreground when clicking its floated search window?
Please see the screenshot:
Is there any way to make the PhpStorm active or bring it foreground when clicking its floated search window?
You are approaching the problem from the a bit wrong angle. There is a better solution than fighting the focus/foreground state.
There is a button in the bottom right corner of "Find in Path" window ("Open in Find" it says on your screenshot) -- click it and it will open search results in traditional / standard Search Results tool window (with grouping by folders/files, preview area etc)... so no floating and no auto closing on clicking somewhere.
P.S. Lots of people forgetting that results shown in this new "Find in Path" dialog/popup is still just a preview (TOP 100 matches only). Super functional (you can edit and stuff) but still preview only. This mainly applies to those who remember the way how this dialog (back then it was dialog window) looked before redesign (now it's more of a popup).
Because of the way how it is all presented now (results occupy majority of the popup space) people somehow automatically forgetting about "traditional" way of searching (clicking actual "Find" button to get search working) and focusing only on what they see on a screen right now.
This new "Find in Path" dialog/popup adds a lot of convenience for sure (you typed search text and results are straight away before your eyes). At the same time quite often you may see/hear "it does not show me all results" frustrated comments (as it shows top 100 .. and a single file may have 100+ hits in some cases) and alike. JetBrains needs to improve UX a bit in this area for sure.
My Ionic1 app displays a list of items that can be collapsed/expanded, so the vertical length of the content can increase significantly when an element is expanded (the way I do it is through ng-show directives).
My issue is that when this happens, I cannot scroll down to see the new content. Actually, if I drag my finger from bottom to top, I can see the new content appear in the bottom, but as soon as I release my finger, some elasticity brings back the top of the content.
However, strangely enough, after a few seconds, the scrolling mechanics is updated correctly and I can scroll normally.
It looks like the Ionic framework takes some time to figure out that the content length has changed and needs some update in the scrolling mechanics... I would like to tell him immediately once it is needed. I tried to call $apply from the onClick call back of the Expand buttons, but I get an error saying I am already in a digest cycle.
Any clue to fix this please? Many thanks!
You can avoid $apply approach because every $scope.$apply is rebind in the page. So you can follow the ionic scroll concept.
ionic scroll
Thanks! this helped me fix the problem, by adding a call to $ionicScrollDelegate.resize() whenever some item is collapsed/expanded.
You can check the issue with this fiddle: quickly expand groups 7/8/9 and try to scroll down:
http://jsfiddle.net/shengoo/6b0y3tar/
I need to save LongListSelector position in order to restore it once I get back to the page.
First I used GetItemsInView with WP7 and it works great.
Then with WP8 it was gone and I have to use ItemRealized.
It also works fine but I have side effect which that ItemRealized gives me the item which is at the bottom of current page (it could be even not visible yet).
But what I need is to scroll to the item at the top of the page.
I could subtract manually items which are visible (by calculating item height and page height) but because the realized item could be not visible yet (that means my calculation logic will not be correct) I couldn't be sure that I chosen the right element.
Is there a way to find the first visible item in the view at LongListSelector?
When you navigate to a page with LongListSelector where items have already been loaded (items are already present in itemsSource), the focus, by default is on top most item. You can scroll down to view other items.
In my application, I have a requirement to focus on bottom most item and user can scroll up to view other items.
One solution is to call ScrollTo function on bottom most item. Here, user can see the list being loaded and then change of focus from top to bottom most element. So, the user experience becomes very bad.
Is there any seamless way to do it?
I think ScrollTo is most efficient for a LongListSelector. But if you need to have the experience more seamless you might want to wait/halt your app with a loading screen while the LLS is populated and the focus is changed to the bottom. Async commands or a simple loading status bar could do the trick.