Hey guys and gals! New here. I'm having a devil of a time with moving and resizing windows. I want a window to move and resize exactly as is shown in the attached screenshot, but I don't know how to determine exactly where it is x and y on the screen and how to tell KM that I want to end up there sized exactly as it is. Please help. Also, talk to me like I'm 5. I'm just getting into automation.
We (those of us who answer lots of questions, or in my case, used to answer lots of questions) love it when people ask questions like yours. Sometimes it feels like people just want easy answers, and that's OK, but when someone wants to learn, well, that just makes our day. So, kudos to you, and keep asking questions!
Then I realized that there was probably a "token" for this. Tokens are awesome, but for some reason, I don't immediately look there. Anyway, I went to the Wiki, and searched for "tokens", and this is what I got:
If I had been observant, I would have picked "A", or better yet, "B", but I picked "C" which was fine, but I just wanted to point out "A" and "B" so perhaps I'd remember to look there next time.
Then I wondered how to display the information, and at first I was just going to use a regular "Prompt for Input" action, but I decided it would be better to be able to copy the values, and I knew there was some sort of "Display" action that displayed text in a window.
So when I'm stuck, I search the Wiki, and this forum, and I usually find the answer pretty quickly. I also periodically just skim this forum, looking for interesting topics. I learn new things all the time that way.
KM is one of the best Mac automation tools available, its Forum is one of the best and friendliest forums on the Internet. Whenever you reach a tough stumbling block trying to use KM, please feel free to post your question/problem here for help.
I renamed my screens so the left and right screens are named "Left" and "Right" and then I just use KM to call the menu item in the window menu to move the currently frontmost window to that respective screen.
Thank you for this post and the one where you lay out how you search the wiki. Very helpful. Discovering this post save me from extending beyond an hour a bout of frustration during which I tried to figure out how to do moving and re-sizing of windows on my own.
Note: To set a length to 0, you have to input 0. An empty value is ignored. For example, if you only want to resize the height, leave the width blank and enter a value for the height.
I always have 3 browser windows open and I prefer all of them to be the exact same size all over lapping each other spot on. Plus I greatly dislike having a ton of things running in the notification area. You can run this app, restore your windows then close the app.
I do not know if it was a coincidence, but right after installing SIZER my Windows interface totally malfunctioned - the start menu got transparent windows was not refreshing and I could not click anything. I had to disable transparency in Windows 10 to fix this. Did anyone have such an issue too?
Actually, I am quite happy with it as it is really easy. If you press CTRL+SHIF+R on any window a dialog appears and you can enter the sizes that you want. The current size of the window is displayed too.
With powertoys fancy zones this can be achived pretty neatly. Define a fancyzone of the desired size by dragging. It shows the size in realtime so pretty easy. When the zone is defined and enabled, you can drag any window while holding shift will allow you to release the window in the zone you defined before and it will resize to fill the zone.
You can resize the Windows partition, and it will still boot. Windows will give an error at start-up the first time, saying the disk size doesn't match its records; it will run checkdisk and update its records, and then work fine. I've done this many times.
You cannot move the Windows partition though, or it won't boot. It's worth pointing out that if you shrink from the left side of the Windows partition, what you are actually doing is shrinking, and then moving; ONLY shrink from the right side of the partition. You also should not expand the partition on the left side, as again you're actually moving it to the left, and then expanding off the end; ONLY expand from the right side of the partition.
I would also point out that partitioning is never a 100% safe activity. You are altering the partition table; if that fails (slim chance) your entire disk is at risk for data loss. It's always a good idea to have a backup of your entire drive before engaging into any form of partitioning, not that most people actually do it.
It worked without a hitch: it's a very smart program. I now trust it. It ended up leaving Windows with less than 1% usable space! Which is great because i could get into Windows 10 and remove over 30% of the stuff, which makes it run better. But be careful.
This fact points out that GParted awesomely moved all the files in the NTFS folder to a tight nit space, and ...I saw it smartly checking for boot loading ability, and checkdisk as well for Windows. Brilliant.
Resizing the boot partition with an external editor (for example GParted) doesn't appear to work for non-NT versions of Windows. Booting will cause an unspecified error on my ancient Windows 98SE virtual machine.
I recently installed JMP and I think I ought to have set up the license properly. However upon going to through the tutorial I noticed something that I really ought to fix and is unfortunately, not addressed in most newbie guides I can find.
When I clicked the trial Columns and began to cast them I found that apparently, there was not any response from JMP.
I could click and drag, I could double click, I could select the columns and then click the X, Factor or Y, Response buttons and nothing would appear to happen. Confused I eventually hit OK and the graph I had attempted to make was properly generated. This baffled me because it appeared that I had never successfully input anything. I tried again still confused and eventually realized that I would have to resize my window to properly see what my inputs are.
So JMP is working properly over here I just appear to have some strange and functionally disruptive bug that revolves around my screen resolution or something. I wondered if there might be some setting that I had on by default that I ought to turn off. So I looked up some JMP troubleshooting guides and entered my File>Preferences menu only to find the same issue again. Again able to be temporarily solved by resizing my window.
I was a little bit lost, because I can't seem to find this issue when I look it up, and I am not sure I want to go around flipping preference switches in hopes that turning off one of the many settings fixes the issue. As I played around trying to replicate my issues (I am able to consistently update the GUI by resizing it) the GUI would sometimes inexplicably work which just makes everything even more confusing. For instance a selection of "Height" in that tutorial would after a few minutes render inside the Casting box, but when trying again with "Weight" I could wait a good ten minutes and never see an update. The first selection I make in a window seems always to work well but the second selection doesn't always highlight. In another window I used the scroll wheel on the right hand side of the screen only to realize no scrolling was occurring. Clicking on the window again updated the window to render the proper part of the page that had been scrolled to.
There must be some reason that all of these things are happening, Hopefully it is one I can fix. Is this a known JMP issue? (I didn't find any reference to it by an internet or forum search.) Maybe it is some compatibility issue? I am using a Dell Windows 10 Enterprise laptop with an Intel CPU and a very basic Nvidia graphics card.
It would be nice to get JMP to work smoothly, frankly having to constantly update the windows such that they render my tutorial inputs is borderline unusable. I'm not an expert R user and JMP looks like it could save me some time, hopefully with a little fixing it can.
What is hardware acceleration and why is it turned on by default? I understand it is likely considered to be a optimization of computer resources but was there a feature it was included to support? Will I want to turn hardware acceleration back on in the future for certain applications?
Graphics cards from different hardware vendors all share a common set of drawing functions. A lot of those functions date from the previous century. They also have vendor specific drawing functions that might be for scrolling or shading or 3D support or fonts or colors...I don't know, it is mostly hidden by layers of operating system support. Turning off the hardware acceleration means ignoring the newer functions, which are made available to the operating system through a device driver written by the hardware vendor. The driver maps the hardware capabilities to a standard OS function. I don't have a real example, but it might do something like replacing a pixel-by-pixel line drawing routine with a routine that uses the graphics hardware to draw a line.
JMP will perform better if the newer functions are available (edit: and the vendor's driver is bug-free enough.) If you install the updated driver, you'll want to turn JMP's hardware acceleration back on.
@Craige_Hales is exactly correct here. The OS technology JMP uses allows us to request extra speed from the graphics card by utilizing its hardware capabilities. This usually results in much faster drawing. The speedup can be especially noticeable with 4K monitors. However, bugs in the video card drivers can result in screen drawing issues just as you experienced. So, turning off that preference shifts much of the graphics work away from the video card and back to your CPU. Using the CPU means more data to move from RAM into the Video RAM when it goes to display so it'll be a little slower but it won't be susceptible to that driver bug. I too encourage you to try re-enabling the hardware acceleration once you get a driver update for the video card. That would help you regain a bit of performance.
c80f0f1006