SuperEdit 4.8 Additions

[codegreen]

So far (except as relates to Japanese file open/save dialogs) we haven't really talked about changes to SuperEdit in the 4.8 update.

These fall into four main categories:

Bug Fixes

There are hundreds of course. Most notably, you once again can safely edit the contents of a background field in multiple card windows at the same time.

Contextual Menus

You can now right-click on most objects in the UI (including in overview windows) to pop up a menu of available operations (instead of double-clicking, shift-double-clicking, option-double-clicking, or whatever). One exception in b19 is the list of data-fork resources (a fix will be in b20).

Keyboard Shortcuts

There's now a keyboard shortcut for almost anything you could want to do in SE overview (i.e., 'list') windows - rotating through them, zooming, tiling, navigating, selecting, opening parent items/folders, etc. If you prefer to keep your hands on the keyboard as much as possible in SE, these should make you smile...

Alignment Guides

Card editing windows now have optional guides and rulers that make it a snap to align the edges, centers, or text baselines of objects, or to quickly create them at or move them to specific locations without having to resort to the dreaded Sizes dialog.

If you have questions, sing out...

-Mark

[sctell]

Alignment Guides

Card editing windows now have optional guides and rulers that make it a snap to align the edges, centers, or text baselines of objects, or to quickly create them at or move them to specific locations without having to resort to the dreaded Sizes dialog.

I have noticed in b19 that the rulers continually flash as you move the mouse.

Is this to be expected?

All the best

Terry

[sctell]

Contextual Menus

You can now right-click on most objects in the UI (including in overview windows) to pop up a menu of available operations (instead of double-clicking, shift-double-clicking, option-double-clicking, or whatever). One exception in b19 is the list of data-fork resources (a fix will be in b20).

This is excellent but...

The popup menus seem to pickup and be displayed in the system font/size and look odd next to the minuscule font sizes in the object lists.

Are the font sizes of the object lists to be increased? or better yet be user adjustable?

This is the main reason I avoid SuperEdit.


All the best

Terry

[Scott]

I have noticed in b19 that the rulers continually flash as you move the mouse.

Is this to be expected?

I have seen this off and on during the development cycle, but don't remember seeing it for quite some time (and can't reproduce it here under a variety of Intel HD Graphics systems).

Anybody else here seeing this?

[parttimeprogrammer]

Anybody else here seeing this?

All is well here, MBP2015 OS X 10.11.5

[codegreen]

I have noticed in b19 that the rulers continually flash as you move the mouse.

I saw this weird behavior myself a couple of times myself several months ago, but since then have been totally unable to reproduce it.

If you have a recipe for this PLEASE by all means post it! I REALLY want to squash this one...

-Mark

[sctell]

If you have a recipe for this PLEASE by all means post it! I REALLY want to squash this one...

I have a test project containing four buttons and a field which I have been using to test alignment.

This morning it started up and there was no problem using the guides, then I chose the alignment palette from the menu and did not use any of the options. The alignment palette opened then I closed it again and the rulers are now flashing.

I will repeat this a few times and see if it is consistent.

All the best

Terry

[sctell]

I will repeat this a few times and see if it is consistent.

It's not consistent.


I will keep looking.


All the best

Terry

[codegreen]

It's not consistent.

I will keep looking.

That's what makes this one so maddening -- it seems to appear based not so much on what you do but rather how you do it.

FWIW it happens because the grid is actually in an overlay window, so the redraw cycles of both must be perfectly synchronized. Somehow though they occasionally manage to get out-of-step. Unfortunately without a precise recipe it's nearly impossible to catch in a bottle...

Dunno if that helps, but at least now you sorta know what you're looking for!

-Mark

[sctell]

I have noticed this in the console and believe it gets posted to the console as the flickering starts.

Is this something you have been doing in the code?

