Fixed a problem with the Standalone builder dialogs on Linux

Any Bug Fixes to OpenXTalk should get listed here so we can keep a list and offer thanks to contributors!
Locked
User avatar
tperry2x
Posts: 1778
Joined: Tue Dec 21, 2021 9:10 pm
Location: Britain (Previously known as Great Britain)
Contact:

Fixed a problem with the Standalone builder dialogs on Linux

Post by tperry2x »

Fixed a problem with the Standalone builder dialogs on Linux

-- fixes the "automatically build her" (button not long enough) on Linux, in standalone builder dialog (general tab)
-- replaces the "depreciated" notice under 32-bit mac build (we'll decide when it's depreciated)
-- replaces the word 'Livecode' with 'OXT' in 'Mac' tab, under "Enter the information and have [replaced] write the PLIST file for you

For anyone wanting to download these changes, you can use the individual stack file posted here, and replace your copy.
revstandalonesettings.8.rev.zip
(101.84 KiB) Downloaded 165 times
A full list of recent changes are here:
https://www.tsites.co.uk/sites/openxtalk/changes/

screenshots:
01_adjusted-general-tab.png
01_adjusted-general-tab.png (61.47 KiB) Viewed 3751 times
02_standalone-mac.png
02_standalone-mac.png (74.13 KiB) Viewed 3751 times
User avatar
OpenXTalkPaul
Posts: 1815
Joined: Sat Sep 11, 2021 4:19 pm
Contact:

Re: Fixed a problem with the Standalone builder dialogs on Linux

Post by OpenXTalkPaul »

tperry2x wrote: Sat Sep 23, 2023 7:13 am -- fixes the "automatically build her" (button not long enough) on Linux, in standalone builder dialog (general tab)
Good stuff, Thanks! I'm going to try to take some time to look at these and merge into OXT DPE GitHub repo this weekend.

The thing about the fonts not fitting thing, this happens with different versions of macOS too, particularly when the App is in HiDPI mode and a stack designed back when most people had 1024x768 x72 DPI screens, in Addition the standard macOS system fonts have changed over the years, it hasn't been Lucida Grande in many years, yet that's what is currently hard coded into the IDE (as a string literal / constant).

A lot of the other theming stuff is 'hard coded' / constants in the IDE scripts. I've been thinking a lot about how that should all be in an IDE theming library. Then it can allow the IDE user to pick from a range of IDE color+icons+fonts+syntax-coloring sets, and we build a stack to facilitate making new theme sets. This would also likely create a need to update a few of IDE stacks revMenuBar, Project Browser, etc. to pull their icons from the selected theme's folder, in the theme directory of IDE main resource folder, instead of from their own folders in the palettes directory where some (revMenuBar) are currently read from.
Locked

Who is online

Users browsing this forum: No registered users and 0 guests