Do you get the class editor if you click a class token?
Yes it’s opening correctly here. I’m also on Intel running Sonoma 14.1.1.
1 Like
I can select a class in the class window, and the right click works as well
I am on Intel running on macOS v13.6.1
1 Like
I’m unable to assign an alternative image.
What solves the issue is to open the class manager from the menu bar and the editor will show when you click on it. It’s the same approach I frequently have to use the same approach for images as the asset manager often refuses to open when clicking on a new image bric. Once opened from the menu bar it behaves correctly.
Try below and you should be good.
Note: You’re hijacking an attribute used by Blocs which could potentially create all sorts of other issues. Use at your own risk!
<script>
document.addEventListener("DOMContentLoaded", function() {
var scrollElements = document.querySelectorAll('.my-class');
scrollElements.forEach(function(element) {
element.setAttribute('data-scroll', "");
});
const locomotiveScroll = new LocomotiveScroll();
});
</script>
Hey @Jerry, do you find that dragging the alternate image from the Asset Manager to the alternate image well works correctly?
This works for me, but I get the same issue as you when clicking the well in the sidebar and then selecting in Asset Manager.
When adding a custom Bloc Blocs Crashes.
It holds just a bunch of Divs for an infinite slider.
Crash Report:
Exception Name: NSRangeException
Description: *** -[__NSArrayM objectAtIndexedSubscript:]: index 0 beyond bounds for empty array
User Info: (null)
0 CoreFoundation 0x00007ff813075fa6 __exceptionPreprocess + 242
1 libobjc.A.dylib 0x00007ff812b6b231 objc_exception_throw + 48
2 CoreFoundation 0x00007ff812fef6ae -[__NSCFString hasSuffix:] + 0
3 Blocs 0x0000000101802a44 Blocs + 776772
4 Blocs 0x000000010180c2fa Blocs + 815866
5 WebKit 0x00007ff91704c663 _ZN28ScriptMessageHandlerDelegate14didPostMessageERN6WebKit12WebPageProxyEONS0_13FrameInfoDataERN3API12ContentWorldERN7WebCore21SerializedScriptValueE + 271
6 WebKit 0x00007ff9173fa2c6 _ZN6WebKit29WebUserContentControllerProxy14didPostMessageEN3WTF23ObjectIdentifierGenericINS_26WebPageProxyIdentifierTypeENS1_38ObjectIdentifierMainThreadAccessTraitsEEEONS_13FrameInfoDataEyRKNSt3__14spanIKhLm18446744073709551615EEEONS1_17CompletionHandlerIFvOSB_RKNS1_6StringEEEE + 626
7 WebKit 0x00007ff91771acca _ZN3IPC18handleMessageAsyncIN8Messages29WebUserContentControllerProxy14DidPostMessageEN6WebKit29WebUserContentControllerProxyES5_FvN3WTF23ObjectIdentifierGenericINS4_26WebPageProxyIdentifierTypeENS6_38ObjectIdentifierMainThreadAccessTraitsEEEONS4_13FrameInfoDataEyRKNSt3__14spanIKhLm18446744073709551615EEEONS6_17CompletionHandlerIFvOSG_RKNS6_6StringEEEEEEEvRNS_10ConnectionERNS_7DecoderEPT0_MT1_T2_ + 209
8 WebKit 0x00007ff91771abe6 _ZN6WebKit29WebUserContentControllerProxy17didReceiveMessageERN3IPC10ConnectionERNS1_7DecoderE + 64
9 WebKit 0x00007ff917732b1d _ZN3IPC18MessageReceiverMap15dispatchMessageERNS_10ConnectionERNS_7DecoderE + 223
10 WebKit 0x00007ff91737f029 _ZN6WebKit15WebProcessProxy17didReceiveMessageERN3IPC10ConnectionERNS1_7DecoderE + 31
11 WebKit 0x00007ff91772ec37 _ZN3IPC10Connection15dispatchMessageENSt3__110unique_ptrINS_7DecoderENS1_14default_deleteIS3_EEEE + 269
12 WebKit 0x00007ff91772f1b9 _ZN3IPC10Connection24dispatchIncomingMessagesEv + 627
13 JavaScriptCore 0x00007ff82fa08fce _ZN3WTF7RunLoop11performWorkEv + 430
14 JavaScriptCore 0x00007ff82fa09d5a _ZN3WTF7RunLoop11performWorkEPv + 26
15 CoreFoundation 0x00007ff8130032c7 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
16 CoreFoundation 0x00007ff813003269 __CFRunLoopDoSource0 + 157
17 CoreFoundation 0x00007ff813003034 __CFRunLoopDoSources0 + 215
18 CoreFoundation 0x00007ff813001cb1 __CFRunLoopRun + 919
19 CoreFoundation 0x00007ff813001352 CFRunLoopRunSpecific + 557
20 HIToolbox 0x00007ff81d8a39d9 RunCurrentEventLoopInMode + 292
21 HIToolbox 0x00007ff81d8a3616 ReceiveNextEventCommon + 201
22 HIToolbox 0x00007ff81d8a3531 _BlockUntilNextEventMatchingListInModeWithFilter + 66
23 AppKit 0x00007ff816611885 _DPSNextEvent + 880
24 AppKit 0x00007ff816f05348 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1304
25 AppKit 0x00007ff816602dfa -[NSApplication run] + 603
26 AppKit 0x00007ff8165d6e10 NSApplicationMain + 816
27 dyld 0x00007ff812b9f3a6 start + 1942
1 Like
As a tourist route that ‘works’. However, it will change the original shown image as well which then will need to be changed back.
Looks like it’s been this way since Blocs V4, so you and your intel laptop win bug finder of the year 2023.
Fix included in Fridays beta.
2 Likes
interesting I’ll test this one out.
LoL. 
I think it’s the first time ever I used it. Summer is approaching so I start looking for tickbox solutions 
1 Like
I’ll check on the M1 later this PM. DIVs and Intel are not best friends at the moment. 
Hey, @Norm.
A big 
on the M1 as well.
M1 crash report:
Exception Name: NSRangeException
Description: *** -[__NSArrayM objectAtIndexedSubscript:]: index 0 beyond bounds for empty array
User Info: (null)
0 CoreFoundation 0x0000000182b86800 __exceptionPreprocess + 176
1 libobjc.A.dylib 0x000000018267deb4 objc_exception_throw + 60
2 CoreFoundation 0x0000000182afcfc0 -[__NSCFString hasSuffix:] + 0
3 Blocs 0x00000001028fdb8c Blocs + 596876
4 Blocs 0x0000000102906390 Blocs + 631696
5 WebKit 0x00000001a577f934 _ZN28ScriptMessageHandlerDelegate14didPostMessageERN6WebKit12WebPageProxyEONS0_13FrameInfoDataERN3API12ContentWorldERN7WebCore21SerializedScriptValueE + 228
6 WebKit 0x00000001a5b8e920 _ZN6WebKit29WebUserContentControllerProxy14didPostMessageEN3WTF23ObjectIdentifierGenericINS_26WebPageProxyIdentifierTypeENS1_38ObjectIdentifierMainThreadAccessTraitsEEEONS_13FrameInfoDataEyRKNSt3__14spanIKhLm18446744073709551615EEEONS1_17CompletionHandlerIFvOSB_RKNS1_6StringEEEE + 668
7 WebKit 0x00000001a5ed6998 _ZN6WebKit29WebUserContentControllerProxy17didReceiveMessageERN3IPC10ConnectionERNS1_7DecoderE + 336
8 WebKit 0x00000001a5eeedb4 _ZN3IPC18MessageReceiverMap15dispatchMessageERNS_10ConnectionERNS_7DecoderE + 264
9 WebKit 0x00000001a5afa794 _ZN6WebKit15WebProcessProxy17didReceiveMessageERN3IPC10ConnectionERNS1_7DecoderE + 40
10 WebKit 0x00000001a5eea3f4 _ZN3IPC10Connection15dispatchMessageENSt3__110unique_ptrINS_7DecoderENS1_14default_deleteIS3_EEEE + 332
11 WebKit 0x00000001a5eeaa48 _ZN3IPC10Connection24dispatchIncomingMessagesEv + 656
12 JavaScriptCore 0x000000019e840d38 _ZN3WTF7RunLoop11performWorkEv + 204
13 JavaScriptCore 0x000000019e841c08 _ZN3WTF7RunLoop11performWorkEPv + 36
14 CoreFoundation 0x0000000182b11cfc __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
15 CoreFoundation 0x0000000182b11c90 __CFRunLoopDoSource0 + 176
16 CoreFoundation 0x0000000182b11a00 __CFRunLoopDoSources0 + 244
17 CoreFoundation 0x0000000182b105f0 __CFRunLoopRun + 828
18 CoreFoundation 0x0000000182b0fc5c CFRunLoopRunSpecific + 608
19 HIToolbox 0x000000018d089448 RunCurrentEventLoopInMode + 292
20 HIToolbox 0x000000018d089284 ReceiveNextEventCommon + 648
21 HIToolbox 0x000000018d088fdc _BlockUntilNextEventMatchingListInModeWithFilter + 76
22 AppKit 0x00000001862eac54 _DPSNextEvent + 660
23 AppKit 0x0000000186ac0ebc -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 716
24 AppKit 0x00000001862de100 -[NSApplication run] + 476
25 AppKit 0x00000001862b53cc NSApplicationMain + 880
26 dyld 0x00000001826b90e0 start + 2360
1 Like
I’m a humble person so no prize-giving ceremony is needed but thank you for the 3 weeks holiday to the Maldives. Flights, accommodation, and all meals/drinks included. 
2 Likes
I copied a single class, but then when I wanted to paste it on another header Blocs threw up an internal crash error. I said continue and it crashed anyway, so I sent in the report.
After restarting up pops a panel saying the port is being used by another process and no other version of Blocs is open. There do seem to be a lot of crashes reported lately.
The internal crash flag is set to true during betas which means any potential crash is flagged up and an alert is shown. In some of these situations Blocs would continue to run, so you will see more of these alerts during betas and testing. It helps to catch the silent bugs.
1 Like
I understand that but it went ahead and literally crashed when I pressed continue, before I could save the changes.
Why have the up and down arrows become unusable?
Oh that’s caused by the recent support to scroll canvas with arrow keys. It’s stealing those events.
It’s fixed and ready for tomorrow. 
1 Like
That is one of the cases when it actually would crash 
The OS manages that alert so it’s likely continue couldn’t work, I think that button is shown by default regardless of error.