621
Mach4 General Discussion / Re: scr.getProperty – Macro Parameters – Registers
« on: March 16, 2018, 11:57:03 AM »
No docs yet. And there is nothing that will list the properties of a control. But there is a function to enumerate the controls of the screen. But only in the very latest builds of Mach.
For all controls that have a background image, there is a scale method property. When a screen is built, you choose a resolution. But the screen may not be actually run at that resolution. Therefore, all of the controls and images are scaled accordingly. Scaling controls is easy. But scaling images is a bit harder. Especially if the scaled image is BIGGER than the original image because pixels have to be added! So that isn't a good thing at all. The fix for that is make the image bigger (pixel wise) than it will ever be displayed scaled. That way, the image is always scaled down. But even scaling an image down has it's issues. Now we are going from more pixels to less. So there are multiple formulas (scale methods) that accomplish this in different ways. Some images will look better when scaled with certain scale methods. You have to choose the one that looks best for your image.
In the hobby version, the buttons are standard Windows controls. And they do things that I may never be able to "undo". In the industrial versions, I wrote my own button that I have complete control over (Advnaced GUI controls).
Now, buttons with transparencies are problematic. Because when the button is pressed, it does move up and to the left to give the effect of being pressed. This is not an issue on an opaque image or regular button because all of the background is repainted. But the background is transparent! So that part of the background is NOT repainted. It is not a bug, per say, but just how the windows operating system works. In the hobby version, the buttons are standard Windows controls. And they do things that I may never be able to "undo". In the industrial versions, I wrote my own button that I have complete control over (Advnaced GUI controls). I would need to see your screen set to determine what is going on. If it is an actual bug or if it is the Windows stock button issue. But I think from your description that it is the stock windows button issue. So make a ticket with Bryanna and attach your profile package (Help -> Support -> Package Current Profile). Tell her to send it to me.
Steve
For all controls that have a background image, there is a scale method property. When a screen is built, you choose a resolution. But the screen may not be actually run at that resolution. Therefore, all of the controls and images are scaled accordingly. Scaling controls is easy. But scaling images is a bit harder. Especially if the scaled image is BIGGER than the original image because pixels have to be added! So that isn't a good thing at all. The fix for that is make the image bigger (pixel wise) than it will ever be displayed scaled. That way, the image is always scaled down. But even scaling an image down has it's issues. Now we are going from more pixels to less. So there are multiple formulas (scale methods) that accomplish this in different ways. Some images will look better when scaled with certain scale methods. You have to choose the one that looks best for your image.
In the hobby version, the buttons are standard Windows controls. And they do things that I may never be able to "undo". In the industrial versions, I wrote my own button that I have complete control over (Advnaced GUI controls).
Now, buttons with transparencies are problematic. Because when the button is pressed, it does move up and to the left to give the effect of being pressed. This is not an issue on an opaque image or regular button because all of the background is repainted. But the background is transparent! So that part of the background is NOT repainted. It is not a bug, per say, but just how the windows operating system works. In the hobby version, the buttons are standard Windows controls. And they do things that I may never be able to "undo". In the industrial versions, I wrote my own button that I have complete control over (Advnaced GUI controls). I would need to see your screen set to determine what is going on. If it is an actual bug or if it is the Windows stock button issue. But I think from your description that it is the stock windows button issue. So make a ticket with Bryanna and attach your profile package (Help -> Support -> Package Current Profile). Tell her to send it to me.
Steve