I faced an issue for using LibreOffice Draw.
I need to move images between grid points snapping to them.
But when I hold the images for more than 1 second, it automatically switched to free transform mode (drag & drop, also the mouse cursor would to be changed).
How can I prevent this?
If you move the image a bit after clicking on it, the mode will not switch. That's at least how it works here.
On windows you can simply do it by disabling this from settings but here you need to move the image for a second just after clicking on it. I think this is the only way to solve your issue.
Related
I have programmed a 90 second sequence in Google Earth Studio and I want to slow down the middle section only.
(I think there could be a long and dirty workaround by changing the overall time of the video in project settings and selecting scaling, then swaping in copies of the original start and finish, and link them all back together - but there must be an easier way to do this!?)
If there is a better forum for Google Earth Studio programming questions, please share in Comments.
I have found a better way to slow down a section of Google Earth Studio but it's still a bit clunky.
Increase the overall length of the animation in project setting, see above.
Highlight all the keyframes AFTER and including the end of the section to stretch (the spots on the keyframe editor, bottom half of screen).
Drag the selected keyframes to the right. This increases the time to get between the 2 keyframes (section to be stretched) automatically slowing the section down.
Tip 1: Selecting multiple keyframes (spots) - click and drag mouse but remember to select all keyframes including those out of sight. Scroll down to lower attributes.
Tip 2: Roll up (shrink) attributes before selecting multiple keyframes. This usually means that you can see everything without needing to scroll down. Click the small arrow next to the attribute (far left of keyframe editor).
Tip 3: You can always select keyframes manually, just hold down shift when you click on them to add to original selection.
Add to the comments if you know an easier way slow down a section of Google Earth Studio.
A bit of background: I recently implemented a Drag and Drop Behavior to my app, where I can drag items from e.g. the Finder inside my NSTableView. Now I wanted to write a few ui-tests for this new functionality.
The general idea was to move the finder window to the left side of the screen and my application window to the right side of the screen and then execute the drag and drop. The drag and drop itself is not the problem, the problem is the setup of the mentioned window layout. I cannot find a convenient way to resize and move the two windows. Coming from .net, I expected something like app.window.setSize(..) or app.window.moveTo(...).
What I tried so far:
As I have Magnet installed on my Mac, I tried the easy way out and sent key-events (control + option + arrow) to the window. This did not work, sending the keystrokes results in an error beep. Doing this manually during the tests works, so I don't know what exactly stops Magnet from rearranging the windows, but I guess it has something to do with the Testing Framework. I did not dig deeper into this, as it would have been a cheap solution anyway.
Drag the app window corners based on screen dimensions, e.g. for the window on the left I drag the corners to the top left, bottom left, top middle and bottom middle of the screen. This requires that all four corners are visible on screen, but that's a problem for another day. The solution would normally work, but the problem is that the y-coordinates I get from the frame of my app window are not what I was expecting. I do receive the location of the app window with app.windows.firstMatch.frame.origin. The x-coordinates look alright, but the y-coordinates are totally off (from what I expected).
I can't find many resources regarding the origin or frame members. Any idea on how to face this problem or where to find a documentation about the XCUITest-Framework and the basic concepts behind it? The official documentation doesn't help in this case. I only found this short explanation in the apple documentation archive about the coordinate system of macOS (or OS X back then) applications.
I have the, in my opinion, simple problem of disabling image detection with the AR Camera. I have the problem, that my app detects an image from the image library and spawns an object etc. everything according to plan.
But the problem is that if move the camera over another detectable image, it recognizes it. This is bad not because it spawns something additionaly but because you can "collect" the images in my app, so it unlocked the other detected one even though it shouldn´t.
So how can I disable image detection without turning off the AR-Camera?
I so far tried to simply disable the "ARManager" and the "ARTrackedImageManager" script (.enabled=false), but it didn´t solve my problem, because the app still detects other images.
Hope I could explain what my question and problem is properly. Any help is appreciated!
It really depends on what library you're using to detect the image. Generally, most marker tracking libraries will create a marker object in your Unity scene. You can disable these marker objects after you find one, and only leave the marker you're interested in. Make sure you also set the number of tracked images to 1 so you won't accidentally find two markers in one frame.
I've recently created a 2D app for the HoloLens. It is a UI Panel with several buttons into it. In order to drag the panel and be positioned as the user wants, I implemented the HanDdraggable.cs functionality (from HoloToolKit). However, whenever I try to move the panel it also rotates.
To change that I modified the Rotation Mode from "Default" to "Orient Towards User" and "Orient Towards User and Keep Uptight". But then It works even worst; if I implement that case, whenever I try to select the panel and drag it to somewhere, the panel runs off from my field of view and it suddenly disappears.
I wanted to ask if somebody has already tried to implement the HandDraggable option into an UI Hololens app and knows how to fix this nodding issue.
I'm currently working on hololens UI for one of my projects and to manipulate UI I used TwoHandManipulatable script which is built into MixedRealityToolKit. In Manipulation Mode of that script you could only set "Move" as an option, and this would allow you to move a menu with two hands, as well as one. (I wanted to have a menu which you can also rotate and scale - which works perfectly with this script, you can lock around which axis you want to have rotation enabled, to avoid unwanted manipulation).
For your script HandDraggable, did you try to set RotationMode to Lock Object Rotation? Sounds like this could solve the problem.
I'm making cuts of an image to use in various parts of my website; The header, the footer, etc. When I copy and paste to a new layer, it leaves a "feathered" edge. even though I have this set to zero. There is a 1 pixel margin around all of the copy and pasted images, that, when assembled as a web page using CSS, leaves little lines between all of the images. I was a professional graphic designer but I've been out of the game too long (2 whole years). God help me.
I'm not 100% sure of the source of the initial assets such as the header and footer, so I'm a little confused (some links might be nice), however it is worth checking a few things just to make sure. Hit M for the marquee and check thats feather amount. L for the lasso (long shot) and check that too, also check for any layer styles.
A nice little alternative, if you are exporting out individual assets,is go to File > Scripts > Export Layers to Files. This may save you a lot of trouble in the long run.
Hopefully this may help...
Additionally how are you copying? Is it from inside Photsohop or are you placing the layers? Are you using the marquee tool?
for try, don't use crop tool.. use select tool instead. select tool provides pixel level accuracy.
In addition to feather, try turning off anti-aliasing in your selections. After you make a selection, in the select options toolbar uncheck 'Anti-alias'.
If this is set photoshop will try to average the edges of the selection with the surrounding pixels to make it 'blend' better. This is worse than useless if you're trying to make accurate, pixel-level selections.
In Photoshop CC, after selecting with the marquee tool, right click to access the Feather option. Enter 0.1 and then copy and paste. That should take care of it.
I just encountered this problem. I'd cut and pasted and then dragged into a new image which created a new layer with the paste on. I then realised that the feathering was wrong. I changed the settings but forgot to change the active layer back to the background layer, so I was cutting and pasting the feathered cut I did originally. Facepalm.