Hello
In 2014R1.1 the Line was straight.
In 2014R2 I get this sloping Line in
Mac IDE and Win IDE/Compiled
By the way the ImageWell and the BevelButton
in Windows (compiled) are ruined too.
Is it me or a bug ?
It is a bug for sure. I had last night exactly the same in an application it was not changed for more than a month.
I had it with a horizontal line. For some reason Xojo added a new short line under an angle. I solved it by changing the normal line and the angular line disappeared.
Xojo does show some unexpected behaviour. I do not know where that weird behaviour is coming from.
I’ve seen this in the IDE too, in OS X. I haven’t been able to reliably reproduce it though.
[quote=110933:@Stefan Cyrus]By the way the ImageWell and the BevelButton
in Windows (compiled) are ruined too.[/quote]
The Windows compiled seems to have been built on the Mac. If that was the case, it would compound the IDE bug and compiler bug. Have you tried to run the project in the Windows IDE to verify the bevel button and canvas issues are there as well ? In the Windows IDE it looks OK.
I have not used line for a while, I tend to prefer a 2 pixels high rectangle for this kind of design. It allows me to set the upper and lower pixels in different colors, and it is always perfectly horizontal.
FWIW, I had the same issue with a line in 2014r2 for Mac. I hadn’t noticed the bevel button problem but may when I test on Win. Between this and the non-public API bug which affects MAS submission, 2014r2 is a bust for me.
Report this. You know what I miss about linexs in Xojo? Clicking an anchor point and dragging the end point to where I want (right, left, up, down, wherever). Xojo lines in the IDE are insane to edit with freedom. And now they present a new weird bug. 
Lines have been a pain since after RB 5.5 (when the IDE was written in C instead of RB/Xojo). I suspect that they never saw lines important enough to get then to work like they did in 5.5 and earlier. Controlling the positioning of a line by drawing it across the diagonal of a rectangle is a horrible experience for us.
Since then I’ve abandoned using them and either used a separator, did without, or for horizontal and vertical lines used a canvas to draw one myself. It’s easy to draw a horizontal or vertical line from end to end through the midpoint of a canvas. Not WYSIYG but close enough.
It is not a show stopper and easily worked around, but the fact that the current way of handling lines was deemed acceptable by Xojo when going from 5.5 to 2005 just shows they don’t sweat the details on usability like some (many?) of us feel they need to in order to get to the next level.
I understand the basic design of the IDE when rewritten in 2005 was for handling RectContols, and the line in 5.5 and before was not REALLY a RectControl in how it was handled in the IDE.
But if something is worth doing/having, it’s worth doing well… Anything else reflects poorly on the product and leave a poor impression even it’s really not a big deal, as in this case.
One other example from ancient history…
We all know that because string are immutable in the language, operations like concatenating a lot of strings the obvious way is EXTREMELY slow which was a big issue for some (many).
When they first introduced the Join function at it was as slow as if we were doing ourself with S = S1 +S2 + … It seemed like under the hood it was written in RB, not even using Memoryblocks ( that was something that should have been done in C under the hood)…
So the function did do what it was supposed to on paper, but in a way that did not address the core need. With complaints they did redo it…
But I can’t help but think paying attention to details/usability up front, would have taken less time and labor (saved money) in the long run, and left a better impression of the product…
All that said, despite some frustrations, I DO like Xojo and will stay with it… It just want it to be all that it can be. (but not join the Army 
)
Lines are just unlike every other rect control - so they quite literally are specially handled.
Every other rect control has a top left width & height.
Not so for lines - they have X1, Y1 , X2 , Y2 - or two control points.
Submit a bug report
EDIT : hate autocorrect It turned my misspelled “specially” into “socially”
[quote=110993:@Norman Palardy]Lines are just unlike every other rect control - so they quite literally are socially handled.
Every other rect control has a top left width & height.
Not so for lines - they have X1, Y1 , X2 , Y2 - or two control points.
Submit a bug report[/quote]
Have you used them since 2005?
They have been laid out across the diagonal since then…
While there may be a new bug in drawing them now, since then we have not been able set the control points directly using the mouse (only via the inspector which is non intuitive for WYSIWYG layout). By Mouse all we can do is change the bounding rectangle…
And If you do use the inspector to get a straight vertical line. it becomes just about impossible to select it by clicking on it…
Go back to 5.5 (if you still have a machine to run it on - I do) and put a line on a window and play with positioning it with the mouse… Not perfect, but a MUCH better experience than it has been since then IMO.
- Karen
Yes I’ve used them before & after.
Yes I’m aware of the issues you noted.
And yes, they are handled entirely specially in the IDE because they are set up entirely different than every other rect control.
Every other rect control can be set with top, left, width & height. Not so a line.
So there is, and always has been, special code (even in the old C++ IDE) for lines.
The OP should be using a separator instead of a line
[quote=110933:@Stefan Cyrus]Hello
In 2014R1.1 the Line was straight.
In 2014R2 I get this sloping Line in
Mac IDE and Win IDE/Compiled
By the way the ImageWell and the BevelButton
in Windows (compiled) are ruined too.
Is it me or a bug ?
[/quote]
Use a separator instead of a line
Hello
Hello
WIN COMPILED means compiled with MAC for WIN
Compiled with WIN for WIN it looks OK:
I found the ImageWell and BevelButton Error:
The Menus are wrapped, and this destroys the two Objects.
Will submit 2 Bug reports.
I’ve seen this too… it does seem unpredictable as sometimes, I can quit Xojo and start it back up and the lines will be fine. Another thing I’ve noticed is that when I specify a borderwidth > 1, it looks good in the IDE but at run time, it’s back to 1. For a workaround, I position the lines where I want and then add the code to set the X and Y coordinates as well as the borderwidth in the Open event for that Window. For now that seems to work but I shouldn’t have to do this.