A disadvantage of Smalltalk is its lack of static type checking. If you change something fundamental, it can break things elsewhere without warning. Testing every feature and button and menu before every update is not an option (many thousands), so we have to rely on our memory of the dependencies.
Gladly those broken links can be fixed with patches immediately.
Great to have the new dynamics parameter. However, when changing individual values with the mouse up/down, this parameter currently jumps by distances of 1, which is huge for this parameter. The increments should be much smaller.
Also changes with the mouse directly can only be done by such large increments at the moment.
BTW: Perhaps a modifier key would be useful to change the increaments to fine or coarse for this or other parameters (If that is quick to implement -- I guess other things are currently more important).
I had a hard time reproducing this at first. It happens at certain HiDPI scalings (150%, 225% for instance) and also depends on current window size, whether width in pixels is even or odd. Imagine that! Because Windows still does graphics with integers (floating point coordinates are standard today), there seem to be rounding and truncation issues! This means we have to query the current scaling factor and add/subtract one non-existent phantom pixel depending on nonsense conditions. That's a totally stupid mess. Developer's nightmare come true.
Scrollbars suddenly have borders, menu items randomly slip sideways, the playhead leaves ugly trails, and possibly a lot more. Because integers.
Unless there's a simple fix, like forcing all window sizes to be even, I have no idea yet how to fix this.
Fixed issues with horizontal scrolling and content visibility
Nope. After a certain zoom, the content still escapes to the right.
Editing: Switching symbol type focus should unselect all
Editing: Simplified click-and-hold menu for symbol types
Nice.
Unless there's a simple fix, like forcing all window sizes to be even
Meh, whatever it takes.
I've noticed, though, that with the -H option, while I don't get smaller GUI elements anymore (did it use to work like that or I just remember wrong?), it solves all Windows issues - popup-outside-the-screen, glitchy text... Can you maybe enable something like that by default on Windows? Unless there are side effects.
Just had a bluescreen when trying to start Synfire on Win 10. Sigh.
Are those still a thing? Didn't get one since a decade ago.
Sure. We can disable HiDPI altogether and be fine. But the blurry appearance with -H is much worse, IMO. With scaling at 100, 150, 200, 250 or 300 percent, most glitches go away. We will show a dismissable message to let the user know this at startup.
Text input is still off for very long text, but not as bad as with odd scalings like 175, 225. It works better with some fonts, but only at some sizes. It's a puzzle almost impossible to solve. I have yet to see a single Windows application (even Microsofts own) that works flawlessly with HiDPI. Microsoft totally botched this. Pixels is the most stupid coordinate system they could have choosen and their font handling is broken, too. The extent to which this blocks our business from moving ahead amounts to a crime.
HiDPI ? Working on 27" LG monitor 1280x720 with Synfire 1.10 is ok . Can you release a Beta Express . Can play with V2 . restarting the software every 30 min is not a problem during testing.
The file and Library menus lookup recently used files whether they still exist. You may experience a slowdown if the list is extremely long or you have a slow network drive or something.
Only while using the menus. It's quite a severe slow down. Definitely related to scanning the recent items lists for libraries, arrangements etc. All other menus are fine. Is no one else experiencing this with the latest update?
Only while using the menus. It's quite a severe slow down. Definitely related to scanning the recent items lists for libraries, arrangements etc. All other menus are fine. Is no one else experiencing this with the latest update?
Are there any problems with the key commands?
I tried to map quantize to "q" but the keystroke does nothing.
Also, I'm looking for keyboard commands for the toolbar, don't they exist?
Also, there is no keyboard command for the key commands itself....
Sa., 23.07.2022 - 12:48 Permalink
Sorry, a patch is already online.
A disadvantage of Smalltalk is its lack of static type checking. If you change something fundamental, it can break things elsewhere without warning. Testing every feature and button and menu before every update is not an option (many thousands), so we have to rely on our memory of the dependencies.
Gladly those broken links can be fixed with patches immediately.
Sa., 23.07.2022 - 19:08 Permalink
Great to have the new dynamics parameter. However, when changing individual values with the mouse up/down, this parameter currently jumps by distances of 1, which is huge for this parameter. The increments should be much smaller.
Also changes with the mouse directly can only be done by such large increments at the moment.
BTW: Perhaps a modifier key would be useful to change the increaments to fine or coarse for this or other parameters (If that is quick to implement -- I guess other things are currently more important).
Sa., 23.07.2022 - 20:20 Permalink
> when changing individual values with the mouse up/down
Correction: with the cursor keys...
So., 24.07.2022 - 20:48 Permalink
Synfire 2.0.7 build #4
Mi., 27.07.2022 - 10:39 Permalink
Regarding graphics glitches on Windows:
I had a hard time reproducing this at first. It happens at certain HiDPI scalings (150%, 225% for instance) and also depends on current window size, whether width in pixels is even or odd. Imagine that! Because Windows still does graphics with integers (floating point coordinates are standard today), there seem to be rounding and truncation issues! This means we have to query the current scaling factor and add/subtract one non-existent phantom pixel depending on nonsense conditions. That's a totally stupid mess. Developer's nightmare come true.
Scrollbars suddenly have borders, menu items randomly slip sideways, the playhead leaves ugly trails, and possibly a lot more. Because integers.
Unless there's a simple fix, like forcing all window sizes to be even, I have no idea yet how to fix this.
Mi., 27.07.2022 - 12:39 Permalink
> also depends on current window size, whether width in pixels is even or odd.
Ouch!
BTW: Just had a bluescreen when trying to start Synfire on Win 10. Sigh. And I just moved from (an oldish) Mac to Windows. ;-)
Do., 28.07.2022 - 22:30 Permalink
Nope. After a certain zoom, the content still escapes to the right.
Nice.
Meh, whatever it takes.
I've noticed, though, that with the -H option, while I don't get smaller GUI elements anymore (did it use to work like that or I just remember wrong?), it solves all Windows issues - popup-outside-the-screen, glitchy text... Can you maybe enable something like that by default on Windows? Unless there are side effects.
Are those still a thing? Didn't get one since a decade ago.
Fr., 29.07.2022 - 11:27 Permalink
Sure. We can disable HiDPI altogether and be fine. But the blurry appearance with -H is much worse, IMO. With scaling at 100, 150, 200, 250 or 300 percent, most glitches go away. We will show a dismissable message to let the user know this at startup.
Text input is still off for very long text, but not as bad as with odd scalings like 175, 225. It works better with some fonts, but only at some sizes. It's a puzzle almost impossible to solve. I have yet to see a single Windows application (even Microsofts own) that works flawlessly with HiDPI. Microsoft totally botched this. Pixels is the most stupid coordinate system they could have choosen and their font handling is broken, too. The extent to which this blocks our business from moving ahead amounts to a crime.
Fr., 29.07.2022 - 12:51 Permalink
Sounds fine to me.
So., 31.07.2022 - 19:16 Permalink
HiDPI ? Working on 27" LG monitor 1280x720 with Synfire 1.10 is ok . Can you release a Beta Express . Can play with V2 . restarting the software every 30 min is not a problem during testing.
So., 31.07.2022 - 22:32 Permalink
Express and Sparks do not yet exist. Their different feature sets still need to be balanced out and tested.
Sounds easy, but is a lot of work.
Mo., 01.08.2022 - 21:31 Permalink
Having crashes when entering chords. crash reports submitted.
Di., 02.08.2022 - 17:51 Permalink
Error opening library
Do., 04.08.2022 - 10:06 Permalink
Can you send the crashing library to support at cognitone dot com?
Do., 11.08.2022 - 18:32 Permalink
Severe slow down for me when engaging the File or Library menus (or associated tabs).
Do., 11.08.2022 - 20:36 Permalink
The file and Library menus lookup recently used files whether they still exist. You may experience a slowdown if the list is extremely long or you have a slow network drive or something.
Do., 11.08.2022 - 20:53 Permalink
No network drives being used. All files exist on local drives. No problems with previous versions.
Fr., 12.08.2022 - 11:53 Permalink
Is the slowdown with the menus only, or does it last after using the menus?
Fr., 12.08.2022 - 12:31 Permalink
Only while using the menus. It's quite a severe slow down. Definitely related to scanning the recent items lists for libraries, arrangements etc. All other menus are fine. Is no one else experiencing this with the latest update?
Fr., 12.08.2022 - 12:31 Permalink
Only while using the menus. It's quite a severe slow down. Definitely related to scanning the recent items lists for libraries, arrangements etc. All other menus are fine. Is no one else experiencing this with the latest update?
So., 14.08.2022 - 10:59 Permalink
Are there any problems with the key commands?
I tried to map quantize to "q" but the keystroke does nothing.
Also, I'm looking for keyboard commands for the toolbar, don't they exist?
Also, there is no keyboard command for the key commands itself....