A key combination, so an arrow key with a modifier key would stretch an object a pixel at a time, or 10 pixels if the shift key is being held down.
This would help with precision in placing and sizing objects
Good idea.
Note: when moving controls in the Layout Editor, Shift+Arrow moves things 8 pixels at a time.
What Iād really like is to make the movement (or stretch) length a user setting. Because itās easier to count in my head the distance I need in blocks of 10.
1 Like
Yes, I noticed when an object is duplicated it takes an odd number of shift+arrow strokes to get its duplicate and it to line up on an axis.
Also when the duplicate is duplicated, it does not go to the new location relative to its source object.
In other words,
Duplicate an object.
Place the duplicate 10 pixels to the right of its source.
When the duplicate is duplicated, it should go 10 pixels to the right of its source.
3 Likes
What is Shift-Arrow ?
Shift-RightArrow move the object to 8 pixels, duplicaed object AND original.
WHAT is the issue # of your Feature Request ?
@scott: Me too, I prefer 10 pixels skip vs 8 (Preview do 10 pixels).
1 Like
The Shift key in combination with any Arrow key (left, right, up, down).
already asked ā¦
https://tracker.xojo.com/xojoinc/xojo/-/issues/13411
14 years ago !!!
2 Likes
Good things take time. 
it still needs review ā¦
@Robin_Lauryssen-Mitchell ???
idem for these two same requests for zoom in/out in the IDE from also 14 years agoā¦
https://tracker.xojo.com/xojoinc/xojo/-/issues/11661
https://tracker.xojo.com/xojoinc/xojo/-/issues/15736
and this one for only 2 years ago (this one does not need review ?)
https://tracker.xojo.com/xojoinc/xojo/-/issues/71499
1 Like
We shouldnāt keep harping on about the fact that there are old and poorly reviewed (or not reviewed at all) tickets in the issue system. Thatās completely normal for an issue tracking system that has been around for a long time. There will always be such tickets.
I think a reference to such long-standing tickets should be mentioned in the new ticket. Of course, itās perfectly fine to point this out here in the forum. But please donāt let us complain about it again and again. 
I donāt complain ā¦or a little may be ?
I know xojo has some priorities that are not always mineā¦
I just recap the old issues so that Robin can merge them
it is still a good FR, along with the zoom in the IDE.
may be one day ?
1 Like
In addition to Zoom facilitating easier manual object placement: https://tracker.xojo.com/xojoinc/xojo/-/issues/11661
It would also help if the square handles could have a transparent fill, or if they could be made to disappear temporarily, when moving or aligning objects. The edges of smaller objects can sometimes be mostly obscured by the handles.
1 Like
I much prefer typing in the X/Y/Height/Width values directly. It gives precise placement. Also, since moving stuff around in the IDE has always been slow, you only have to do it once.
1 Like
With a litle luck or if you do not change your mind. But overall, I share Timās opinion on this one.
Maybe Keith have a particular case where his way may be far better than that ?
Keith ?
An example is with a layout having multiple objects placed horizontally.
The top coordinate of all the objects can be different, but they must line up at the bottom.
I canāt think of a better way than to select them all and then type the bottom coordinate in the Inspector field labeled āBottomā. Entering the bottom coordinate changes the height of each object while leaving the tops in place. Itās effectively getting the computer to do the work of recalculating the heights so the bottoms will match.
Stretching, the original subject of this post, is for that case where the group needs to be made taller or shorter by a pixel, for instance. A Command-Key plus down-arrow-key would be a fast way to get that done. Also, since I always get it wrong a few times, keystrokes are much more convenient than returning to the field and retyping the number.
These cases were reviewed shortly after they were created.
The āNeeds Reviewā label was recently added to all unresolved Feature Request cases that are over two years old.
I am (very) slowly working my way through them.
In quite a few instances such cases are closed as Implemented - usually via another Feature Request.
Others are closed because they are obsolete.
Some will remain open waiting for the Development team to review them.
3 Likes
Isnāt there a button to do that ?
Yes, there are.
Butā¦
They canāt do this.