15/06/2016 14:08:38.033 WindowServer[160]: disable_update_likely_unbalanced: UI updates still disabled by application "SuperEdit" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.
15/06/2016 14:08:38.033 SuperEdit 4.8[4287]: void CGSUpdateManager::log() const: conn 0xea5b legacy 1
15/06/2016 14:08:38.033 SuperEdit 4.8[4287]: Backtrace (at 76654.4):
15/06/2016 14:08:38.033 SuperEdit 4.8[4287]: void CGSUpdateManager::log() const: 0 CoreGraphics 0x965fe04f CGSDisableUpdate + 207
15/06/2016 14:08:38.033 SuperEdit 4.8[4287]: void CGSUpdateManager::log() const: 1 HIToolbox 0x9cf028e3 DisableScreenUpdates + 19
15/06/2016 14:08:38.033 SuperEdit 4.8[4287]: void CGSUpdateManager::log() const: 2 SuperEdit 4.8 0x0007132e updatemodifieds + 14
15/06/2016 14:08:38.033 SuperEdit 4.8[4287]: void CGSUpdateManager::log() const: 3 SuperEdit 4.8 0x0003165e runedit + 734
15/06/2016 14:08:38.033 SuperEdit 4.8[4287]: void CGSUpdateManager::log() const: 4 SuperEdit 4.8 0x0007941b main + 155
15/06/2016 14:08:38.033 SuperEdit 4.8[4287]: void CGSUpdateManager::log() const: 5 SuperEdit 4.8 0x000021b9 _start + 208
15/06/2016 14:08:38.033 SuperEdit 4.8[4287]: void CGSUpdateManager::log() const: 6 SuperEdit 4.8 0x000020e8 start + 40

All the best

Terry

[sctell]

A few notes:

1. When the flickering starts I cannot stop it until SE quits.

2. If you hide guides and show guides the flickering starts again.

3. If you carefully move your mouse to the edge of the window when flickering the guides always hide when going beyond the bounds. ( could this be a flag setting that is incorrect)

4. The flickering seems like a faulty flag reseting and setting itself as the mouse moves.

Could it be?

All the best

Terry

[sctell]

I have noticed this in the console and believe it gets posted to the console as the flickering starts.

Sat there for 10 minutes manipulating test project with the console open behind with a blank display until it happened again and sure enough as soon as the flickering started got this in the console:

15/06/2016 19:14:11.425 WindowServer[160]: disable_update_timeout: UI updates were forcibly disabled by application "SuperEdit" for over 1.00 seconds. Server has re-enabled them.
15/06/2016 19:14:25.424 WindowServer[160]: disable_update_likely_unbalanced: UI updates still disabled by application "SuperEdit" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.
15/06/2016 19:14:25.425 SuperEdit 4.8[4466]: void CGSUpdateManager::log() const: conn 0x18c3b legacy 1
15/06/2016 19:14:25.425 SuperEdit 4.8[4466]: Backtrace (at 81000.8):
15/06/2016 19:14:25.425 SuperEdit 4.8[4466]: void CGSUpdateManager::log() const: 0 CoreGraphics 0x965fe04f CGSDisableUpdate + 207
15/06/2016 19:14:25.425 SuperEdit 4.8[4466]: void CGSUpdateManager::log() const: 1 HIToolbox 0x9cf028e3 DisableScreenUpdates + 19
15/06/2016 19:14:25.425 SuperEdit 4.8[4466]: void CGSUpdateManager::log() const: 2 SuperEdit 4.8 0x0007132e updatemodifieds + 14
15/06/2016 19:14:25.425 SuperEdit 4.8[4466]: void CGSUpdateManager::log() const: 3 SuperEdit 4.8 0x0003165e runedit + 734
15/06/2016 19:14:25.425 SuperEdit 4.8[4466]: void CGSUpdateManager::log() const: 4 SuperEdit 4.8 0x0007941b main + 155
15/06/2016 19:14:25.425 SuperEdit 4.8[4466]: void CGSUpdateManager::log() const: 5 SuperEdit 4.8 0x000021b9 _start + 208
15/06/2016 19:14:25.425 SuperEdit 4.8[4466]: void CGSUpdateManager::log() const: 6 SuperEdit 4.8 0x000020e8 start + 40

Don't know if it's relevant or not.

All the best

Terry

[sctell]

Have been reading about NSDisableScreenUpdates and NSEnableScreenUpdates, could not find the HiToolbox equivalents but suspect the underlying is a call to the same place. For those interested who have seen this flickering here is a description for NSDisableScreenUpdates. I don't know but would not be surprised if the issue is related to the 1 second rule somewhere along the line.

Prevents drawing operations from being flushed to the screen for all windows belonging to the calling process. When you re-enable screen updates (with NSEnableScreenUpdates) screen flushing for all windows belonging to the calling process appears to be simultaneous. You typically call this function so that operations on multiple windows appear atomic to the user. This is a technique particularly useful for synchronizing parent and child windows. Make sure that the period after calling this function and before reenabling updates is short; the system only allow updating to be disabled for a limited time (currently one second) before automatically reenabling updates. Successive calls to this function are placed on a stack and must be popped off that stack by matching NSEnableScreenUpdates calls.

All the best

Terry