All right, after having worked through Cocoa Dev Central's "Build a Core Data Application" tutorial I started experimenting with building my own application, using the code and .nib file from the tutorial as a reference to make sure that things are put together properly. Overall I've been managing pretty well with it, however I seem to have hit a snag.
I'm building a form with two NSTextView boxes, like in the tutorial, however linked to different attributes within the same entity. All the other controls work properly and save/refresh their values when I go between records (minus some date box silliness, where the second box doesn't want to save its values). I have checked all of the bindings settings and the NSArrayController against the .nib from the tutorial to see where things could be off; that led to unhooking the first text box and then reconnecting it with the same settings and it suddenly magically working. The second box doesn't want to behave, however, and persists in breaking the program (the debugger shows up, listing all manner of variables and memory addresses and stuff that's frankly quite beyond my comprehension).
Currently, the offending box is configured as follows:
Class: NSTextView
Value: Bound to `history`
Controller Key: selection
Model Key Path: `description`
Checked: Allows Editing Multiple Values Selection
Checked: Conditionally Sets Editable
Checked: Raises For Not Applicable Keys
Any insight into what's going on here?
All right, got it figured out. Changed the attribute name from description and it started behaving; seems the name was triggering something when it compiled that the initial bug check missed.
Related
I recently replaced Aloha editor with HalloJS in my CMS for several reasons, the most important of which are HalloJS being more leightweight and a lot easier to customize. A severe problem I have however run into is that it doesn't seem possible to init the HalloJS toolbar to elements that are dynamically added to the DOM after initial initialization of Hallo.
Judging from the source, something is definitlety happening, since a div#hallojstoolbar appears upon clicking the newly created editable in the DOM, but it isn't visible and its widgets, controls & dialogs aren't to be found anywhere.
Ok, I feel slightly silly now. After sifting through heaps of 'foo is not a function' notices in the console before posting this question I found out that it wouldn't work because several of the options set in initialization weren't read/set (anymore).
After manually setting some of the vars at the point they were supposed to be used but missing, I discovered that HalloJS was using all the plugin's default options, such as the contextualToolbar (where I am using the static one) and, more importantly, an empty plugin list. I find this weird, bacause after dynamically adding my new element I tried calling HalloJS with all options set, to no result.
However, if you copy all your prefered option settings (including all plugin references!) into the jQuery.widget('IKS.hallo') settings in the hallo.js file, everything works as expected.
I chose to post this on here anyway since there isn't a single reference to any problem remotely related to this anywhere on the netz. So I figured this could save someone googling the same issue in the future the time it took me to figure this out.
Ok this may be a vague question but I have an issue recognizing a webelement in one module (tab) but works completely fine in another tab. This is the same webelement. Everything seems to be same. It's the same form on the gui side with same properties and values.
Now this is another weird part, I can add one to the object repository but when I go to the other tab and try the same qtp becomes extremely slow. The + sign for adding it to the repository appears but when I click it, it gives me a message saying this object cannot be added to the repository.
The Web app uses extJS if that matters and this is a high level webelement that has a constant html id. I'm just puzzled as to why it works in one module but not the other.
There are also some subtabs where you can click on this form. Those work fine but when it comes to capturing this element the issue persists.
Any hypothesis as to why this is happening?
Okay it looks like it works when I took off the visible identification and just identifying it by the html id. I still don't get why taking the visible made a diff but it works.
I have recently noticed something odd with Display Suite. I am rather new to Drupal so if its something on my mistake please do not make fun of me.
But I have noticed that no new custom display settings (view nodes are being added to either node or field collection) previously it worked perfectly but now if I create a new view mode and attaching it to the node / field collection it seems it does not apply to it.
See the photos attached. Any suggestion?
http://oi59.tinypic.com/727fqp.jpg
http://oi59.tinypic.com/jb44cj.jpg
P.S. I have cleared drupal cache but it still keeps not working.
Thanks in advance
Fist I'd say that if you're a new user to Drupal, using Display Suite is really jumping into the deep end. It's a really powerful module and creating View Modes is just the tip of the iceberg of what it can do. Second, when you create a new View Mode, you're doing it for an Entity (such as Content Types, Users, Comments, File - but not so much a single node, nor a field). You can find more info on what View Modes and entities are here. You don't need Display Suite to activate other View Modes but if all you're wanting to do is create a custom view mode, the lightweight module to use for that is Entity View Mode. Lullabot does a nice job of explaining this module here.
Anyhow, modules aside, note that the controls for turning View Modes on and off are only found on the 'Default' view mode for a given content type, ie: when on the Manage Display page of whatever content type you're working with, at the top right under the main tabs, you'll see your activated view modes. If you select 'Default' then you will see the control to turn on/off other view modes.
Now, maybe you're wondering how do you see what a particular View Mode looks. To do this, you're best off using Views as it ties in nicely with View Modes.
Hope that helps.
I have to modify an old VB6 program that uses ActiveReports 2.0 at work and I am having some problems (BTW I have never used this program before and only have a basic knowledge of VB6)...
I have to make some text boxes biggers which is pretty easy to do but as soon as I move them a whole section of text (and not simply the content of that text box) disappear.
I have noticed that it was in some sort of section (sorry, I don't know how they call that) which englobed those text boxes so I made it bigger and that made no difference.
What could be causing this?
Thank you!
Nick
It sounds like the TextBox is inside a UserControl. A UserControl is created by a developer, and is basically one control with any number of other controls in it. You can check to see if there are any User Controls in your project in the Project Explorer (Ctrl+R).
One way to know exactly what class the control belongs to is to open your form in design mode (Shift+F7), click on the control, and look at the Properties window (F4). The drop-down list should show the currently selected control's class name in bold, then the name of the object.
What is the control's class? If it is anything other than TextBox, then this would explain the unexpected behavior you experienced.
I'm currently extending a custom "Platform" for VC-2010 (it is extremely similar to the standard pipeline and mostly just swaps 'cl' for 'gcc') and have run into a problem with the property pages.
I can't seem to figure out how to force a property page to always be visible. This page is for a tool that will pretty much always be run on a special control file that has many different tools run over it (hence why I don't want to directly link it to the file type via the 'FileExtension' in my 'ProjectSchemaDefinitions' file). So far I've only been able to get property pages to display when I've added a file with the correct 'ItemType' as an 'Item' in the vcproj file.
How can I make it so that my custom property page is always displayed, regardless of whether there is a property group for it in the vcproj file?
Thanks
A fresh look at the code this morning revealed the 'ProjectTools' MSBuild item which seems to do exactly what I want.