I am testing a mobile app I have built and noticed that when I manually clear a ToastBar message through the touch interface, if there is a Component beneath it, such as a Button, it is clicked as well.
I know that in Android native development, it is possible to mark a Component in a way that does not allow this to happen. Does anyone know if there is such a method or "attribute" in Codename One too?
Related
After Summit 2019, we were excited to start working on updates for 2018R2, and I practiced adding mobile screens for our custom modules in my sandbox.
We decided to fully refresh our DEV instance and reapply our customizations. No problem there, but when I try "Add New Screen" in the mobile section and then try to enter my screen number, the mouse goes to "waiting" and I can't add my new screen. Eventually, I get a "timed out" message. Same problem even when trying to add a standard Acumatica screen. Everything else in the project and Acumatica web interface seems to work fine.
Any ideas on where to look for what is preventing adding a new screen?
I'm on Build 18.209.0021.
It seems like an Ajax issue in the customization project editor. After callback to server the client page javascript is stuck waiting on the server response. You can try using Chrome browser which has less of those Ajax hangs and update Chrome if you're already using it.
There is also a known issue specifically affecting 2018 R2 Mobile that leads to generic error Sequence contains no matching element on mobile detail page. Based on your question this doesn't seem to be the issue you are having but you can give the workaround to this bug a try:
Open Generic Inquiry screen (SM208000)
Select FS-ServiceOrder inquiry, uncheck Expose to mobile and save
On Apply Updates screen (SM203510), click on Restart Application
This was identified by Acumatica support as a bug. Upgrade to a new release for the fix.
I have recently implemented a custom plugin that is just a basic JQuery application. When I'm in the admin dashboard, the back button works perfectly fine, send me back to the previous plugin I just came from. When I view it in the previewer however, the back button does nothing. I never overrode the back button functionality in the actual plugin code, so I'm not sure how this would be happening, especially since the back button functionality is working inconsistently between the dashboard and previewer.
I also tried restoring the back button's default functionality via the SDK navigation methods, as well as setting a custom navigation function on back button click. Neither of those worked. I am not even able to view this plugin in the debugger, as nothing will show up for this particular plugin in the list of remote sources when I try to debug it, so I can't even see if there is some error being thrown. Any ideas?
Do you have the latest version of the SDK? I believe there was a fairly recent release that fixed an issue related to the back button.
I have the latest version of the SDK and the back button works for me in the plugin tester.
I added a couple of custom control into a plugin and imported them on the server using the update site. They are working quit well so far but when i open an application in the designer client i can see the custom control from the plugin twice.
I tried to add them the same way bootstrap4xpages is adding a plugin but mine is duplicated.
One entry is without any icon the other has the standard grey cc icon. Not the end of the world but i must have done something wrong. Any idea why that happens?
It's a known issue with 9.0 and 9.0.1, specific to components that are Custom Controls. I encountered it quite a while ago. Mark Leusink had the same problem for Debug Toolbar and discussed it with the IBM developers at IBM Connect last year. So I would hope it will be addressed in the next point release, 9.0.2.
It still works fine though, regardless of which one you select.
After i had successfully ported the app. the app is running fine and taking touches on native ios nibs files where used for dialogs. But it is not taking touches on menu items.
let me explain this. It has some different view of axis. like tap on somewhere on screen will open some other menu which was not tapped. it seems it is taking touches but opening the desired menus but the location of buttons are not proper..
I had similar. In my case I had implementation of touchesBegan,touchesMoved and touchesEnd in View class with calling super. On iOS it works fine and messages going directly to controller. With apportable SDK it does not work. Maybe you have the same situation.
When launching the Chrome Extension Google-Hangouts, a panel initially appears that lists members and a link/button to create a new Hangout.
This panel is initially pinned to the bottom right of the browser window. When pinned like this, it remains always on top as a browser navigation session continues: users can go to different URLs, change tabs, etc. and that panel stays at the bottom right and stays on top of all other windows (or at least on top of the main browser window).
Once it's unpinned, you can drag it around the window, but it no longer stays always on top.
My question is, how was that achieved - what code, or what functions, do i need to call to create that window/panel so that it stays initially pinned and always on top? Is there some binding to some native code that's involved? Some other approach?
If anyone know and can show or explain, i would be hugely grateful as this feature is key to an extension i'm trying to build.
Thanks a lot!
This may not be an answer but to get a clue of what is happening I extracted the crx file to view its content there are a few OS specific files : ace.dll , libace.so and ace. After researching a bit i found this. This is a plugin. Hangouts extension is using ace plugin which is actually running on your desktop(i'm not sure about this). You can check this article
I found this related post: How to build an chrome extension like Google Hangouts
ACE is actually not what makes the window, Chrome has that capability built in, apparently. Even if you don't enable panels, extensions from Google can still make them, provided your OS is capable.