moonworth.blogg.se - Where is the sort button in word for mac 2011

What's odd is this works well through the Word VBA debugger. Bigger than that, the window (at least on my machine) became globally modal.

But the behavior is odd - if you don't focus on the custom UI window before closing the dialog box, then the custom UI disappears. Unless you subsequently call something like "MsgBox 'something'" in VBA. When you invoke the sub via a button click, etc., the UI disappears or never presents.Set theReturn to theWindowLauncher's openUpdateOutput Property theWindowLauncher : class "MyWindowLauncher" Use framework "/Library/Frameworks/amework" 'If you want this to stick around, you have to do something like. 'I _cannot_ get it to work from the VBA when launched from a button in a document.Ĭommand = "osascript ~/Library/Application\ Scripts//OpenMyUI.scpt" Private Declare Function popen Lib "libc.dylib" (ByVal command As String, ByVal mode As String) As Long Which calls AppleScript (OpenMyUI.scpt) to call public method "show me the interface" in your framework.In this version, Word fields work fine - strings look great and all field fieldText properties can be accessed and set without issue. With this approach, you use vba to call osascript to call out to an applescript that hosts your UI (I know.

Option 2 - Framework w/ osascript + AppleScript I have absolutely no idea why this is failing and at this point I have to believe it's got to do with how the framework is interacting with Word when launched like this. But more times than not I just can't get at the fieldText. When it does work I get "corrupt" string responses. Microsoft Word got an error: Can’t get active document. Set theField to field theIndex of active document it just attempts to return the field text for a given field (by numeric index) on getFieldDataForFieldAtIndex:theIndex Thinking this could be odd behavior with the AppleScript-Objective-C bits when running via the external framework, I actually tried to call out to AppleScript from Objective-C (embed applescript, write wrapper in Obj-C, then load script at runtime). I can only say "corrupted" as the text appears to go from ascii text to some form of unicode characters and also appears to be truncated after that.ĮX: (Then : after "Name" is at position 256)

On those occasions when you can access fieldText (it's still unclear to me how/why this occasionally works), the fieldText is "corrupted" after exactly 256 characters.

For whatever reason, fieldText appears to be : ) //data parameter is nil The entry_index, range, and other components all seem to be fine.

Attempting to access a field's fieldText (aka "data" from Windows) will frequently return data parameter is nil.

This worked well, but for a serious issue with Word field codes. Private Declare Sub MyLibOpenCustomUI Lib "/Library/Frameworks/amework/MyFramework" ()

VBA Macro (OpenOurCustomUI) messages your public C interface.

m file in your framework and expose public methods for accessing your UI (EX: "MyLibOpenCustomUI"). Because your framework is more directly hosted by Word, you have to compile it as 32-bit. You reference the framework in Word and can call out to the public C methods. Into your framework and use those to create view controllers. With this approach, you create public C interfaces

Deploy as framework, call through AppleScript (via VBA.).

Deploy as framework, call into Framework by referencing a public C interface (via VBA).

So I looked at two similar, but different options for doing that: But what I'd really love to do is have this embedded into Word. Hosting through an external dummy app, all works well, too. Running through XCode unit tests I've actually got everything working.

Write Obj-C methods and view controllers to present user with controls.

In some cases where that's just broken ( find, for example), bridge to AppleScript with AppleScript-Objective-C.

Export Word AppleScript headers with sdef, then create Obj-C interfaces using sdp (Scripting Bridge).

There's a super simple UI to do things like this them and then under the hood the create/update/delete functionality is in various classes. Which I realize is absolutely not supported.Įnd of day, the plugin manipulates Word field codes. I realize I'm touching on the intersection of several voodoo topics here, so please bear with me. I'm trying to get a Mac Word faux-plugin to work and I'm running into a few weird issues.