For my Android Buildfire app, I am using buildfire.history to navigate between screens within my plugin. Using the Buildfire built-in back button in the title bar works fine and correctly pops the history when pressed. However, when Android's native back button is pressed, it does not pop the history and instead seems to want to exit the plugin (which is especially a problem on the home screen as it exits the app no matter how many breadcrumbs have been pushed).
I would expect this to work the exact same as the built-in back button. Is this a bug in buildfire? I even made a super simple plugin to test the history navigation and it is an issue.
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 am working on electron app where i open a child window which i want to be above all the windows (not above fullscreen windows though), I managed to do it by using
win.setAlwaysOnTop(true, "screen-saver");
It now stays on top of all other open apps and keynote app presentation mode, i want user to be able to click buttons inside my window but now the issue is as soon as user clicks on button or just window in my child window, keynote window minimizes (as focus shifts to my window).
What i tried : I tried almost all available window option given in electron docs with different variations, I also tried playing with modals, but obviously modals stay in window itself, i want to keep main app minimized and keep child window on top of other apps. I also found electron-modal package, but that also behaves same.
working example
I was trying different application to check is any other application is able to do it, and i found that zoom app window (in screen share mode) is able to stay on top of keynote app and you can click buttons inside that app, you can move window, and keynote app keeps running in the background with no issues. I am trying to achieve exactly same behaviour.
This is something that you won't be able to recreate with electron currently, except through a native node module that manipulates your window related OS flags.
You can follow this issue on the Electron repository, since the flags introduced there should resolve your issue, or at least give you a point of entry to make your own PR or node_module.
https://github.com/electron/electron/issues/10078
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.
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.
I have a very basic jquery mobile modal dialog that INTERMITTENTLY reloads on clicking "close". This happens across all devices but not on desktop browsers.
The close button always works, but the dialog will pop back up randomly.
Anyone esle experience this. I'd post this on the jquery mobile forum but new registration is broken right now.
So, it's code related but the code won't tell you the what the problem is. The close button on the dialog was directly over the dialog's open button. So when you pressed close, the button beneath it was also being activated to open the dialog again. I moved the position of the close button to not be on top of the open button and that solved it. However, the bigger issue is having touch events read through all layers.