What I'm adding, and what I'm planning next...

[tperry2x]

While you're at it: There's a decades old bug in it concerning the resize script: Quite important information (number of lines of script) is always hidden outside to the right - so each time you have to manually adjust it :/

No problem, thanks Axwald - I'll sort that too.

Have fun!

I try

edit: done. You now have resizers that actually work, but the default also fits the columns to the window:

resizers.png (181.9 KiB) Viewed 4488 times

dark-mode.png (207.04 KiB) Viewed 3867 times

[tperry2x]

Paul also let me know that when you dragged something off the tools palette in OXT lite, it no longer showed a preview of what you were dragging into your new stack. Neither did it hilight the stack it was being dragged into. (oops! this was accidentally broken when I was sorting the other tools, so I've now fixed that too).

drag-tools.gif (363.6 KiB) Viewed 2942 times

[richmond62]

But the image attached to that posting shows up as bust, on Android at least.

[micmac]

Effect Window.jpg (65.04 KiB) Viewed 2932 times

Hi there

Another longstangding bug is with the Effect Window:

A selected object, fx a Field —> Object Inspector —> Effect.

Problem 1:
If you work on a stack that fills the whole screen AND you make some click in that stack, the Effect Window can no longer be called to the front. You will have to restart.

Problem 2:
If you work on a stack AND you make some click in that stack, the Effect Window becomes unresponsive and brakes to pieces.

on MacOS


Mic

[tperry2x]

Hi Mic.
Yes, this has been mentioned somewhere on this forum before.
It's a bit of a nightmare to fix because it seems to involve rewriting most of the inspector.

I had started to do it, but hit a brick wall because some of the custom properties are not documented and not named correctly in the inspector. That's where I'd need someone who is an array master, highly skilled with custom properties, to lend a hand.

You could always use this stack to generate the effects you want, then copy and paste it into your stack.
I know that's not ideal, but it's what I have at the moment:

filter.png (35.64 KiB) Viewed 2926 times

[micmac]

Thank you Tom

Im not certain what you mean be "then copy and paste it into your stack"

Mic

[tperry2x]

Once you'd got that graphic looking how you'd like, by adjusting the sliders - you could select the pointer tool.
Click the graphic, so it's selected:

select.png (22.04 KiB) Viewed 2916 times

Edit menu > copy object

copy.png (29.15 KiB) Viewed 2916 times

Make a new stack, then edit menu > paste object

paste.png (44.1 KiB) Viewed 2916 times

There you go, your object with the effects that you want are now in your stack. It's a workaround until I get the inspector sorted out.

[micmac]

Thanks Tom

So I deleted the graphics and put a field instead and the script did not work anymore...

Mic

[tperry2x]

Yes, at the moment - all that stack does is apply the effects to a graphic. This is why it needs making into a fully-fledged inspector palette. It's just a simplistic method of applying effects to the graphic at the moment, rather than being something that currently applies effects to whatever object is selected. It could be amended to do that though.

[tperry2x]

Are there any final, late-breaking-changes, that anyone would like included in an upcoming v1.10 build?
(I'm thinking of leaving experimental windowing stuff out, and saving this for a future release). So what I'm saying nicely is that v1.10 will not be any further forward regarding windowing issues under various 'buntu Linuxes, as this is a larger job and not an overnight thing - so please don't expect that to be fixed for the latest ubuntu.

This is mainly just to take all the v1.09 updates and merge them into a v1.10 build. BUT, if there's anything you really want added before I do that, please let me know here.

[tperry2x]

...HOLD the "funky-monkey" new window furniture for a, possible, 1.11 or 11.69.
Get a 1.10 'out' and then turn your attentions elsewhere . . .

Okay, no problem. I may be jumping the gun (well, I am - but I made a copy and experimented with the alternative window buttons on the inspector). Works just about as well as the original ones did - still gives the same weird window juggling in the 'buntus, even when I drawer stack 'revtools', or set the decorations to empty. So I'm a bit back to the drawing board there. It does at least solve the dark mode issue with the titlebar on Microsoft Windows though

Short version is I won't be including this in v1.10 as mentioned.

wd-test-in-1_11.png (82.19 KiB) Viewed 2475 times

[richmond62]

Is it just me, or does the 'thing' about Dark Mode really matter that much?

Surely, as end-users are using OXT to write standalone programs any theming is largely up to them.

Personally I have always thought that FORM (what the thing looks like) is my responsibility, and FUNCTIONALITY is what makes an xTalk IDE so super.

[tperry2x]

Is it just me, or does the 'thing' about Dark Mode really matter that much?

To me, yes - I work in dark mode 90% of the time, and to have something that doesn't understand dark mode is a big disappointment. I know this matters to a lot of other people too, but not to everyone. It's a personal preference thing.
I'm talking about how the IDE deals with dark mode more than anything. Standalones can of course be customised as it's essentially just the stack without the accompanying IDE stuff.

On Microsoft Windows, it was just the titlebars that I couldn't get to show up correctly - but if I use custom window decorations, then this sidesteps that issue.

[richmond62]

Ah: OK: that's clear.

On MacOS 12 and 15 I always use Dark Mode as I fell in love with it instantly on its release in MacOS Catalina.

I know that you can do 'fake dark mode' with MacOS 104, 10.6, and 10.7 (The other versions of MacOS I use fairly regularly), but as the non-Dark MacOS GUI was a lot nicer than what 11, 12, and so on cough up, I have not bothered.

[tperry2x]

Just a note, that v1.10 is now in the downloads section.

[richmond62]

I am just downloading 1.10 onto my MacOS 15 machine at work.

Launches: no obvious problems.

Thank you very much.

[micmac]

1.10

Mac Ventura

First time I did not have to de-quarantine the app

Mic

[richmond62]

Same as previously on Xubuntu 24.10 . . .

[tperry2x]

Same as previously on Xubuntu 24.10 . . .

Yes, please see my earlier post about that.

So what I'm saying nicely is that v1.10 will not be any further forward regarding windowing issues under various 'buntu Linuxes,

The issue will still be the same, because this is a larger engine incompatibility after recent ubuntu updates. My hope is they rectify it. If they don't, then I will revisit it - but it's not a simple in-engine fix I'm guessing.

So the short version is, it will still be broken because I've not done anything about it. I'm waiting to see what the Ubuntu community do in a future update. (I will note, Ubuntu 24 was terrible as far as performance goes, before I even launched OXT) - it threw a kernel panic and logged me out of the session at least twice (when using the XFCE and "Ubuntu Session" options). As I mentioned, the quick fix is to install a different desktop session ("mate-desktop-environment") and log into that. My hope is ubuntu switch their desktop environment to something else at this point, or revert whatever they recently changed, as it seems really unstable.

Alternative desktop environments:

[richmond62]

I suspect the problem lies with XFCE.