On 20/06/2022 21:01, Stacho Mudrak wrote:
> Hi, this should be fixed in the latest snapshot - upgrading wxWidgets
> from 3.0 to 3.1 seems to solve the problem.
>
> Could you please try and confirm whether this fix works for you?
Verified fixed. Windows 10, Loch 6.1.0+682fcb3 msys2 #376. Nice
Hi, this should be fixed in the latest snapshot - upgrading wxWidgets from
3.0 to 3.1 seems to solve the problem.
Could you please try and confirm whether this fix works for you?
Thanks, S.
On Mon, 20 Jun 2022 at 21:14, Bruce Mutton wrote:
> > Just got around to updating, using the standard
> Just got around to updating, using the standard "Windows installer" on the
Therion download page. In this release, I have been getting this error on
Windows 10 when trying to run Loch:
> This doesn't sound like something wrong on my machine, but I would have
expected someone else to mention it
On 20/06/2022 16:48, Benoit Martinez wrote:
> Same here with the standard installer on the release page, on Windows 11
Nearly a month after the release and nobody mentioned it yet o_O
I don't know what this says about all of us :D
Something about who is on vacation, the number of Windows Therion
Same here with the standard installer on the release page, on Windows 11
I use the MXE installer and there is no more problem :
https://github.com/therion/therion/actions/runs/2397690531
Benoit
Le lun. 20 juin 2022 à 17:02, Tarquin Wilton-Jones via Therion <
therion@speleo.sk> a écrit :
> On
On 27/05/2022 18:00, Therion via Therion wrote:
> Hi, there is a new release 6.1.0 of Therion.
> Check https://github.com/therion/therion/releases/tag/v6.1.0 for more details.
Just got around to updating, using the standard "Windows installer" on
the Therion download page. In this release, I have
On 20/06/2022 10:19, Bruce Mutton wrote:
> Ha! It was the great Tarquin who provided me with insight one year ago
> https://www.mail-archive.com/therion@speleo.sk/msg08109.html
"I have no memory of this place" Gandalf
But yes, what I am seeing now conflicts with what I wrote then. So
something
> As far as I am aware, the last called layout or statement always wins.
> Certainly since I started using the recipe I have not noticed any
> problems, and my layouts occasionally have conflicting parameters for a
> particular setting (which is why I originally had problems – I was not
> rigorous
Ha! It was the great Tarquin who provided me with insight one year ago
https://www.mail-archive.com/therion@speleo.sk/msg08109.html
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion
Hi Tarquin
I have occasionally had unexpected behaviours due to conflicting layout
calls, and came up with the recipe here for hierarchy and order of calls
some time ago
https://therion.speleo.sk/wiki/bds#order_of_layout_functions_called
As far as I am aware, the last called layout or
Hi folks,
I stumbled on something odd about the "copy" command, which is used in a
"layout". Normally, commands in a layout are interpreted in sequence, so
if you hide something with one command, then show it with a subsequent
command, it will use the second one, and show it:
symbol-hide point
11 matches
Mail list logo
